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 Live Helper Chat — 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.
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.
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.
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.
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 Live Helper Chat.
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 Live Helper Chat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Frill is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Frill is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 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 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.