Help Scout vs Slack
Side-by-side trajectory, velocity, and editorial themes.
Help Scout adds SLAs, presence-aware routing, and WhatsApp — the shared inbox grows enterprise teeth.
Help Scout's recent stream centers on operational discipline. SLAs landed in April with response and resolution timers in the inbox, then immediately deepened with SLA-specific views for upcoming, due-soon, and breached conversations. Presence is now first-class: availability auto-updates from app activity, custom status messages add context, and Routing only assigns to Active teammates. The platform also broadened: WhatsApp arrived as a native inbox channel in March, an Aircall call-context integration shipped in January, and AI Agents can now pull from Google Docs and Sheets as knowledge sources. An auto-redaction feature for sensitive customer data is queued for April GA.
The team is shifting Help Scout from a friendly shared inbox toward a measurable support operations product — SLAs and presence-aware routing both presume a manager looking at throughput numbers. Channel breadth (WhatsApp, Aircall) and AI knowledge expansion (Google Docs) make the inbox the consolidation point regardless of where the customer started, which positions Help Scout to compete more directly against Intercom, Front, and lower-end Zendesk deployments. The redaction feature signals the company is also taking compliance more seriously, likely in response to mid-market sales motions.
Expect Help Scout to ship SLA reporting beyond the inbox view — dashboard-level breach trends, per-customer SLA contracts — and a richer routing engine that uses skills and historical performance, not just availability. WhatsApp GA polish (templates, broadcast outbound) is a likely near-term follow-on.
Slack rebuilds its developer platform around shipping in-channel AI agents.
Slack is well into a platform pivot, restructuring its CLI, Block Kit, and APIs around AI agent use cases. The 4.0.0 release in April formalized this with an agent-scaffolding command, sample agent apps, and a live-reloading dev workflow. Recent additions — streaming chat APIs, Card/Carousel/Alert blocks, and continued MCP server expansion — show the surface area for in-Slack agents widening fast.
The platform is shifting from 'agents can post messages' to 'agents are first-class UI citizens'. The new chat.startStream / chat.appendStream / chat.stopStream methods change what an agent reply looks like, and the Card and Carousel blocks hint at richer multi-turn agent flows. Security work on PKCE and optional scopes is keeping pace, which tells you third-party agent developers are the audience, not just first-party features.
Expect Slack to publish reference agents and likely a discovery or marketplace surface for agent apps within the next minor cycle, with streaming Block Kit becoming the canonical pattern shown in the docs.
See more alternatives to Help Scout →
See more alternatives to Slack →