Zoho Cliq
Cliq 7.0 stops being a destination app and becomes a layer across Zoho
A side-by-side editorial comparison of Chatwoot and Matrix Bridge — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Chatwoot | Matrix Bridge |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | customer-support, ai-agents, voice, routing | matrix, bridges, sdk, dependency-tracking |
| Last editorial update | 5h ago | 14d ago |
| Website | — | Visit → |
Chatwoot is making Captain something a support team can scope, schedule and hand back.
Captain, the AI agent, now has per-assistant Audience and Schedule settings: teams choose which customers it answers using contact and conversation attributes, and when it is available - anytime, during business hours, or outside them. Non-matching conversations route to the human Open queue instead. Voice, introduced in June, has its own Calls dashboard with filtering, per-call status and in-place recordings, and reporting charts lead from a metric to the conversations behind it.
A bridge library whose releases are mostly its dependencies moving underneath it.
matrix-appservice-bridge releases a few times a year, and the content is dominated by keeping in step with matrix-bot-sdk, the Node support matrix, and whatever Matrix spec proposals homeservers have started enforcing. The last two years produced one behavioural fix that bridge operators would notice — registration failing when MSC4190 is enabled — plus authenticated media support and a media endpoint correction.
Captain, the AI agent, now has per-assistant Audience and Schedule settings: teams choose which customers it answers using contact and conversation attributes, and when it is available - anytime, during business hours, or outside them. Non-matching conversations route to the human Open queue instead. Voice, introduced in June, has its own Calls dashboard with filtering, per-call status and in-place recordings, and reporting charts lead from a metric to the conversations behind it.
The pattern is consolidation: each release takes something already shipped and adds the surface a daily operator needs. With Captain that has meant answer quality first, then self-maintaining documents, and now deployment controls - the settings that decide whether an AI agent can be switched on in production at all. The after-hours configuration is the telling one, positioning Captain as coverage for the hours a team is not staffed rather than as a replacement for it.
Voice remains the thread with a dashboard but no automation - neither workflow triggers nor Captain participation - and the Audience and Schedule model is the obvious shape to extend there next.
matrix-appservice-bridge releases a few times a year, and the content is dominated by keeping in step with matrix-bot-sdk, the Node support matrix, and whatever Matrix spec proposals homeservers have started enforcing. The last two years produced one behavioural fix that bridge operators would notice — registration failing when MSC4190 is enabled — plus authenticated media support and a media endpoint correction.
This is infrastructure code, and it behaves like it: no feature narrative, no roadmap visible in the changelog, just alignment work. What movement there is comes from the Matrix specification rather than the library — authenticated media and MSC4190 both arrived because homeservers changed, not because the bridge SDK set out to add something. Major version bumps here signal dropped Node versions rather than new capability.
The next releases will most likely track matrix-bot-sdk versions and Node LTS transitions, with any user-visible change arriving as a response to a homeserver-side spec change rather than as new bridge functionality.
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 Matrix Bridge.
Cliq 7.0 stops being a destination app and becomes a layer across Zoho
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
Element Web is opening an extension surface while rebuilding its timeline underneath.
Signal's beta train keeps trickling small comfort settings between maintenance drops
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
Krisp is selling real-time voice manipulation to contact centers, and the defense against it too.
See all Chatwoot alternatives → · See all Matrix Bridge 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 6.3 vs 0.0), with 1 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 6.3 vs 0.0), with 1 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 Matrix Bridge alternatives in Comms are ranked by recent ship velocity. Browse the "Matrix Bridge alternatives" section above for the current picks, or visit /alternatives/matrix-appservice-bridge for the full list with editorial commentary on each.