Slack Business - Enterprise Reviews

We use the solution to collaborate with other teams. As a product manager, I need to engage with the engineering team, marketing department, and account executives.

The solution suits collaboration, where multiple people work on the same issue. We use it for integration with Google Drive and Zoom. It syncs up with the official Google account. So, I get notified through Slack whenever I have a meeting or if somebody shares a particular document on Google Drive. It also tells if somebody leaves a comment on a document on Google Drive. I also use it to connect with my internal IT team.

Slack allows me to write personal notes to myself and set reminders for them. It has a send now and a schedule send option, so I can send messages immediately or schedule them for later. Maybe you don't want to send a reminder to a certain team now, but you'll forget when you have to; you can schedule it.

Slack is an official application, and everything should be tracked, but sometimes, we accidentally share sensitive information on open channels. It would be good to have if there was an option to delete messages within a certain time. You could still keep the messages in the background, but they wouldn't be shown to the audience where they were posted.

I have been using Slack for two years. We are using the V4.34.121 of the solution.

The product is stable. I've never had any issues where it got stuck.

I rate the solution's stability a nine out of ten.

The solution is scalable. It is a lightweight application. Around 10,000 employees are using this solution in our organization.

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

We have used Microsoft Teams for collaboration. Teams is also for chats and meetings. Slack doesn’t offer meetings because Huddl gets complicated sometimes. Microsoft Teams has call features and collab. You can integrate MS Teams with your Outlook or email so you get notified of the meetings. I have to set up meetings on Google Calendar and then Slack notifies. Slack should set up meetings with Slack, and you can also take notes within those meetings. Slack is only for chats and as a collaboration tool within an organization, but it could be used to set up meetings and schedule meetings.

The initial setup is straightforward. We don’t need any support for the installation.

I rate the initial setup of Slack an eight on a scale of ten, where one is difficult, and ten is easy.

Engineering and product management teams should always have Slack, as it is an excellent tool for collaboration. If it is a small team, especially one that requires collaboration to support engineering development. Slack is a great tool because you can also share code snippets, which will be formatted in a code-friendly way. Slack is a good tool for these teams and is portable for everyone.

Overall, I rate the solution 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.

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.

Our clients use Slack because it is highly customizable, allowing us to create applications and plugins to easily connect with various applications and receive updates.

Slack offers the ability to make customizable applications and plugins. It facilitates the connection of various applications to receive and send updates. It's for popular applications like the calendar and others and it is also adaptable for cloud applications, making customization straightforward.

In Slack, there are areas for accessibility improvements. For example, Canvas has options for reading documents in particular channels, however, these could be more accessible. There are some accessibility glitches where status is not accurate, unlike Microsoft Teams, which provide accurate status updates.

I've been using Slack from July or September to November, which accounts for one and a half years now.

The stability is rated six to seven out of ten. It can benefit from updates, as it's sometimes not easy to restart.

The scalability is rated as high, with a score of eight out of ten.

Customer service and support can be rated as an eight out of ten, with good support and the ability to report issues.

Positive

The initial setup is rated nine out of ten, indicating it is easy.

We are like an implementer that acts as a partner. 

I would recommend Slack to other people, and I would rate the overall solution as an eight out of ten.

I used it for managing competition-related matters, as well as for handling announcements regarding new products or services. It was also a go-to platform for tracking logs related to ticketing and service issues that required urgent attention, as well as for internal tasks like software deployment and operationalizing services promptly.

One of the key benefits is the ability to easily share large video files and documents without any limitations. It also integrates with ticketing systems like Jira, allowing you to add plugins, such as Outlook, to streamline collaboration with emails. It offers customization options for various applications, including integrations with Zoom for video calls and a wide range of other integration plugins. This flexibility in integration is a significant advantage. You can segment your user base into different channels based on shared access, ensuring efficient communication. One recent noteworthy feature is the collaboration space, known as Slack Canvas, which enables users to share and edit documents collectively.

It could further improve by expanding its integrations to include conference platforms, such as Atlassian and its products. Integrating with platforms like Medium for article sharing and tagging, as well as LinkedIn for publishing posts and connecting them to Slack, would be beneficial. It would be highly advantageous if it could incorporate calendar information from sources like Outlook or Gmail, providing users not only with meeting schedules but also a comprehensive daily agenda view.

I have been using it for four years.

While downtime occurrences are not very frequent, there have been a few instances when we experienced outages on certain days. Overall, it is relatively stable compared to some other solutions.

It is a highly scalable solution, given that over ten thousand daily users rely on it for their work. As the user base grows, managing channels can become overwhelming, and maintaining them can be a significant challenge in such cases. It may require a minimum team size of around thirty to forty people or more to manage it effectively.

We don't interact directly with Slack; instead, we rely on our internal support teams for any issues.

We used Microsoft Teams previously. While Slack offers numerous advantages over Teams, the one area where it could improve is in providing a more robust system for document collaboration and organization, similar to the functionality found in SharePoint.

I do not have insight into the enterprise-level installation process, but accessing it privately is straightforward. You typically receive an invitation, a secure password, or an order code, allowing you to join the designated Workspace. Once you're part of that Workspace, you gain access to various internal channels, which is a significant benefit.

When it comes to pricing, it is on the expensive side.

I would rate Slack at around eight out of ten. It's a pretty decent platform that many startups and new companies prefer today, especially for larger audiences. One of the drawbacks or areas for improvement is the learning curve users from Microsoft-based products like Link, Skype, or Teams might face when trying to adapt to Slack's architecture. Slack's structure is quite different, and it can take some time for users to become acclimated to this new orientation. Once users overcome this learning curve, it proves to be a robust and highly effective tool that can benefit many users.

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.