Slack Business - Enterprise Reviews

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.

We use the solution for internal communication within the company. We also use Slack for one-to-one messages and audio and video meetings.

The most valuable features of Slack are basic chatting, file sharing, and screen sharing. I've also used the solution for automation.

Slack's screen sharing might also add the remote control feature, which is not there. You cannot control somebody else's screen if they're sharing it. You can only view it. That is one feature that could help.

I have been using Slack for eight to nine years.

The solution's stability is good enough. Sometimes, it hangs a little, but you can force reload it to make it work.

I rate the solution’s stability a seven out of ten.

Around 800 users use the solution in our organization on a daily basis. I've used the solution with 20 to 30 people, and it has worked fine.

The solution's initial setup is easy.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight to nine out of ten.

The solution improves productivity and makes it very easy to coordinate with your teammates. Slack makes it easy to work in groups and easily search for information.

Slack has improved the way our organization functions. It spares you the trouble of emailing back and forth. You can just hop on a channel and interact with all the interested parties rather than waiting for emails to come and then responding to them. The solution really improves the organization's productivity.

I was running a monitoring setup. Whenever there was a high-priority alert, I linked it through Slack's webhooks feature so that I would receive a message on a certain Slack channel that something was down. I would recommend the solution to other users.

Overall, I rate the solution ten out of ten.

My organization uses it for collaboration and updates. We use it for meetings. Slack can be integrated with Confluence, Google Meet, and Zoom. We use it for important events. We constantly check Slack for updates from our bosses, CTO, and CEO.

The solution provides spell-check features while messaging. People cannot join groups without the admin’s permission. Slack’s security is really, really good. Even if something happens to our mobile phones, we can still retrieve our messages in Slack. I like that we can integrate the solution with various tools. The product gives the best user experience. The interface is wonderful.

The product could improve its notifications. The notifications on the phone are delayed. The notifications on the laptop come on time, though. There’s a latency issue in the application.

I have been using the solution for four years. I am using the latest version of the solution.

I rate the tool’s stability a nine out of ten. I had an issue when I was using Slack on a Linux distribution. Not all Slack integrations are reliable. The version of Slack on Windows is far more stable than Linux. I did not contact the support team for it, though. I just deleted the application and reinstalled it.

I rate the tool’s scalability a nine out of ten.

The initial setup is very easy. The product is deployed on the cloud. The deployment takes a couple of minutes. It has very low latency.

I advise everybody to use the solution. It is one of the best tools that a company can use. It is specifically designed for collaboration within the workplace. Overall, I rate the product a nine out of ten.

Slack is primarily used for communication, file sharing, and sometimes for Huddle, which is similar to a Zoom call within Slack. You can start a call with the person directly. 

Slack offers several valuable features. Firstly, they have a message deletion feature, which is now available in other software as well, but Slack was the one who introduced it in enterprise solutions. 

Additionally, Slack has a great feature for creating communities. This means that if you want to communicate with someone from a different company, you can create a channel specifically for them. They won't have access to other channels or public channels in your company, only the channel you've created for them. This is particularly useful for our interactions with one of our client, as we have a dedicated channel with them, allowing us to receive support. It's one of the best use cases I've seen for Slack, apart from its primary use for intra-company communication.

The video calling experience on Slack needs improvement. We prefer using Google Hangouts for video and audio calls because the call quality on Slack is not up to the mark. There is still for improvement in this aspect. The audio and video quality is not so good. 

So, we have two applications for communication. One is Slack, and the other one is Google Hangouts. So, it is definitely an area of improvement.

We started using Slack in 2018, so it has been around five years.

Slack has been stable for us. We have experienced only one outage since we started using it in 2019.

Everyone in our company, approximately 1,300 employees, is using Slack.

We contacted Slack's support team when we were building a bot using Slack. They were quick to respond and provided us with the necessary documentation.

Setting up Slack was very easy. It's an out-of-the-box solution that can be quickly deployed.

Slack is hosted on the cloud. It is a SaaS tool, we don't need to worry about the hosting details. We access it through slack.com, just like accessing Facebook without knowing its hosting details.

Slack is definitely worth the money.

I would recommend using Slack. You can also consider Microsoft Teams. They are a good alternative. In fact, if you are using Microsoft Azure cloud, Teams can be more cost-effective for you compared to Slack. However, if your company is on AWS or Google Cloud and not using Microsoft Cloud services, then Slack would be a more affordable option as a standalone system. It's worth noting that Teams comes bundled with a license for Microsoft Cloud subscriptions.

I would rate Slack a nine out of ten. They have had very few outages, and the software's features and GUI are impressive. However, there is room for improvement in the calling experience.

We primarily use it for internal communication and coordination. Mostly, we were using it to share information and then, you know, use it more as a repository for exchange and communication among users. 

So we were using it more like an alternative to email, at least for all internal conversations and coordination. That's one. And mostly to share info and share docs, etcetera.

Basically, the fact that we moved to one platform and away from emails has helped us. Everybody can see what everybody else is saying, so we don't have to plow through tons of emails. The fact that there is a history already there for somebody to see, at least since the time they became a member of a group or a team, is the biggest time saver. 

We can always scroll back and look at the history to see what happened and react based on the context of the conversation or discussion. For me, that would be the biggest advantage of moving away from emails.

Our usage was fairly limited. We used it to communicate with our team internally, and, in some cases, we had Slack channels with customers as well. But that was purely to ensure that the information was accurate and there were no different versions. Everyone was aware of the latest happenings. That's the only feature we actually used. We never used any other features.

