NanoMQ
A protocol-layer correctness pass, delivered largely by first-time contributors
A side-by-side editorial comparison of Chatwoot and Fellow — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Chatwoot | Fellow |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | customer-support, ai-agents, voice, routing | meeting management, calendar integration, stale changelog, external sharing |
| Last editorial update | 17h ago | 3mo 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.
Fellow's public changelog has been silent since 2021 — no recent direction is observable here.
The visible signal stops in spring 2021. The last few releases were calendar-extension touch-ups: action items appearing directly in the Google Calendar extension, public view-only meeting links for external attendees, and multi-calendar sync within a single Google or Office account. Nothing in this dataset reflects the past several years of Fellow's actual work.
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.
The visible signal stops in spring 2021. The last few releases were calendar-extension touch-ups: action items appearing directly in the Google Calendar extension, public view-only meeting links for external attendees, and multi-calendar sync within a single Google or Office account. Nothing in this dataset reflects the past several years of Fellow's actual work.
From the entries alone, no current trajectory can be inferred — the data is years stale. Whether Fellow has shifted to AI-meeting-notes or remained focused on the original meeting-management surface is not visible here and would be guesswork to assert.
Predictions can't be grounded in this data. The most useful next step is to refresh Fellow's changelog source so that present-day moves are captured.
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 Fellow.
A protocol-layer correctness pass, delivered largely by first-time contributors
The RocksDB migration reaches native code as the legacy DLedger broker mode is marked for removal
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
See all Chatwoot alternatives → · See all Fellow 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 Fellow alternatives in Comms are ranked by recent ship velocity. Browse the "Fellow alternatives" section above for the current picks, or visit /alternatives/fellow for the full list with editorial commentary on each.