Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
A side-by-side editorial comparison of Live Helper Chat and Xurrent — release velocity, themes, recent moves, and the top alternatives to consider.
Live Helper Chat keeps building the supervisor's view: who is offline, why, and how the team performed.
Live Helper Chat ships a version roughly every four to six weeks, and the last half-year has gone almost entirely into operator management and measurement. Operators can now select a reason when going offline, backed by a new model, CRUD interface, and permission, with those reasons surfacing in online-hours statistics. That sits on top of performance dashboard widgets, a cron aggregator writing to a dedicated statistics table, and offline-time tracking added to agent stats.
Sera AI crosses from assistant to autonomous agent while the ITSM core keeps its monthly grind.
Xurrent ships on a disciplined monthly cadence, and the last quarter splits cleanly in two. One half is steady ITSM plumbing — shared tags across Requests, Problems, Workflows and Projects, CMDB reconciliation that a human can actually read, iPaaS connectors, self-service reservations. The other half is Sera AI, which moved from a chat widget to a configurable studio and then, on 10 July, to two agents that act without a person in the loop.
Live Helper Chat ships a version roughly every four to six weeks, and the last half-year has gone almost entirely into operator management and measurement. Operators can now select a reason when going offline, backed by a new model, CRUD interface, and permission, with those reasons surfacing in online-hours statistics. That sits on top of performance dashboard widgets, a cron aggregator writing to a dedicated statistics table, and offline-time tracking added to agent stats.
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 forms module got the same treatment this cycle: search, filtering, and an audit trail on operator edits.
Expect the next releases to continue extending statistics and permissions into the modules that have not received them yet, following the pattern where a feature gains filtering, then history, then its own permission. Nothing in these entries points toward AI or automation work.
Xurrent ships on a disciplined monthly cadence, and the last quarter splits cleanly in two. One half is steady ITSM plumbing — shared tags across Requests, Problems, Workflows and Projects, CMDB reconciliation that a human can actually read, iPaaS connectors, self-service reservations. The other half is Sera AI, which moved from a chat widget to a configurable studio and then, on 10 July, to two agents that act without a person in the loop.
The two tracks are converging rather than running in parallel. Knowledge article readiness, CI location hints and reconciliation legibility are not standalone features — they are the data-quality preconditions an agent needs before it can be trusted to close a request. Xurrent is building the substrate first and letting Sera consume it, which is why the agent work has landed without the usual rollback noise. Agent Designer success metrics suggest the next constraint is proving the agents work, not shipping more of them.
Expect the agent count to grow slowly and the governance surface around it to grow faster — more Golden Set tooling, more per-agent success reporting, and tighter scoping of which request types an agent may close unaided.
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 Live Helper Chat or Xurrent.
Plain built an autonomous support agent, and has now built the controls to trust it.
Sleekplan rebuilt itself around AI triage, then put the feedback board inside ChatGPT.
Comm100 publishes steadily about AI support — none of it is Comm100 shipping anything.
respond.io is layering an agent-authoring copilot and consumption billing on top of its omnichannel inbox.
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 Live Helper Chat alternatives → · See all Xurrent alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Xurrent is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Xurrent is currently shipping more aggressively (velocity 6.3 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Support products to evaluate alongside.
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.
Top Xurrent alternatives in Support are ranked by recent ship velocity. Browse the "Xurrent alternatives" section above for the current picks, or visit /alternatives/xurrent for the full list with editorial commentary on each.