Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
A side-by-side editorial comparison of Frill and Xurrent — release velocity, themes, recent moves, and the top alternatives to consider.
Frill is turning its feedback board from a destination into something machines read on demand.
The MCP server is the centrepiece: ten tools, one API key, no configuration, callable from Claude, ChatGPT, Cursor or Intercom Fin, and included on every plan rather than gated. The Chrome extension follows the same instinct from the capture side — grab an idea wherever you spot it, and collapse a long help desk thread into a clean idea with an AI summary in one click. Behind both sits the June groundwork: a public npm SDK, multiple API keys, webhook handling, and MCP in public beta.
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.
The MCP server is the centrepiece: ten tools, one API key, no configuration, callable from Claude, ChatGPT, Cursor or Intercom Fin, and included on every plan rather than gated. The Chrome extension follows the same instinct from the capture side — grab an idea wherever you spot it, and collapse a long help desk thread into a clean idea with an AI summary in one click. Behind both sits the June groundwork: a public npm SDK, multiple API keys, webhook handling, and MCP in public beta.
Frill is systematically removing the requirement to be in Frill. Capture moves to wherever the conversation already happens; retrieval moves to whatever assistant the team already uses. That reframes the product as the feedback store rather than the feedback interface, and the pricing decision reinforces it — putting MCP on every plan optimises for the corpus being queried, not for upsell. The earlier enterprise work (EU hosting, EntraID SSO, CSP) is what makes that store trustworthy enough to hold the data.
Expect write paths to follow the read paths — an assistant that can already ask what users want will next be expected to file, merge and status ideas — and expect more capture surfaces beyond the browser extension.
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 Frill 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 Frill alternatives → · See all Xurrent alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within Support. Frill and Xurrent are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. Frill and Xurrent are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Support products to evaluate alongside.
Top Frill alternatives in Support are ranked by recent ship velocity. Browse the "Frill alternatives" section above for the current picks, or visit /alternatives/frill 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.