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 Re:amaze — 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.
Re:amaze matures its AI support agent with testing and visibility tools
Re:amaze is a customer-support helpdesk centering its roadmap on its AI Agent. Genuine product posts — multichannel AI Agent across email and SMS, smarter intent detection, and a new set of AI-agent visibility and testing tools — sit interleaved with SEO blog content like help-center writing tips and Prime Day prep. The product is steadily hardening an AI support agent it launched in January 2026.
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.
Re:amaze is a customer-support helpdesk centering its roadmap on its AI Agent. Genuine product posts — multichannel AI Agent across email and SMS, smarter intent detection, and a new set of AI-agent visibility and testing tools — sit interleaved with SEO blog content like help-center writing tips and Prime Day prep. The product is steadily hardening an AI support agent it launched in January 2026.
The arc is consistent: launch the AI Agent, then make it broad and trustworthy. Re:amaze has moved from clearer conversation states to sharper intent detection, to email and SMS coverage, and now to observability and testing so teams can see and validate how the agent behaves before handing it real volume. The recurring blog question — how much support AI should handle — mirrors where the product is steering customers.
Expect continued AI-Agent depth: more channels, deeper analytics on agent performance, and controls governing how much volume teams delegate to automation.
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 Re:amaze.
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 Re:amaze 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 Re:amaze 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 Re:amaze 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 Re:amaze alternatives in Support are ranked by recent ship velocity. Browse the "Re:amaze alternatives" section above for the current picks, or visit /alternatives/reamaze for the full list with editorial commentary on each.