Slack Business - Enterprise facilitates team communication and collaboration with integration capabilities and a user-friendly interface, supporting mobile and web platforms. It enhances productivity through efficient organization, instant communication, and extensive customization options.
| Product | Mindshare (%) |
|---|---|
| Slack Business - Enterprise | 9.6% |
| Microsoft Teams | 6.9% |
| Atlassian Confluence | 6.6% |
| Other | 76.9% |
| Type | Title | Date | |
|---|---|---|---|
| Category | Enterprise Social Software | Jun 23, 2026 | Download |
| Product | Reviews, tips, and advice from real users | Jun 23, 2026 | Download |
| Comparison | Slack Business - Enterprise vs Microsoft Teams | Jun 23, 2026 | Download |
| Comparison | Slack Business - Enterprise vs Atlassian Confluence | Jun 23, 2026 | Download |
| Comparison | Slack Business - Enterprise vs Adobe Experience Manager | Jun 23, 2026 | Download |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| Atlassian Confluence | 4.1 | 6.6% | 90% | 109 interviewsAdd to research |
| Microsoft Teams | 4.1 | 6.9% | 95% | 178 interviewsAdd to research |
| Company Size | Count |
|---|---|
| Small Business | 46 |
| Midsize Enterprise | 11 |
| Large Enterprise | 19 |
| Company Size | Count |
|---|---|
| Small Business | 142 |
| Midsize Enterprise | 48 |
| Large Enterprise | 97 |
Designed for seamless integration with apps and services, Slack Business - Enterprise provides efficient organization through channels and threads, instant communication, file sharing, and video calls. Productivity is boosted via notifications, reminders, bots, and automation. Customization enhances the user experience, promoting collaboration. However, improvement areas include video chat, meeting functions, and third-party tool integration. Users prioritize enhanced UI, security, and document collaboration, alongside better scalability, stability, and attachment browsing capabilities.
What are the key features of Slack Business - Enterprise?Slack Business - Enterprise is widely used across various industries, serving as a communication hub within organizations. Its features support internal and external communication, project management, and workflow optimization. Industries benefit from its integration with Google Drive and Zoom, enabling efficient collaboration and streamlined operations.
Strava, The New York Times, Spotify, Blue Bottle Coffee Company, Eventbrite, Box, Circa, Stripe
| Author info | Rating | Review Summary |
|---|---|---|
| Senior Consultant at a consultancy with 10,001+ employees | 4.0 | I've found Slack Business - Enterprise excellent for team communication, especially through threads and webhooks, helping us manage automation and tickets efficiently, though I’d love to see multimedia support and AI-powered summarization features added. |
| Co Founder at a tech consulting company with 11-50 employees | 4.0 | We've used Slack Business - Enterprise for over two years, mainly for deep integrations and external collaboration, and while it's effective, simpler integration setup for non-technical users would make it even better. |
| Director at Xander & Thomas | 4.5 | I've used Slack Business - Enterprise for internal communication and find it simpler and more stable than Teams, though screen sharing and direct calls could improve. Search works well, and once set, notifications are effective. |
| Integration Engineer | 4.0 | In my company, we've used Slack for two years as a primary communication tool. It's user-friendly with valuable features like customizable channels and integration with tools like Jira. However, app connectivity and search functionality could be improved compared to Microsoft Teams. |
| Webflow Developer at Qureos | 5.0 | I've been using Slack for communication with colleagues and clients for over four years. Its automation and integration features are valuable, though pricing could be more flexible for freelancers. Despite this, I haven't noticed significant ROI. |
| Senior IT Security Specialist at Citadele Banka AS | 4.0 | I primarily use Teams for messaging in web application scanning work; it's easy to use, looks better than Slack, and functions well, though I haven’t used it extensively enough to fully evaluate all features. |
| CEO at PeerSpot | 4.0 | I've used Slack Business – Enterprise for eight years to streamline R&D and deployment communications, especially with our external DevOps team. It’s effective, though sometimes distracting, so we limit its use company-wide. |
| Da at hanasoft | 5.0 | I’ve used Slack Business - Enterprise for six years and found it reliable, feature-rich, and easy to use, especially for team communication and API integration, though minor improvements like text color customization would enhance the experience. |
| Application Security Manager at Interact Intranet | 4.0 | We use Slack for collaborative tasks, especially software release management involving various teams. Its threaded discussions, wikis, and task-tracking features enhance workflow, though channel management could improve. Previously, we relied on multiple tools. Slack has boosted our process efficiency. |
| Data Engineer at BlazeClan Technologies | 3.5 | I use Slack for internal communication at my company, appreciating its Google Calendar integration and interactive features. However, it sometimes unexpectedly shuts down, and I wish it included a call group feature for easier meeting scheduling. |
Our main use case for Slack Business - Enterprise is internal communication within the team, especially test communications, which primarily happens through Slack channels.
We typically use Slack channels for test communications for any kind of internal discussions. When issues arise, we start a Slack thread and continue the conversation on that particular thread. We have been mainly using Slack threads for putting all conversation related to one topic in a single place.
One of the unique functionalities we use with Slack Business - Enterprise is Slack webhooks, which we use to push notifications into our Slack channels about status and outcomes of our data pipelines.
We have been using both incoming and outgoing webhooks. We use the incoming webhook to push end results of automation, which makes our life easier by allowing us to easily check the status of our automation jobs through our corporate phone while in Slack itself. This is the most important functionality we have been using and what I very much appreciate about Slack.
This incoming and outgoing webhook functionality in Slack Business - Enterprise is valuable in that we can send notifications in text format. One addition I would suggest is if multimedia such as images or videos could be added so that I can push them to our Slack channels using incoming or outgoing messages, that would be a feature worth adding.
Slack Business - Enterprise has impacted our organization positively. Slack Business - Enterprise is performing very positively compared to other chat applications and is very helpful at an enterprise level to keep track of everything in separate threads. Slack provides a very nice, friendly, colorful user interface, which is very helpful in terms of daily activities.
We have been using Slack to improve our team's efficiency and collaboration because as we have production support and manage many tickets, we maintain a separate thread for each ticket, and all conversation happens on the same thread. This allows us to reduce the usage of numerous emails we would otherwise send to our inbox. It makes our life much easier. In summary, it is very easy to maintain tickets and their follow-up through Slack threads.
One suggestion I would make for improving Slack Business - Enterprise is the support of multimedia such as images and videos that we can easily share through Slack. That would be great. Additionally, another thing is AI integration; if Slack has some AI capabilities to get insights about conversations or summarization, that would be a great feature.
If Slack has an AI feature that can summarize a particular Slack thread and provide a summary of that, that would be a great feature for us.
I would rate it a ten if it comes with some AI features, particularly using generative AI to produce summarization and other kinds of insights from communication in a more secure, data-secure way.
I have been using Slack Business - Enterprise for the last five years.
Slack Business - Enterprise is very stable with approximately 99.9% uptime. I have never experienced downtime on Slack in my entire career.
Whenever we had any issues, we directly contacted our internal enterprise team, and if something was beyond their hands, then it would only be escalated to the external Slack team. We have had a pretty good experience with our internal Slack enterprise team.
Neutral
Slack Business - Enterprise is a very powerful and simple tool to use, especially for small organizations and startups as well as for big companies that have a large number of employees and big projects. Slack is very scalable in terms of features and user experience.
Slack Business - Enterprise is a really great tool in terms of user experience, user interface, and threading capabilities. It is very easy even for a beginner to start with, and especially for smaller startup companies, it is a very good tool for internal communications. I rate this product an eight out of ten.
Slack Business - Enterprise is definitely a communication channel across multiple teams that we have. However, what we are heavily using is the integrations. Since we are a tech company, there are many operations going on at the backend. If something breaks, production issues happen, or tickets are raised by the client, we have set up a bunch of notifications and automations on Slack Business - Enterprise, and that is the primary use case that our organization is sticking with Slack Business - Enterprise. We haven't switched to any other communication tool because copying all those automations and interactivity that we have built does not make sense to migrate to any other tools.
Our organization uses multiple vendors across AWS as a cloud provider and Slack Business - Enterprise as the communication channel, among multiple others. We are using the premium version, which is a paid version. AWS provides a multiple suite of their services starting from database service, storage service, compute, and many other services.
The first one is definitely the integration. We are using a bunch of integrations with great depth, not a surface level integration, but very deep and very structural workflow related integration. Secondly, I would say external collaboration with other companies' Slack Business - Enterprise workspaces. Since we work with a lot of enterprise customers, Slack Business - Enterprise gives us the opportunity to create cross-functional or cross-organizational channels. Our team is able to create channels and communicate with other enterprise customers' accounts, which is very much essential for us.
Slack Business - Enterprise keeps on adding a lot of features, but I would not comment from the feature point of view. Rather, I would comment on the ease of integration point of view. There is some scope for improvement. There are a lot of integrations and custom integrations available, but I believe there are opportunities to make those integrations much easier and faster, particularly for business or non-technical people.
We have been using Slack Business - Enterprise for almost two to two and a half years.
I do not use search capabilities to the fullest extent. I am already integrated with a lot of other tools where we do the searching very well. We haven't explored the search capability to the fullest extent possible with Slack Business - Enterprise. However, basic search works fine.
From the project management point of view, we are not using Microsoft or Atlassian or any other tools. We are continuing with Asana, but we also explored other tools such as Notion because of some restrictions by our customers. The tools that customers sometimes specifically mention are the ones we have to use. So, we are still using Asana.
We haven't explored MCP server yet. We are continuing with Asana, but we also explored other tools such as Notion because of some restrictions by our customers. The tools that customers sometimes specifically mention are the ones we have to use. So, we are still using Asana.
The custom integration or bespoke integration through Slack APIs is the primary reason that we are still on Slack Business - Enterprise and we have never thought of migrating to any other vendors or exploring any other vendor. Over time, we have written a bunch of custom and bespoke integrations for our internal business processes, and we are heavily using those.
Out of 10, I would rate the integration capabilities somewhere between seven to eight. The reason that I am not willing to give it a nine or 10 is we haven't explored a bunch of customization capabilities. Maybe we believe that the customization is available, but it can be much easier or faster to implement. That is the only reason that I would deduct a couple of points. Whatever we require for our business operation, it is completely satisfied. If I rate the complexity on a scale of one to 10, where 10 is very simple and one is very complex, I would rate it as 8.
I would rate this review a 10 out of 10 overall.
I am still with HubSpot and work on the basic HubSpot platform, not Marketing Hub or Service Hub.
I have recently moved jobs, so apart from HubSpot and Pipedrive, the tech stack is pretty basic. We use Slack Business - Enterprise and Granola, which is interesting.
We use Slack Business - Enterprise for internal company communication.
The call functionality when making direct calls to peers could be improved. Notifications need to be set up properly initially, but once configured, they work effectively.
It has become easier to use than Teams, which is the main benefit of Slack Business - Enterprise. It is simple and connected.
Searching in Slack Business - Enterprise is very easy.
Slack Business - Enterprise is superior compared to Teams.
Slack Business - Enterprise is very stable.
Granola (G R A N U L A) is an AI notetaker that is quite effective.
The direct call feature could be enhanced, particularly when calling peers.
When showing screens during calls, the screen sharing functionality is not as smooth as Google's offering. It appears to be designed for short calls, which limits its effectiveness for longer sessions.
I have a bit less than five years of total experience with the solution.
Slack Business - Enterprise is very stable.
I believe Slack Business - Enterprise is scalable, as massive companies use it.
I have never had experience with technical support from Slack Business - Enterprise.
Negative
I have worked with Teams for internal communication.
Slack Business - Enterprise is superior to Teams. Teams has issues with UX and features. Teams is quite clunky and I never really enjoyed using it.
I didn't do the full integration, but signing up and downloading Slack Business - Enterprise is easy.
I don't use CMS Hub for web content management.
On a scale of 1-10, I rate Slack Business - Enterprise a 9.
My experience with Slack is that for the past two years in my present company, we use it as a communication channel for each and every team discussion, manager discussion, or any alerts through various channels.
We primarily use the application on our system, connecting it with our official email address, and we have been doing this for almost a year. However, they plan to change to improve cost efficiency.
What I find valuable in Slack is that the interface is very attractive and it's easy for any new person to adapt to. There are a lot of channels we can create, and we can add people to those channels, allowing us to receive messages or conversations only between those individuals. Additionally, we have created some error alerts and notification-related channels in the Workato recipe itself, where if we encounter any production issue errors or alerts, we receive error notifications with descriptions, error messages, and recipe names in a dedicated production error alerts Slack channel. Users can also easily set their statuses in Slack when they are out of the office or in specific meetings. Furthermore, we can manage Jira tickets directly through Slack, allowing us to comment on and create tickets.
My impressions of the search functionality in Slack are that it is good, but it does not meet high expectations. There are opportunities for improvement, such as making the search functionality more intuitive or integrating it with AI to enable easier automation of tasks.
Regarding functionality in Slack, I believe we don't utilize it much. The interface and look and feel are preferable to me compared to Teams, but for cost reduction, it would be better to use Teams. Moreover, the newly introduced Copilot option in Microsoft products could be a significant advantage, allowing new users to find information by typing messages to get answers effectively.
For the initial setup of Slack, I find it straightforward. It isn't as difficult as one might think; it can be done based on requirements easily.
From my perspective, a disadvantage of Slack compared to Teams is that connecting between the apps can be a bit difficult. In Teams, all applications available in the Microsoft launchpad are easily accessible, while in Slack it is a little challenging to search for and install particular applications. Additionally, Teams allows for setting up an automatic update flow, which is more difficult to manage in Slack.
In terms of room for improvement in Slack, I believe we can enhance a few templates and lists. We can also improve the creation of channels, particularly in terms of privacy, security, flexibility, and the addition of members to newly created channels.
For the past two years in my present company, we have been using Slack.
As of now, no escalations have been made to Slack's technical support. We tend to focus more on Workato for support, but internally we raise service requests with the infrastructure team for any issues related to Slack.
Negative
The initial setup of Slack is straightforward. It isn't as difficult as one might think; it can be done based on requirements easily.
From next month onwards, we will be transferring from Slack to Teams to reduce the cost efficiency for the company.
I prefer Teams because most companies use Outlook as their working email, and they purchase licenses from Microsoft for Outlook and Teams. By using Teams as a communication channel alongside Outlook, companies wouldn't prefer any other communication channels or invest in additional licenses, thereby reducing the licensing cost for the business.
In terms of cost efficiency, I find Slack to be a great tool for communication. It simplifies the communication of meetings and integrates well with tools like Zoom and ServiceNow; however, to enhance cost efficiency, we will be moving to Outlook.
Based on my experience, I would recommend Slack to other teams. Personally, I think Slack is preferable because, in Teams, not all users adapt easily.
On a scale of 1-10, I rate Slack an 8.
I am an end user of Webflow, building and designing our website while integrating third-party tools with Webflow, which I have been using for the last four years.
I have been using Slack for over four years, specifically for communication with my colleagues and clients.
Slack is very supportive in terms of communication between my colleagues and clients.
While working with the reimbursement feature, I found the automation capabilities on Slack to be incredibly useful, allowing me to automate messages for specific dates or times and even to greet someone on their birthday.
I haven't specifically used the channel organization feature of Slack, as I am added to channels, but I use it with Airtable, which automates notifications to a specific Slack channel when a user fills out a form on our website.
In my experience, Slack is a stable product for communication, and I appreciate its automation features and integration of AI capabilities for enhancing specific functions.
I haven't experimented a lot with Slack, but I find it user-friendly; even non-technical users can navigate it comfortably.
I rate Slack's pricing an eight; I believe it should provide specific pricing models for freelancers or individual users, especially considering the current charge of around $20 per month after a three-month free trial.
They should introduce a separate license for freelancers.
I have been a customer for four plus years.
I didn't set the solution up myself.
I believe Slack's stability is a perfect 10.
In my experience, Slack is a stable product for communication, and I appreciate its automation features and integration of AI capabilities for enhancing specific functions.
I rate Slack's scalability at eight to nine.
There are many platforms similar to Slack on the market, and I believe a user who engages with Slack daily and utilizes various features would provide more valuable insights; thus, an eight to nine for scalability seems fair.
I haven't had the need to communicate with Slack's technical support.
Before Slack, I used a few tools professionally, but I currently don't remember their names.
I didn't set the solution up myself.
I haven't experienced any noticeable return on investment since starting with Slack.
I purchased Webflow directly from its website, not via AWS Marketplace or any other place.
I go to webflow.com to purchase it, and Webflow also provides you with a free feature to create two websites, so you can log in, create your account, and make those two websites for free.
Since I'm not integrating any third-party tools with Slack right now, I have explored Slack with Zapier for experimenting with automating specific features.
I believe Slack's features are adequate for the community and its members, though users who make automations might provide more reliable feedback on specific questions.
I rate this solution 10 out of 10.
I am working only with Web Application Scanning.
We are using Teams and Slack. I communicate with technical personnel from another company that is doing development work for us. We are using Teams internally and mainly Slack externally, so I am used to Teams more frequently.
The interface looks better to me. It is more easy to use. We do not need a lot, but it works for our purposes. It is only for messaging between us, and I am not using it for anything else. Everything is working okay.
I would need to use it way more to say something definitive. Teams looks way better to me.
I would rate it an eight maybe, just because I think I am not using it often enough to say something better or something worse.
I think everything is working fine. I have not encountered any issues that I can recall.
For me no, but I know that some others are using some ticketing system.
Positive
I do not know about the company. I was using it in a previous company, so maybe like four or five in total.
I think only from the company portal we installed it. So it was rather easy.
We are still using Qualys. I cannot answer this because I am not using it that much. There are a pair of channels and there is no need to search for information.
I am not using it too much. Now I have set it to start automatically, but before that when I was launching manually, there was a strange way to log in, not like just clicking on an icon and being instantly locked. I would say that is a disadvantage. Everything was working as needed and that is it.
I would rate this review an eight.
We use Slack Business - Enterprise to communicate. We have a few use cases. We don't use it for the whole company. The R&D team uses it just for themselves. In addition, we use Slack Business - Enterprise to communicate when we do deployments. We have a small group of people who are involved with the deployment of our website, so we send out information on that in the Slack Business - Enterprise channel.
We also have a channel with our external DevOps team and we find it provides very good communication to be able to have the relevant people at PeerSpot and the relevant people at our outsourced DevOps team all in a single Slack Business - Enterprise channel. In case any urgent issues come up, we can talk to them and chat with them in real time.
They use the deployments through Slack Business - Enterprise. Every deployment goes through Slack Business - Enterprise. It's really our source of record for all of our deployments. Everything out there is accessible, and in that way, everyone gets to see it. It's something that is important for all the people that need to know what's being deployed and when. If there's a problem with deployment, they're able to flag it in the Slack Business - Enterprise channel, and then we may need to roll back the deployment or fix it immediately.
Good communication and a very good user interface are the best features Slack Business - Enterprise offers.
Slack Business - Enterprise has had a positive impact on our organization with better communication. It provides faster response times, fewer emails, and has helped create a more agile company.
I think Slack Business - Enterprise is great for what it's used, but I don't think it is always the best usage for everything. It can be very distracting to people, so that's why we don't have Slack Business - Enterprise company-wide.
The excessive notifications and distracting nature keeps it from being a perfect solution for me.
We've been using Slack Business - Enterprise for about eight years.
I worked with ThreatMetrix before, but I do not currently use it. A year ago, I transitioned to a different field and do not work with technical tools anymore; I do only analysis now, primarily using Excel and collaboration tools like Slack Business - Enterprise.
The major purposes for using Slack Business - Enterprise are company communication and intra-team communication.
In terms of client relationships, we did use Slack Business - Enterprise occasionally; we talk with other companies, so we utilized it for external communications.
We did use Slack Business - Enterprise bots, and we loved them; they have markup support and online tutorials, and technically it worked well with no issues.
Customizable notifications help my team stay informed, and we did not have problems; notifications worked well with no issues.
Slack Business - Enterprise is beneficial for us primarily because the API was very beneficial, and that is the main one; the second benefit would probably be the upgrades they do, including integrating some AI and allowing customization of chats in categories.
When I need to locate critical information, I would say it is easy for me to find it.
In terms of drawbacks or areas for improvement in Slack Business - Enterprise, maybe some small things could be better, such as coloring text; if the API could support HTML, that would be great, but I think there are reasons why they do not support HTML. It would help if there was text color customization or a default coloring for messages, as when I was searching something, all text was the same color, making it hard to understand if something was coming from me.
I have been using Slack Business - Enterprise for six years.
I do not see glitches, latency issues, or downtime; I do not remember any latency, and the speed was good with no latency.
I think Slack Business - Enterprise is a scalable product fitting for small businesses as well as enterprises, with no limitations on the number of users.
I have not had experience dealing with technical support of Slack Business - Enterprise as I seldom have issues; when I connected to Slack Business - Enterprise API, tutorials and documentation were available online, so I did not have any problems.
Negative
I used Skype before it was still on, but I find Slack Business - Enterprise is better because Skype was heavy and Slack Business - Enterprise has many more options and features.
To install Slack Business - Enterprise, I do not remember having any problems, but I do not recall the process being complicated.
When I need to locate critical information, I would say it is easy for me to find it. I am not aware of the price and license for the product. In my company, I think we have Slack Business - Enterprise on-premises, but I am not sure. My review rating for Slack Business - Enterprise is 10.
We use Slack for collaboration between engineering teams, cloud teams, and technical support. One particular use case is releasing updates to our software. This process involves a risk management process, code review by different stakeholders, and testing by QAs. It is a multi-disciplinary task, and Slack helps to manage these releases via channels.
In managing releases via Slack channels, one major advantage over Teams is the ability to have threaded discussions, which helps in catching up on relevant discussions without the distraction of interleaved conversations. Slack's wikis, or task-tracking capabilities for different responsibilities, are useful for setting times and documenting release issues. These canvas and list items provide a management overview of release activities.
Slack's channel and chat management could be more intuitive. Configuring chats and pinning in Teams is easier, even though Slack has these features, they are not intuitive enough to engage with.
Additionally, I haven't engaged much with the Huddles feature, as Teams natively supports calls with a more intuitive interface.
We have been working with Slack for four and a half years.
Slack's stability is exceptional. I have never experienced downtime. It integrates with various systems, allowing us to manage site reliability, availability, and reliability.
Slack is endlessly scalable. As it scales, managing it can become challenging, however, it is necessary for communication.
I have never had any communication with Slack's technical support.
Neutral
Before Slack, we used multiple communication tools simultaneously.
The initial setup was easy, around an eight or nine on a scale from one to ten. Anyone can be invited to our Slack area, and it supports native applications and browser use.
I have seen improvements in collaboration, specifically in our release and cloud management processes.
The choice of communication tool often comes down to personal preference. Slack and Teams are well-established and influenced by users' experiences in other organizations.
I would rate Slack an eight out of ten.
For those evaluating Slack, it's important to consider it in the context of other communication tools and what fits your organization.
Neutral
