Use separate chats for each instance of a recurring meeting
For long-running recurring meetings, such as weekly all-hands meetings, the text conversation can get very, very long, upwards of several hundred messages. This means every message in those conversations results in a notification that can take several seconds to load.
A solution would be to have one text conversation per instance of a recurring meeting, which means a) you're less likely to be tagged for a notification because you've posted in it before and b) if you do get a notification, it only takes a second to load up the entire conversation.
Zoltán Lehóczky commented
It's very annoying to have an ever-growing chat thread. We could cancel the meeting and schedule it again to create a new thread (like yearly) but this should really just work better out of the box.
Susanne Quiel commented
not necessarily separate chats, but easy to see in the chat which parts belong to which instance - maybe a menu like in the chat app would be helpfull, instead of recent and pinned have one part fpr each instance that can be opened and closed.
Thierry Dalon commented
Yes and it helps to split the meeting content. Else you have to check for the date it was posted. All in all it is a bit misleading/ confusing.
Sean Ellis commented
If implemented, this must be an option. There are enough users that this will be ideal for some, but not others.
As always, "no options" is not an option.