Element
Element 1.12.33 ships: simpler recovery keys, mandatory verification, no libolm migration.
A side-by-side editorial comparison of Chatwoot and Fonoster — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Chatwoot | Fonoster |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 7.5 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | ai-assistant, customer-support, whatsapp, voice-calling | programmable-voice, sip, twilio, open-source |
| Last editorial update | 1mo ago | 14h 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.
Fonoster ships four releases in a day to make linking a Twilio number a single step.
Fonoster went from v0.35 to v0.38.1 on October 28. The thread is Twilio: trunk provisioning for a number link is now idempotent, a Twilio number can be linked to an app or SIP agent in one API call, linking moved server-side with an API key or Auth Token (a breaking change), and the Numbers page can do it from the UI. v0.35 also lets Routr be configured through routr-one.yaml.
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.
Fonoster went from v0.35 to v0.38.1 on October 28. The thread is Twilio: trunk provisioning for a number link is now idempotent, a Twilio number can be linked to an app or SIP agent in one API call, linking moved server-side with an API key or Auth Token (a breaking change), and the Numbers page can do it from the UI. v0.35 also lets Routr be configured through routr-one.yaml.
After rebuilding its SIP and media edge and defaulting to HTTPS in the 0.31 to 0.33 run, Fonoster is now working on onboarding, using Twilio as the way to bring an existing number. The release rate stays very high and breaking changes still land in minor versions.
Expect the same number-linking flow for other carriers, or more Numbers page work; the entries only cover Twilio so far.
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 Fonoster.
Element 1.12.33 ships: simpler recovery keys, mandatory verification, no libolm migration.
tawk.to's widget 4.4.0 turns to keyboard and screen-reader fixes after a run of form work.
Krisp 2.83.4 brings Voice Translation into conference calls and lightens Accent Conversion.
Pixelfed 0.15.2 ships the PHP RCE patches and turns cached timelines on for everyone.
Salesmsg Reviews can now trigger follow-ups automatically based on a customer's latest rating.
Netcore keeps publishing competitor comparisons and ecommerce posts after its Orbit launch.
See all Chatwoot alternatives → · See all Fonoster alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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 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 6.3), with 0 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 Fonoster alternatives in Comms are ranked by recent ship velocity. Browse the "Fonoster alternatives" section above for the current picks, or visit /alternatives/fonoster for the full list with editorial commentary on each.