- Review platform summaries (scale indicators)
- G2
- Rating: a high rating with a very large number of reviews on G2.
- G2's summary highlights ease of use and organizational benefits, while noting themes such as notification overload and feature limitations.
- TrustRadius
- TrustRadius lists Slack with a high aggregate score and a substantial review footprint.
- TrustRadius "areas for improvement" include task management and visual planning tooling; Slack is not typically positioned as a full project management suite.
- Capterra
- Large review volume with user stories emphasizing reduced email and improved collaboration, while also noting the need for notification management.
- Gartner Peer Insights
- The product has a Gartner Peer Insights page with user reviews accessible.
- Representative user-reported impressions (paraphrased from public reviews)
- Positive examples (paraphrased):
- A Gartner Peer Insights review described Slack as effective for team culture and rapid communications.
- A TrustRadius review noted that Slack helped improve interdepartmental communications and client coordination in that reviewer's organization.
- Capterra review headlines commonly emphasize improved team collaboration while advising careful notification management.
- Negative / critical examples (paraphrased):
- Some TrustRadius reviewers report limitations in the search experience, particularly in large or complex workspaces.
- Consumer-style review sites and community forums include complaints about pricing, UI/UX changes, and support responsiveness; these sources are more complaint-focused and often anecdotal.
- Community discussion threads report concerns about UI density, workspace sprawl, and cost comparisons versus bundled Microsoft licensing.
- Common criticisms and complaints (from review/community patterns)
- Notification overload and channel sprawl.
- Mixed assessments of search quality: some cite it as a strength, others report limitations in large-scale or cross-tool search expectations.
- Perceived price increases and changes to enterprise plan packaging, especially when compared to bundled alternatives such as Microsoft Teams.
- Friction related to UI/UX redesigns and changes to workflows.
- Why customers chose Slack over alternatives
- Faster, more conversational channel-based communication than email.
- Broad integration ecosystem (DevOps tools, ticketing, CI/CD alerts, etc.).
- Cultural fit in many engineering and product organizations that adopted channel-based workflows early.
- Why some customers left for competitors (churn reasons)
- Cost and procurement simplicity: organizations standardized on Microsoft 365 sometimes migrate to Teams because it is included in existing contracts.
- Desire for consolidation into a single vendor for meetings, calling, and file co-authoring.
- Governance and retention requirements that increase costs; if Teams or another suite meets compliance needs under existing agreements, migration pressure increases.
- Deal-breakers and reasons customers didn't purchase
- If an organization requires a single-suite approach (meetings, telephony, co-authoring, chat) under a single vendor contract, Slack may be perceived as an additional application to manage.
- If self-hosting or air-gapped deployment is required, Slack is generally not positioned as a sovereign self-hosted solution; alternatives such as Mattermost are typically considered for those requirements.