However, I appreciated that it was easier than email and more comfortable than sending emails. The entire conversation is recorded in one place where anyone can go back and look through past discussions, statements, or situations. It's much easier than trying to figure out how to use the search feature in email. And, obviously, given that multiple threads could be initiated, email can lead anywhere. Slack helps us keep the conversation focused and avoid multiple threads that create more confusion. I would say that has been the biggest advantage for us.

For me, the only thing I can say is that every time somebody sent me an attachment, the attachment was listed somewhere, and then I had to open the conversation and go to the individual to open it. So there is no handy repository or an easy way to quickly look at attachments. For me, that was a bit difficult.

I would say that having a small panel with a list of all shared attachments with whom I'm conversing would be important. Many times, I had to search and had some trouble finding the file. But that's about it. That would be a significant improvement based on my experience.

I used Slack for a year and a half.

I would rate Slack as very stable. I don't think we ever had an issue with it. I would say it's a nine out of ten for stability. It was very stable. We never had any major issues with it.

For my use case, I would rate the scalability a nine out of ten. Other than the limited issue of searching for files, I didn't find too many issues. But overall, it was highly scalable and served its purpose well.

Our organization was small. It was about 25 people. So everyone was using it, and we had clients and partners as well. So we had around 30 to 35 people using Slack across our organization and external contacts.

We used to reach out to our internal team, and they handled everything. If we ever needed support, we would go through them.

We have an IT team to take care of the deployment. There was no maintenance required. Whenever there were situations where Slack was down, we were informed. So there was nothing else except for updating the client version whenever a new update was released. But that's the extent of the maintenance. It was limited to that. It was more like an app update. Since it was on the cloud, there was nothing else for us to update. Whenever a new update was available, Slack would send us a message, and we simply updated it.

In terms of return on investment, I think it was okay. We were pretty satisfied with it, although there could have been improvements, especially in terms of pricing. But compared to the alternative of using Gmail, we found Slack to be more efficient in organizing content and information.

It was more time efficient and helped you save time compared to writing emails. It was faster than writing emails, but the ability to organize content and information properly is what I appreciated the most.

I would put Slack around seven out of ten,  in terms of return on investment.

I would rate the pricing model a seven out of ten, where one is low, and ten is high price. It's on the more expensive side. For the usage we had, it would have been better if there were different pricing plans because we were not utilizing all the features that Slack offered. Although, there were no additional costs.

I would definitely recommend it. However, it depends on the situation. There may be other Slack alternatives available now. Especially for internal communication and coordination, there might be better tools suited for specific use cases. So, based on my personal experience, I would recommend Slack, but it depends on the specific use case.

I would rate this product overall a nine out of ten. They are delivering on what they claim. Whether it meets my specific use case or not, it's more about the product fit for what I wanted to achieve. But considering the extent to which we used it and its alignment with our goals, I would rate it around nine out of ten.

We use the solution to manage communication within our organization.

The solution could be more stable compared to Microsoft Teams. Also, we encounter errors with Slackbot while granting authority. It needs to be more straightforward in providing documents.

I rate the solution's stability a six and a half. It could be better.

We have 200-300 solution users in our organization. I rate its scalability a seven out of ten.

I rate the solution's initial setup process a nine out of ten.

I rate the solution's pricing as five out of ten. It is less expensive than Microsoft Teams.

I rate the solution a nine out of ten.

I work alongside other departments, and we use Slack mainly as a source of communication.

Slack is a very collaborative tool that makes it easier for me to communicate with the onboarding and billing teams.

Slack tends to crash once a month. We have to keep an eye on the dashboard status because there is always an issue with attachments or sending images once a month. The application crashes out of the blue. There are issues in general with the application, especially the desktop application.

I have been using Slack for about a year.

Slack’s stability works fine for us.

Slack is a scalable solution. About 500 to 600 people are using Slack in our organization.

I contacted Slack's customer support because I once faced an issue sending invitations. It was an issue on their end that was easily fixed because they were super helpful.

Positive

Slack's initial setup is super easy.

Slack is deployed on-cloud in our organization.

Since it's very easy to collaborate with the tool, I would recommend Slack to other users.

Even though Slack is a very useful tool with many incredible features, the fact that it tends to crash once a month makes it a little bit difficult to work with.

Overall, I rate Slack a seven out of ten.

We're using Slack to communicate with other partners outside of our company. In most of the cases, it's for external communication.

Basically, it’s great for getting different kinds of groups with different partners - let's say one with the IT, one with the payment solution, into one place. It’s used just to communicate and nothing more than that. It's just a better solution to use instead of Skype or any other standard application.

It is easy to set up.

The solution is stable.

The product has the ability to scale.

The last time I tried to work with some other partners on the same document, we couldn't figure out a way to work on the same one. We actually have to have one person gather all the documents and then prepare one. It was actually taking way much longer than usual. We’d like it to have more capability for everyone to work on one doc in real time all at once.

I’ve been using Slack for three or four years.

The solution is very stable. It doesn’t have bugs or glitches. It doesn’t crash or freeze. It’s reliable.

I haven’t seen a lack of scalability. It seems like it would be easy to expand.

Most of our colleagues use the solution. We have around 100 people on the solution.

I haven’t used technical support. I can’t speak to how helpful or responsive they are.

We’ve also used Skype.

It's easy to set up. The IT team didn’t take that long to install it. There’s nothing wrong with that.

I don’t deal with the licensing aspect of the solution.

I'm not sure about the version I'm using. IT is taking responsibility for that.

I’d recommend the solution. It's easy to use. You just kind of need to use it more often just to get used to it and see how it works. It's nothing hard to figure out. It's easy to start.

I’d rate the solution an eight out of ten.