Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
Comparison · Support
LiveAgent vs Xurrent
A side-by-side editorial comparison of LiveAgent and Xurrent — release velocity, themes, recent moves, and the top alternatives to consider.
LiveAgent vs Xurrent: at a glance
What is LiveAgent?
LiveAgent is spending this window on scale defects, not on the AI surface it built in spring
Every release in the last six weeks is a build-stamped fix batch, and the failures being fixed are the kind that show up at tenant scale: a background ticket-search job crashing repeatedly on a deleted message record, a Facebook ticket poisoning its reindex batch forever with no dead-letter, a purge task full-scanning conversations fleet-wide, Microsoft shared-mailbox OAuth timing out on tenants with thousands of addresses. Work is being cut on two branches at once, 5.67.7 and 5.66.5, with the important fixes backported. Nothing in this window touches the MCP server or AI agent routing shipped in May and June.
What is Xurrent?
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.
LiveAgent vs Xurrent: editorial side-by-side
LiveAgent
5.0SUPPORT
LiveAgent is spending this window on scale defects, not on the AI surface it built in spring
◆ Current state
Every release in the last six weeks is a build-stamped fix batch, and the failures being fixed are the kind that show up at tenant scale: a background ticket-search job crashing repeatedly on a deleted message record, a Facebook ticket poisoning its reindex batch forever with no dead-letter, a purge task full-scanning conversations fleet-wide, Microsoft shared-mailbox OAuth timing out on tenants with thousands of addresses. Work is being cut on two branches at once, 5.67.7 and 5.66.5, with the important fixes backported. Nothing in this window touches the MCP server or AI agent routing shipped in May and June.
◆ Where it's heading
This is the consolidation phase after a fast AI push: the MCP server, AI Agent Work Distributor and per-agent auth tokens landed in spring, and the engineering attention has since moved to durability and to the integrations that feed the helpdesk. Maintaining a parallel 5.66 branch with backports indicates customers who will not move versions quickly, which slows how fast any of the newer AI surface actually reaches the base.
◆ Prediction
Expect the fix cadence to continue on both branches, with the next feature-carrying release most likely extending the existing MCP tool set rather than opening a new AI surface.
Xurrent
6.3SUPPORT
Sera AI crosses from assistant to autonomous agent while the ITSM core keeps its monthly grind.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to LiveAgent and Xurrent
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 Xurrent.
Sleekplan
Sleekplan rebuilt itself around AI triage, then put the feedback board inside ChatGPT.
Comm100
Comm100 publishes steadily about AI support — none of it is Comm100 shipping anything.
Respond.io
respond.io is layering an agent-authoring copilot and consumption billing on top of its omnichannel inbox.
Hatz AI
Hatz sells through MSPs, and its roadmap has started to serve the partner more than the end user
Knowmax
A teaser-only content feed making one argument: AI in the contact center fails on knowledge, not models.
See all LiveAgent alternatives → · See all Xurrent alternatives →
Recent activity from LiveAgent and Xurrent
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6d agoLiveAgentShared-mailbox OAuth timeout and chat completion fixes
- 8d agoLiveAgentChat lookup, pop-out, and ringing-agent fixes
- 13d agoLiveAgentGmail quote parsing, CRM notify, and ticket-integrity fixes
- 13d agoLiveAgentCRM notification fix backported to 5.66.5
- 13d agoXurrentKnowledge auto-translation and tag merging land in August
- 16d agoLiveAgentTicket-search crash fix backported to 5.66.5
- 16d agoLiveAgentTicket-search and reindex job durability fixes
- 16d agoXurrentQ3 2026 IMR updates open as a living document
- 27d agoXurrentMy Reservations self-service and Agent Designer success metrics
- 1mo agoXurrentShared tags span Requests, Problems, Workflows and Projects
- 1mo agoXurrentSera AI's first two autonomous agents ship ⚡
- 1mo agoXurrentGetting Started with Sera AI Studio
Frequently asked questions
What is the difference between LiveAgent and Xurrent?
They serve adjacent needs but don't currently overlap on shipped themes. Xurrent is currently shipping more aggressively (velocity 6.3 vs 5.0), 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.
Is LiveAgent better than Xurrent?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Xurrent is currently shipping more aggressively (velocity 6.3 vs 5.0), 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.
What are the best alternatives to LiveAgent?
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.
What are the best alternatives to Xurrent?
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.