Slack is an application that helps teams communicate and work together by combining messaging, file sharing, and app integrations in one place. It makes it easy for teams to stay connected and work efficiently, whether they are in the office or working remotely.
Slack AI works where you do. It can summarize conversations and tap into your companyโs collective knowledge to help you work in a smarter, simpler way.
My love for Slack continues to wane (that last design update has been a nightmare) and it makes me wonder about how ethically Slack is being in sourcing training data. Plus, how much AI do we need in everything?
Report
Slack remains at the center of modern work. With automation, AI integrations and ecosystem extensibility, itโs still a model for how SaaS can drive deep daily engagement. Excited to see how Slack continues to evolve the future of team communication.
Report
Congrats on the successful release. Finally someone is making an ai plugin for slark. I've been waiting for someone to do slark's summary plugin.
The $200/year price tag for Slack AI seems steep, especially considering companies are already paying per-seat fees. However, this might replace multiple smaller AI-powered Slack apps that businesses currently use. I'm curious how many existing apps this new feature could potentially consolidate.
also hey @wahl, it's great to see your name here :)
We ve been struggling to actually see the feedback users leave emails, forms, random messages all over the place.
So we built Retour, and every submission comes straight to Slack with full context ratings, notes plus AI-generated summaries to make sense of it quickly.
Teams at PwC, Vercel, Supabase are using it to act on feedback instantly instead of chasing it.
Curious how do you all collect user feedback in Slack?
Hey all, Let me start by saying that I really enjoy using @Slack. Every day I use it, though, I find myself wishing I could create threads within sub-threads. Is this limitation intentional to encourage keeping conversations in the main thread or are there any plans to support one additional level of threading in the future? For example, we're building a product called Mozart, an AI-powered digital audio workstation (DAW). We had a thread discussing the mixer component, and within that, someone started a sub-thread about how effects would be handled. I wanted to go even deeper and discuss one specific effect the reverb module but there was no clean way to do that without cluttering the entire sub-thread. I instead had to forward the message to the main chat and start another thread there. A sub-sub-thread would have allowed us to stay a bit more organised and focused without losing context. Keen to get your thoughts on this :)) !
Slack earns strong praise for fast, organized team comms, powerful integrations, and channel/thread structure that keeps work movingโespecially for remote teams. Makers from
prefer it over traditional tools. Users love huddles, search, and extensibility, but cite notification overload, clutter in busy threads, and limits on free plans. Best results come with channel hygiene, focused notifications, and pairing with a doc/issue tracker.
Slack remains one of the leading team communication tools, and for good reason. Its clean interface, speed, and extensive integration capabilities make it a fantastic option for organizations looking to enhance their collaboration. Iโve found it particularly effective for real-time messaging and file sharing, and the ability to connect seamlessly with third-party apps like Google Drive, Notion, and Zoom is a major plus. It was beneficial when we were developing Taskosaur, as the search function and workflow automation features significantly streamlined collaboration across our departments.
However, there are some drawbacks to consider. For larger teams, Slack can quickly become noisy and overwhelming if channels arenโt organized effectively. This can lead to important messages getting lost in the shuffle, which happened with us. Furthermore, I think the pricing is a bit steep for startups, which might limit its accessibility for smaller companies. Lastly, Slack's heavy reliance on internet connectivity can be a downside in low-bandwidth situations, making it less than ideal in those circumstances.
Overall, while Slack is a powerful communication tool, it does have its limitations that teams should be mindful of.
Slack gives you excellent real-time teamwork: fast channels/threads, solid search, and deep integrations (GitHub/Jira/PagerDuty) plus huddles for quick calls. Downsides: notification noise, fragmented decisions in threads, and higher costs if you need long message retention or multiple workspaces. Versus others: Teams wins on M365/meetings, Discord is cheaper for voice, email/docs are better for decisions. Verdict: great for day-to-day coordination. Pair it with an issue tracker and a doc hub, and enforce channel hygiene.
We use Slack because it's kind of the middle ground between Google Chat and Microsoft Teams, which both are not that great. Slack is a good messenger tool. If you use it just as a chat, trying to integrate anything else into it, and/or trying to juggle multiple workspaces, or get people onboarded who have never used it before is a bit challenging. I think Slack was better before they tried to add all of the features that all of the other tools most companies already use. It feels less polished, kind of clunky, and difficult to navigate. Conversation threads, lose messages and get buried if you get too many messages in a day. We use it because there's nothing else really. Would love to see a Slack Lite with just messaging and no other features.
Raycast
Slack remains at the center of modern work. With automation, AI integrations and ecosystem extensibility, itโs still a model for how SaaS can drive deep daily engagement. Excited to see how Slack continues to evolve the future of team communication.
Maxim AI
Telebugs