Respond.io
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
A side-by-side editorial comparison of LiveAgent and Live Helper Chat — release velocity, themes, recent moves, and the top alternatives to consider.
Two maintained branches, a build-stamp version scheme, and a steady diet of defect fixes.
LiveAgent ships from two branches at once, 5.67 and 5.66, and tags each build with a timestamped version string rather than a release name. The window is almost entirely defect work: chat lifecycle bugs, a shared-mailbox OAuth timeout on large tenants, Gmail quote parsing, and several database write loops. The most recent pair are same-day builds on both branches carrying an overlapping fix set.
Live Helper Chat keeps adding the oversight surfaces a supervised support floor needs.
Two releases landed together. 4.89v makes the online-operators dashboard widget configurable - a settings screen under Statistics with its own onlineop_settings permission, selectable and orderable columns, restored expand/collapse, and column control from the embed code - and starts recording which operator set a user offline. 4.90v completes the pair on the other side, adding an online_by_user_id column and a 'Set online by' column in online-hours statistics. Both ship raw SQL migrations operators run by hand.
LiveAgent ships from two branches at once, 5.67 and 5.66, and tags each build with a timestamped version string rather than a release name. The window is almost entirely defect work: chat lifecycle bugs, a shared-mailbox OAuth timeout on large tenants, Gmail quote parsing, and several database write loops. The most recent pair are same-day builds on both branches carrying an overlapping fix set.
The recent fixes have shifted from user-visible bugs toward the cost of running the system: a chats overview that re-ran a full grid query every ten seconds per open screen, a language synchroniser writing on every read, and uncached language metadata. That is a performance pass on hot paths rather than feature work. The dual-branch pattern is stable, with the older 5.66 line receiving a subset of each fix set as backports.
Expect the branch pair to continue, with 5.66 receiving narrower backports of whatever 5.67 fixes, and further work on query and write amplification now that three such issues have been addressed in one build.
Two releases landed together. 4.89v makes the online-operators dashboard widget configurable - a settings screen under Statistics with its own onlineop_settings permission, selectable and orderable columns, restored expand/collapse, and column control from the embed code - and starts recording which operator set a user offline. 4.90v completes the pair on the other side, adding an online_by_user_id column and a 'Set online by' column in online-hours statistics. Both ship raw SQL migrations operators run by hand.
This is a self-hosted product being fitted out for teams large enough to need oversight. Each release adds another measurement or access-control surface - permissions on features, field change tracking on forms, participant-aware exports, per-operator performance snapshots - rather than reaching for new channels or assistive features. The current pair extends that to operator presence itself: who set whom online or offline is now attributable, which only matters where someone is accountable for floor coverage. The feature-then-permission-then-statistic sequence repeats almost every release.
Expect statistics and permissions to keep extending into the modules that have not received them yet, following the same feature-then-filtering-then-permission order; nothing in these entries points toward AI or automation work.
Other Support 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 LiveAgent or Live Helper Chat.
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
Post-rebuild Sleekplan is adding the objects a feedback board never had: docs and components.
Plain built an autonomous support agent, and has now built the controls to trust it.
Comm100 publishes steadily about AI support — none of it is Comm100 shipping anything.
Hatz sells through MSPs, and its roadmap has started to serve the partner more than the end user
A teaser-only content feed making one argument: AI in the contact center fails on knowledge, not models.
See all LiveAgent alternatives → · See all Live Helper Chat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — live-chat — within Support. LiveAgent and Live Helper Chat are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. LiveAgent and Live Helper Chat are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Support products to evaluate alongside.
Top LiveAgent alternatives in Support are ranked by recent ship velocity. Browse the "LiveAgent alternatives" section above for the current picks, or visit /alternatives/liveagent for the full list with editorial commentary on each.
Top Live Helper Chat alternatives in Support are ranked by recent ship velocity. Browse the "Live Helper Chat alternatives" section above for the current picks, or visit /alternatives/livehelperchat for the full list with editorial commentary on each.