Slack Reviews

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.

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 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.

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.

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.

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.

The reason we are considering other products is because of integration. It doesn't integrate with CRM or ERP. We worked with Microsoft Exchange and we worked with CyberArk. We have what we need, so we don't require Slack anymore. But I think it's a good product.

The reason is we are moving towards a new CRM, so we have a suitable solution to integrate with the new CRM. We have more specific needs now. Slack lacks in certain integration. 

I have been using this solution for two years. 

Slack is a very stable product. However, with the free version, we only have limited message history access in the free version. But overall, it's a good product and a good solution.

There are around ten end-users in my company using this solution. There is only one administrator for the solution.

The initial setup was very easy.

Slack is a good product in its free version, but currently, we are integrating it with VM-sharing solutions like Dolibarr. We are also exploring other products similar to Slack. So, in about a month, we will be moving towards these new products and won't be using Slack anymore. 

However, until now, for the past two years, it has been a good product.

In the new CRM RFP, we plan to use Nextcloud. We also use SysTrack, but it's free. That's how our organization works. We have our own server, etcetera.

So, the only problem is we could not integrate it with our new solutions.

I would definitely recommend Slack for small companies. For medium and large companies, I'm not sure. Maybe there are integrations available in the premium version of Slack. Otherwise, it is a very good product. 

Overall, I would rate the solution an eight out of ten . 

I use the product to chat and huddle with company members.

It doesn't offer much in terms of improving the organization. It's just used for chatting, being in touch with others, and setting up meetings.

The huddle feature is valuable to me. We can easily make a video call.

The product should provide integration with other solutions like Gmail or Outlook.

I have been using the solution for more than two years.

The solution’s stability is good. I rate the stability a ten out of ten.

I rate the solution’s scalability a ten out of ten. All 150 people in my organization use the product.

I use Microsoft Teams and Google Chat as well. I'm more comfortable with Google Chat because the interface of my Gmail and Google Chat is on the same page. I do not need to open two different software.

The initial setup was very easy. It took five to ten minutes.

The product is not difficult to use. Overall, I rate the solution a nine out of ten.