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 HelpCenter.io — 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.
HelpCenter.io is building a funnel off Zendesk's weak spots — a free FAQ tool at one end, migration guides at the other.
The newest post is a migration playbook aimed squarely at Zendesk customers, arguing that Zendesk has no native article export and that its URLs stop working when the subscription does. That editorial sits on top of a genuine product run: FAQs.me, a standalone free FAQ builder with no account, watermark, or callback scripts; Template Editor v2 for per-page design control; a rebuilt support widget whose AI answers cite their sources; and analytics rebuilt to report a self-service resolution rate.
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.
The newest post is a migration playbook aimed squarely at Zendesk customers, arguing that Zendesk has no native article export and that its URLs stop working when the subscription does. That editorial sits on top of a genuine product run: FAQs.me, a standalone free FAQ builder with no account, watermark, or callback scripts; Template Editor v2 for per-page design control; a rebuilt support widget whose AI answers cite their sources; and analytics rebuilt to report a self-service resolution rate.
The pieces fit into one motion. FAQs.me and the migration content both bring people in without a sales conversation, the widget and template work make the product worth keeping, and the analytics rebuild supplies the number that justifies it. The company is targeting switchers rather than new buyers, and the argument it makes is about lock-in — export and URL ownership — rather than features. Content and product are being pointed at the same competitor.
Expect more migration material covering other incumbents, and for the resolution-rate metric to become the number the product is sold on. Whether FAQs.me converts into paid accounts is the open question, and nothing visible here reports on it yet.
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 HelpCenter.io.
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 HelpCenter.io alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Frill and HelpCenter.io 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 HelpCenter.io 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 HelpCenter.io alternatives in Support are ranked by recent ship velocity. Browse the "HelpCenter.io alternatives" section above for the current picks, or visit /alternatives/helpcenter-io for the full list with editorial commentary on each.