As foreign as chat is to email, mixing them unleashes unforeseen possibilities, like directly referencing customer emails in dev chat conversations discussing feature implementation.
Making collaboration between email heavy teams (sales, support) and chat heavy teams (dev) easier.
I personally think that using a threaded based UI is more efficient to use than the infinite channel Slack offers even for chat.
e.g. Having your Github notifications grouped into different threads based on branches and pull requests all labeled with a Github label.
https://missiveapp.com/slack-vs-missive (detailed post, with meat)
As foreign as chat is to email, mixing them unleashes unforeseen possibilities, like directly referencing customer emails in dev chat conversations discussing feature implementation.
Making collaboration between email heavy teams (sales, support) and chat heavy teams (dev) easier.
I personally think that using a threaded based UI is more efficient to use than the infinite channel Slack offers even for chat.
e.g. Having your Github notifications grouped into different threads based on branches and pull requests all labeled with a Github label.