Slack Reviews

The integration with third-party automation services such as IFTTT and Zapier has significantly boosted productivity.

We receive automatic notifications of certain business activities and planned events, instead of having to send out manual emails to disseminate that information.

It has encouraged more transparent communication, getting more staff members exposed to and involved in different areas of the business.

Many of the advanced features and integrations are built with developers in mind. More functionality and integration for other use cases would be welcome.

Slack integrates with bots that automate tasks and add functionality. A large portion of these bots do things specifically to help developers do their jobs, such as accessing code repositories and sharing code with colleagues.

It would be great if there were more bots and third-party integrations that targeted other groups of potential Slack users.

We have been using the solution for 18 months.

We have had no major issues with downtime or with the apps crashing.

We are using the free version, which only keeps a limited number of messages archived. As our team has grown, we go through this archive allotment fairly quickly.

We have not had to use technical support.

We did not previously use a different solution.

The solution was very easy to set up. I created the team through the Slack web site, which automatically invited everyone else via email and instructed them to download the client apps.

The free version can do pretty much everything you need it to. You'll have to pay if you have a large team or if you have specific security and compliance requirements.

We did not evaluate any other products.

Make a significant effort to get user buy-in right from the start.

If people see it as just another system, not a powerful email reducer and productivity booster, adoption will lag.

You really need everyone on the team to be on board for it to succeed. If even one person sticks to email-first communication, it makes everyone else rely more on email, which defeats the purpose of having Slack.

We primarily use it for sharing official documents and compositions instead of using platforms like WhatsApp. Although we haven't utilized it for meetings, the main purpose behind creating and using it is to streamline the sharing of official information within our team.

It allows to facilitate communication, allowing us to create channels for updates, file sharing, and photo sharing within our team profiles.

Integrating Slack with calendar functions would be advantageous, allowing for the seamless scheduling of meetings within the platform.

I have been using it for two months now.

I would rate the stability eight out of ten.

Its scalability is evident in its ability to handle a varying number of users, channels, and integrations, making it suitable for businesses of different sizes and complexities. I would rate it eight out of ten.

We previously employed Google Workspace. Slack provides visibility into the online status of team members when the application is active, it doesn't track users outside of the platform. Unlike some other tools, such as Gmail, where your online status isn't visible to others when you're using it, Slack primarily serves as a communication and collaboration platform.

Overall, I would rate it eight out of ten.

I use it if I want to search for information from Kubernetes communities, and then I chat with someone who already has knowledge or knows about Kubernetes. I use it to talk to people using other software like Kubernetes.

It is a really trendy tool for uploading information with cutting-edge technology. I can browse all the information to find what I want to really know.

In comparison to Teams or other tools, Slack's interface is not simple for me. It's not a user-friendly interface.

I have been using Slack for almost three months. I am using its cloud version. I just downloaded it from the internet as a third-party solution or software. I am a user of the solution.

The engineers in their department use Slack. Around 50 engineers use Slack.

In terms of setup, approaching its menu is simple. However, when I went to click and change the account, I was confused regarding whether it was proceeding or not.

It is an expensive tool. We pay 15 to 20 USD monthly per user.

I suggest those planning to use Slack to get another social network software such as Teams or Chanty, a tool used in South Korea, are very good. I think Chanty is used in South Korea, especially in the IT sector of Korea.

I rate the overall solution a six out of ten.

The channels feature is the selling point for me. Being able to create a conversation for both public and private purposes through some channels is an absolute plus.

I was the president of a college event planning organization. Being able to have a conversation with my executives separately from the organization members was very convenient.

With multiple events happening and multiple conversations going on, I was able to divide the conversations into their respective groups and create channels for focus groups. This increased our productivity and efficiency by more than 80%.

Archiving for direct messages made tracking back conversations very difficult once the group started to grow large.

From what I noticed while using Slack, once a channel starts growing in
its number of messages, older messages are archived. This made it more
difficult to reference older messages. To be able to search for a particular message, you'll need to remember the exact phrases or the sender.

