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 INKY — 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.
INKY is wiring an LLM into email security while binding itself tighter to Kaseya.
INKY ships a dashboard release every one to two weeks, moving from 1.8.5 to 1.9.5 since May. The functional center is the Triage workspace, which pulled detection review, message actions and account-takeover enforcement into one place and made ATO configurable without a SIEM. July added Smart Insights, an LLM second opinion on inbound mail, plus automatic Autotask ticketing. Running alongside the security work, email-signature management has grown from a single page in June into a tabbed editor with per-field styling.
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.
INKY ships a dashboard release every one to two weeks, moving from 1.8.5 to 1.9.5 since May. The functional center is the Triage workspace, which pulled detection review, message actions and account-takeover enforcement into one place and made ATO configurable without a SIEM. July added Smart Insights, an LLM second opinion on inbound mail, plus automatic Autotask ticketing. Running alongside the security work, email-signature management has grown from a single page in June into a tabbed editor with per-field styling.
Two threads are pulling in the same direction. Detection is becoming AI-assisted and explainable, with Smart Insights returning a verdict, a trickiness rating and a written rationale rather than a score. And the managed-service channel is being deepened at every layer — Autotask billing, Autotask ticketing, Kaseya-provisioned entitlements, a third-party training platform slotted in as an option. INKY is optimizing for the provider reselling it across many tenants, not the employee reading the mail.
Smart Insights is gated to Pro with a per-team opt-out, which points to it being extended and monetized further rather than made universal. Mesh was added as a recognized upstream provider under an auto-detect setting, so additional relay providers are the obvious continuation of that 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 INKY.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Frill and INKY 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 INKY 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 INKY alternatives in Support are ranked by recent ship velocity. Browse the "INKY alternatives" section above for the current picks, or visit /alternatives/inky for the full list with editorial commentary on each.