4 ms·
Thank you for the pointers! On your third bullet, when you say "versus channels" are you also saying "don't use channels at all" or are you saying "when using c
by jxf 2y ago
Thank you for the pointers! On your third bullet, when you say "versus channels" are you also saying "don't use channels at all" or are you saying "when using chats, use @everyone but don't do that in channels"?
- turtleyacht 2y agoIn channels, you can only @-mention individuals or the channel name. I believe @Everyone is only available in chats. You'll have to use channels. Channels enable connectors like webhooks*, and it's the only way to speak to folks outside being invited to chats. * Webhooks will be deprecated in a few months in favor of Power Automate.
- Spooky23 2y agoI never use channels because of the context switch. Just big, adhoc group chats. I’m a member of about 300 teams, have literally never looked at them.
- turtleyacht 2y agoIt used to be easier to sort Teams, but that's admittedly too many without hyperscroll. Group chats are quick to make, refresh to the top, and naturally expire. It's nice that chats can be renamed to focus on a topic.
- rk06 2y agoNo one in right mind uses channels. Last time I checked, you can't pop out channels. While you can pop out chats.
- turtleyacht 2y agoYes, it's still the case that only chats can be popped out and not channels. I guess channels and chats differ by exclusivity and recency. Chats auto-sort by latest and are invite-only; a Team can be a "public square" for petitions or callouts. There are use-cases for private Teams if additional features beyond chat are needed. Channels require scrolling, so it's usually easier to ping someone instead. Channels as webhook sinks incentivize regular checking, but only if the user is actively seeking.