Fonoster
Fonoster parks its Deepgram diarization work after two 0.22.x stability patches.
A side-by-side editorial comparison of Chatwoot and Heymarket — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Chatwoot | Heymarket |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 7.5 | 5.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | ai-assistant, customer-support, whatsapp, voice-calling | business-messaging, conversational-ai, customer-support, rcs |
| Last editorial update | 18d ago | 1mo ago |
| Website | — | Visit → |
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.
Heymarket's feed argues for conversational AI without confirming it ships any.
Seven entries, all explainer content: conversational AI in retail, multilingual support, chatbot versus conversational AI, AI data enrichment, RCS versus SMS, and shared inboxes. Bodies are truncated after roughly two sentences, so each entry gives a scenario and a promise with the substance behind a link. Nothing here is a release note.
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.
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.
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.
Seven entries, all explainer content: conversational AI in retail, multilingual support, chatbot versus conversational AI, AI data enrichment, RCS versus SMS, and shared inboxes. Bodies are truncated after roughly two sentences, so each entry gives a scenario and a promise with the substance behind a link. Nothing here is a release note.
The topic mix has shifted decisively toward AI handling inbound messages rather than routing them to people — repetitive retail questions, languages the team doesn't speak, after-hours requests. That is a clear statement of where Heymarket wants to compete in business messaging. Whether its own product does these things, or the posts are describing the category, cannot be resolved from these entries.
Expect the AI-support content to continue and RCS coverage to expand as carrier support broadens. A claim about Heymarket's actual capabilities would need the full articles, which this feed truncates.
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 Heymarket.
Fonoster parks its Deepgram diarization work after two 0.22.x stability patches.
Element 1.12.32 cuts guest access tokens and NEB starter links to close two advisories.
Element X Android turns on multi-account and global search in its biggest release in months.
Netcore follows its Orbit email launch with more retail content and no new product change.
Pixelfed's 0.15 candidate adds an account-delete API and drops PHP 8.3.
Salesmsg lists its MCP server with Claude and ChatGPT, so texting runs from the assistant.
See all Chatwoot alternatives → · See all Heymarket alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — customer-support — within Comms. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
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.
Top Heymarket alternatives in Comms are ranked by recent ship velocity. Browse the "Heymarket alternatives" section above for the current picks, or visit /alternatives/heymarket for the full list with editorial commentary on each.