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.