I categorize Slack as a modern workstream collaboration and automation tool. The simple use cases are peer-to-peer or group chats and collaborating in channels. I might create a channel based on certain needs, like a project or a particular subject, but it's not just chat, there are also features like the sharing of information and knowledge. I also use Slack for document collaboration.
Then you get into more advanced features for tools with things like automation, such as being able to integrate with ServiceNow. This ITSM platform opens up tickets and automatically creates a channel where service teams can easily communicate about that event or that outage if it's a high-priority ticket.
Twenty years ago, we communicated through email, where we would send documents back and forth with different versions as people changed them. If we sent the documents to a group of people, we would have to figure out the versions and who modified what. When we work with a platform like Slack, we can have one source without merging different document versions. That makes people more productive and collaborative at the end of the day.
Slack is not as strong as competitors like Teams when it comes to things like video meetings and audio meetings. Teams is more of a Zoom-like product, where you can get into virtual conferences and work through issues and so on, and that's where Slack doesn't scale as well as Microsoft Teams. I don't know if they will improve this because Zoom is a Slack partner, so Zoom themselves use Slack.
I have six years of experience with Slack.
Slack is very reliable. I've seen two significant events in the past six or seven years I've used it. Since you are relying on something that's not on-premises and using the Internet to connect to it, a robust Internet networking capability is very important.
Slack's scalability is massive, and there are companies out there with hundreds of thousands of users. If you're talking about the free version, it is limited in its capabilities. But the enterprise edition of Slack can scale absolutely massively.
Since it is a SaaS platform, there are different versions of Slack. There's an enterprise, encrypted version, and the initial setup is relatively easy. The most important thing is preventing the service from becoming the wild, Wild West by putting some standards and controls around it so you don't have everybody arbitrarily creating channels on Slack, and that channels are either created through a set of Slack administrators or automation based on a specific need, like a high-priority incident.
The pricing can range up to about twenty bucks a user. You can spend a lot of money, especially if you're talking about thousands of users. Generally speaking, Slack is less expensive than Teams. Slack doesn't include all the bells and whistles that Teams does. So you can go from a $6 license in Microsoft 365 to a $50 license per user per month, and there's a lot more you can do in the $50 license.
Slack has been around for a long time, and it's an industry leader. Of course, Salesforce owns Slack now and is starting to integrate into it. I have attended Slack conferences and met with product and support managers. They're an excellent organization.
Choosing Slack depends on the organization's size, so you need to plan your deployment and make sure you put some controls and standards in place and not just turn it on.
If you're a Slack shop, you will have to have something like a Zoom or Microsoft Teams platform for when you need to do video conferencing internally or externally. Many shops have both products, but they use Slack for collaboration, chat, and so on, and use Teams for video and audio conferences. At the end of the day, Slack is missing those capabilities, so either you're going to be a Slack/Zoom shop or you're going to be a Microsoft Teams shop. I rate Slack an eight out of ten.