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 Infobip — 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.
A CPaaS rebuilding around AI agents that act, not just channels that deliver
Infobip publishes quarterly roll-ups, and the feed stores each quarter twice — once as a bare label, once as the summary paragraph. Across Q3 2025 to Q1 2026 the through-line is consistent: AgentOS unifying the communication stack, AI agents that take action rather than reply, MCP servers connecting models to real channels, and AI voice work under Vocalize, against continued WhatsApp, RCS and CDP investment.
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.
Infobip publishes quarterly roll-ups, and the feed stores each quarter twice — once as a bare label, once as the summary paragraph. Across Q3 2025 to Q1 2026 the through-line is consistent: AgentOS unifying the communication stack, AI agents that take action rather than reply, MCP servers connecting models to real channels, and AI voice work under Vocalize, against continued WhatsApp, RCS and CDP investment.
The company is repositioning from delivering messages to running autonomous customer interactions on top of them. Channels are becoming the substrate; the product being sold is the agent layer above. MCP servers matter most here — they make Infobip's channel reach callable by models a customer already runs, rather than requiring Infobip's own agent builder.
Expect the next quarterly to lead with AgentOS depth — orchestration, handoff and measurement across agents — since the channel and MCP groundwork it needs has now shipped over three consecutive quarters.
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 Infobip.
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 Infobip alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within Support. Frill is currently shipping more aggressively (velocity 6.3 vs 0.0), 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 0.0), 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 Infobip alternatives in Support are ranked by recent ship velocity. Browse the "Infobip alternatives" section above for the current picks, or visit /alternatives/infobip for the full list with editorial commentary on each.