I think it would be much easier to "Scroll back" into older messages even
though it archived.

I have been using this solution for three years.

Stability was not an issue at any point. My team and I used it across multiple devices and platforms and the flow was seamless.

We had no issues with scalability. I was able to create more channels as the team grew bigger.

I never had to contact the support team.

We were initially using email and IM chat to communicate. We switched because the conversations became unorganized and inefficient when conversations started overlapping.

The setup was very straightforward. Once I sent an invite to my new team members, all they had to do was create a password and sign in. Their channels were pre-assigned and they had no issues joining the conversation. It was also easy to navigate.

Through an in-house one. Level of expertise was as great as it could get.

I had a relatively small team, so I didn’t have to worry about pricing and licensing. I only encountered pricing third-party apps and bots to help facilitate automations.

I did not evaluate any other options as I did not have a reason to. Eventually I heard of Ryver. I was not compelled to switch though.

I think Slack is a very creative application to help unify communication across all team sizes. I will definitely suggest this as my first choice.

We use Slack for having meetings with one of our vendors.

The most valuable features are video conferencing and sharing content during meetings.

I would like the in-meeting content sharing facility to be improved.

We have been using Slack for about one year.

Slack is stable and we haven't had any problems.

We have not had issues with scalability but our audiences in the meetings have not been large.

The technical support is fine.

In addition to Slack, we use Microsoft Teams as well as Skype. I think that all of these products are comparable, with nothing, in particular, that is an advantage or disadvantage.

Overall, Slack meets the needs that we have.

I would rate this solution as average, at five out of ten.

Overall, it is a good idea as it works better than most solutions out there.

The mobile function is horrible. 

Notifications rarely show up. Either messages will not send or they will send twice.

The mobile app needs improvement. It consistently misses notifications.

I use Slack to communicate mainly for content related tasks with clients as they find it easy and quick to keep track of all of the on-going projects. Most importantly, it helped me to communicate with other content writers whenever I have to work in a team for a particular content project.

Earlier, while we used to communicate through email, it was good but it became difficult to keep track of all the projects and keep ourselves updated with the latest changes. Since we started using Slack, we have been able to solve each other's problems and identify all of the loopholes within a reasonable timeline.

Slack is a powerpack bundle of features that help small or large organizations to handle teams and their tasks. Personally, I love the feature that gives you the ability to name a channel as per task and include/exclude members within that channel to eradicate all other disturbances.

According to my observation, a large size file sharing feature is what can be expected, which will centralize all activities within Slack and that can save a lot of time.

I would like to see the social sharing of blogs, announcements, or other news directly from the message corner. 

• Channel conversations, because it's an easy way to get to a few people or a whole team at the same time.
• Private conversations, because they're simple, convenient and they work!
• Slackbot reminders, because it's a simple way to set a reminder for yourself or a colleague, without messing with calendars.
• Integrations. For instance, thanks to integration of our own application Woodpecker.co with Slack through Zapier, we get notified each time one of our users starts the paying process and each time they complete it. We can actually see the new customers coming on board in real time.
• Slack is just a communicator, no more. It has a narrow set of features focused on team communication. It's simple. I guess that's why it works so well for us.

Everyone's up to date with what's going on in our product development, marketing and sales. We communicate faster and no one has any troubles learning how to use the communicator.

I would like to see if someone has already read my message, but that's just a whim, not really a necessary must-have feature.

We have used the solution for over two years.

We hardly ever had any issues with stability. I remember Slack was only down once over the whole time I've been using it so far.

We haven't yet had any issues with scalability, but our team is quite small with only 17 people at the moment.

In fact, I never felt the need to contact support, so I have no experience with that, but I guess that's great!

We used a number of solutions which were really only a feature of a bigger product.

The setup was simple for me, but I was joining the team someone else set up.

We're using the free version and some people from our team wish that the message history had not been removed, so if you sometimes need to go back a few months in a conversation, the paid version would be something to consider.

Definitely give Slack a try.