Slack Reviews

We are using Slack to collaborate between employees, as many of them are working from home. While I personally started using it a couple of years ago, it has been about a month since all of our employees began using it.

Slack allows our employees to share information on a daily basis without overloading email.

This solution is easy to use.

Slack makes it easy for employees to contact each other and exchange documents or information. It is not like a big CRM but for internal usage, it's good enough.

I would like to see a special feature for multiple people to collaborate on a document, working on it at the same time.

For most add-ons, clients need to know the command to run the add-ons. I think it would be useful for them to design the appropriate icons so that non-IT clients can launch them in a simple and easy way. For example, starting a video conference with an already defined room.

It would be useful for an organization to be able to define a specific storage space for the storage of all documents exchanged by teams

I have been using Slack for two years.

This is a stable solution.

We are only using the free version so I do not really know about the scalability.

We have 300 users and daily, there are 60% to 70% of them using it.

I have not needed to contact technical support.

Slack is very easy to set up and there are only a few steps involved.

We deployed this solution ourselves. It was easy to send employees invitations to join.

We use the free version that does not have a license.

We may use Microsoft teams in place of Slack in the future, although this is not a decision that I will be part of. At this time, there is not much interest in moving to Zoom or Teams.

We did not want to spend too much time investigating options before starting our remote work and because I was familiar with Slack, this is what I chose.

My advice for anybody who is researching Slack is that it is easy to set up and quite helpful for daily common things. We use only the free license but it is enough for us. If we continue to use Slack after the current crisis ends then we may buy more features and add-ons. For now, however, we have what we need.

Overall, we are satisfied with Slack.

I would rate this solution an eight out of ten.

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 use Slack for general communication, conference calls, and sharing screens because we have people working from different countries.

There are 53 people using Slack in our organization.

The solution is deployed on-premises.

It gives you the ability to share your screen and have conference calls. You can also create different channels. You can use it on your PC or on your phone.

We recently had to learn about another program, and somebody had to teach from abroad. They could share their screen, and we were able to have a conference call through that.

Everything has room for improvement, so I think Slack could add additional features without making the solution slower or more difficult to use.

I have been using this solution for a year and a half.

The stability is good. It doesn't matter how many people use it.

Setup is pretty easy.

I would rate this solution 8 out of 10. 

You can use it on your phone, not just on your PC or laptop. It pretty much works the same, and you can do almost everything on your phone.

I use Slack primarily for communications. This includes communicating with individuals as well as grouping people into cells to work on specific parts of a project. We don't use the features beyond just the basic communicative side of it.

With respect to being a clean and efficient communications platform, I think that it does the job quite well.

It's very good for when you have a large number of people working within the team. It can be a challenge to ensure that people are working within the bounds of the project that they are assigned to, and Slack is effective for ensuring that happens.

I have found it cumbersome to create and set up groups, or channels. I recall having to go through the application, then back to the web site, and then back to the application. I didn't really like that and this is something in the interface that should be improved. If it were possible or easier to create those working groups within the application, without being taken into a browser and working entirely within the software itself, that would be ideal.

I would like to see integration with collaborative tools, such as word processing software or programming environments and coding software, made clear, easy, and as broad as possible. It should handle simple products, all the way to complex ones. It should be easily embeddable inside a channel so that anyone can use it.

I think that changing the privileges to remove restrictions would help the users to adapt to the platform more easily, removing bottlenecks. Having to request access for particular users is time-consuming and it would be better if more people can do these things themselves.

I have been using slack since the beginning of 2019.

I have not noticed any bugs, glitches, or other issues with stability.

We have between 30 and 50 users.

A lot of the work that we're doing now ends up on Microsoft Teams. Whether I like it or not, it tends to marginalize and eventually push Slack out of the picture.

I found the initial setup to be straightforward. You can also bombard people with reminder messages that they should be joining a channel or discussion. In fact, I've had less trouble with slack than I've had with Teams.

From my perspective, this is a good product and I definitely recommend it. My advice for anybody who is implementing this type of product is to first consider what it is that they want to achieve, and then make the decision about which product to implement based on that. If you're trying to pick between platforms, like Teams versus Slack, I would recommend Slack for a variety of reasons. Even if you are using Teams already, I would suggest using Slack in addition because you can't go wrong.

I would rate this solution an eight 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 it with our clients for sharing files and for communication.

We use thread-based communication. So that if a new person comes to look into a problem for a particular task, they can easily go and look into the particular thread it is discussed in.

We also send/download multiple files at a time.

It's also helpful that we can do group and individual calls on Slack.

There is a great search functionality.

 Sometimes there are login issues.

I have experience using Slack. 

It is stable. 

Slack is east to scale.

It is an affordable solution. 

Overall, I rate the solution a six out of ten. 

The feature that is most valuable is the ability to be a part of multiple Slack channels that are all specific to our needs i.e. a product, infrastructure, personal one-on-one, small specific group, feature discussion, IT assistance, company announcements, etc.

The quick line of communication, most certainly improves the functionality of our organization. Discussions can happen at the drop of a hat, in a Slack channel and a critical decision can be agreed upon to take further action. Triage of customer issues can happen at the moment of crisis and this is of huge assistance as to how we can get our product back up and running, when needed.

I'd like the ability to re-organize the channels in my list. You can favorite a channel but you can't organize them in a specific order, that fits your every day use. I'd also improve it's security. It can be breached easier than an email client, so we tend to keep more confidential conversations out of the app.

I have personally used this solution for over two years.

Our Slack bots have issues from time to time. There have been a few times where the app was done but other than that, it has been a solid performer.

There were no issues with the scalability.

I have personally not used technical support for Slack.

We were using Gchat as a source to speak to each other but channel functionality is very important in Slack.

I was not part of the initial setup.

I am sure that other options were evaluated but I was not a part of that decision-making process.

Providing API connections to your bug database and any other database that you use, can give you updates and links inside of a channel, which is a huge help.

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