← Back to home
Comparison · Comms

Chatwoot vs Slack

A side-by-side editorial comparison of Chatwoot and Slack — release velocity, themes, recent moves, and the top alternatives to consider.

Chatwoot vs Slack: at a glance

FeatureChatwootSlack
SectorCommsComms, Collab
Velocity score7.56.3
Sparks · 30d01
Top themesai-assistant, customer-support, whatsapp, voice-callingagents, a2a, mcp, slackbot-skills
Last editorial update1mo ago3d ago
Website—Visit →

What is Chatwoot?

Chatwoot retires Captain V1 and rebuilds its AI assistant as a structured, per-assistant behavior system.

Chatwoot is in the middle of a significant architectural transition for its AI assistant layer. The original Captain V1 (free-form instructions) is being retired in the next self-hosted release in favor of a structured model with scenarios, response guidelines, guardrails, and a testing playground. Cloud users are already on the new system. Alongside this, two substantial releases expanded Captain's control surface: per-assistant custom tools, inactivity handling, and audience/schedule targeting. WhatsApp BSUID support and improved call recording controls round out a busy month in the communications layer.

Read the full Chatwoot trajectory →

What is Slack?

Slack now hosts any A2A agent without Slack-specific code.

Slack's developer channel is almost all agent plumbing. On 10 November Slack became an A2A (Agent2Agent) client: a team hosts its own agent, publishes an Agent Card, and Slack calls it when people talk to it, with no request URL, event handling or Slack-specific logic. This follows Slackbot skills managed through Web API methods, a Slack CLI that points coding agents to the Slack MCP server, and a new requirement that Work Objects embeds allow the slack-mcps.com frame ancestor.

Read the full Slack trajectory →

Chatwoot vs Slack: editorial side-by-side

C7.5

Chatwoot retires Captain V1 and rebuilds its AI assistant as a structured, per-assistant behavior system.

◆ Current state

Chatwoot is in the middle of a significant architectural transition for its AI assistant layer. The original Captain V1 (free-form instructions) is being retired in the next self-hosted release in favor of a structured model with scenarios, response guidelines, guardrails, and a testing playground. Cloud users are already on the new system. Alongside this, two substantial releases expanded Captain's control surface: per-assistant custom tools, inactivity handling, and audience/schedule targeting. WhatsApp BSUID support and improved call recording controls round out a busy month in the communications layer.

◆ Where it's heading

Chatwoot is shifting Captain from a chatbot add-on into a proper automation layer with auditable, testable behavior. Per-assistant tool isolation, audience segmentation, and schedule-based availability bring it closer to the model used by Intercom Fin and Zendesk AI. The V1 retirement removes a backward-compatibility constraint that was slowing this transition. The playground — which lets admins test assistant configurations before saving — removes the need to test in production, which was the practical barrier to iterating on Captain.

◆ Prediction

The next likely move is a reporting layer for Captain — tracking resolution rates, handoff rates, and scenario effectiveness per assistant. The playground's 'Run details' view (showing which scenario handled a message and which tools ran) is the building block for that kind of analytics.

Slack logo
Slack
COMMSCOLLAB
6.3

Slack now hosts any A2A agent without Slack-specific code.

◆ Current state

Slack's developer channel is almost all agent plumbing. On 10 November Slack became an A2A (Agent2Agent) client: a team hosts its own agent, publishes an Agent Card, and Slack calls it when people talk to it, with no request URL, event handling or Slack-specific logic. This follows Slackbot skills managed through Web API methods, a Slack CLI that points coding agents to the Slack MCP server, and a new requirement that Work Objects embeds allow the slack-mcps.com frame ancestor.

◆ Where it's heading

Slack is lowering the cost of putting outside agents in front of its users: first skills as code, then MCP pointers for coding agents, now a standard protocol in place of the Slack app model for agents. The platform is positioning itself as the place where agents built anywhere meet the people who use them.

◆ Prediction

Expect more A2A follow-ups, such as agents appearing in Slackbot or skills surfaces and richer Agent Card features, given how fast the agent releases have stacked up since October.

Alternatives to Chatwoot and Slack

Other Comms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Chatwoot or Slack.

See all Chatwoot alternatives → · See all Slack alternatives →

Recent activity from Chatwoot and Slack

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoSlackBring your A2A agents to Slack ⚡
  2. 8d agoSlackWork Objects embeds require the slack-mcps.com frame ancestor
  3. 10d agoSlackSlack CLI 4.13 tells coding agents about Slack MCP and Skills
  4. 10d agoSlackSlack Skills Plugin installs in Claude Code from its own marketplace
  5. 12d agoSlackUpdated low-usage submission criteria for Slack Marketplace apps
  6. 15d agoSlackSlack CLI 4.12.0, the fourth CLI release in October
  7. 1mo agoChatwootCaptain V1 is retiring: every account moves to the new Captain ⚡
  8. 1mo agoChatwootMore control over Captain Assistant behaviour ⚡
  9. 1mo agoChatwootImproved Help Center media uploads
  10. 2mo agoChatwootSupport for WhatsApp usernames and BSUIDs
  11. 2mo agoChatwootDecide when calls are recorded and transcribed
  12. 2mo agoChatwootGuided manual setup for WhatsApp inboxes

Frequently asked questions

What is the difference between Chatwoot and Slack?

They serve adjacent needs but don't currently overlap on shipped themes. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 6.3), with 0 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Chatwoot better than Slack?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 6.3), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.

What are the best alternatives to Chatwoot?

Top Chatwoot alternatives in Comms are ranked by recent ship velocity. Browse the "Chatwoot alternatives" section above for the current picks, or visit /alternatives/chatwoot for the full list with editorial commentary on each.

What are the best alternatives to Slack?

Top Slack alternatives in Comms are ranked by recent ship velocity. Browse the "Slack alternatives" section above for the current picks, or visit /alternatives/slack for the full list with editorial commentary on each.