Sleekplan
Sleekplan is making the public feedback board safe to run with real customers on it
A side-by-side editorial comparison of Chatway and Frill — release velocity, themes, recent moves, and the top alternatives to consider.
Chatway's bot learned to read the store; now the store can listen back
Chatway is a live chat widget for small e-commerce sites, weighted toward WooCommerce and Shopify, with an AI support agent attached. The last three weeks added the two things that decide when and where the agent operates: webhooks that push conversation, contact, assignment and resolution events out to external tools from the existing Developer Tools panel, with per-event subscriptions and delivery logs; and AI Availability settings that schedule the agent by weekly time range, timezone and special dates rather than leaving it always on. Underneath, self-service and routing shipped earlier in August.
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.
Chatway is a live chat widget for small e-commerce sites, weighted toward WooCommerce and Shopify, with an AI support agent attached. The last three weeks added the two things that decide when and where the agent operates: webhooks that push conversation, contact, assignment and resolution events out to external tools from the existing Developer Tools panel, with per-event subscriptions and delivery logs; and AI Availability settings that schedule the agent by weekly time range, timezone and special dates rather than leaving it always on. Underneath, self-service and routing shipped earlier in August.
The product keeps widening from a widget into a support stack, and the recent work is about control and connection rather than new answering ability. The August spark grounded the AI agent in live store data; since then Chatway has added the Help Center it can point to, routing that decides who takes a conversation, an outbound event stream so other systems can react, and now a schedule that says when the AI is allowed to be the one responding. The consistent thread is that merchants are being given switches over an agent they were first given a reason to trust.
With events flowing out and a schedule governing the agent, the obvious next gap is inbound control — triggering Chatway actions from outside, or handing off to a human on a rule rather than a reply. The entries do not indicate which, and no API beyond webhooks is mentioned.
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.
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 Chatway or Frill.
Sleekplan is making the public feedback board safe to run with real customers on it
ServiceDesk Plus moved upstream of the ticket, then spent the week tidying the sidebar
ManageEngine's cloud service desk drips small fixes; its AI arrives data center by data center
Asset management is the real build; the feed is mostly an interview series.
Formbricks spends a whole RC train on making enterprise SSO stop breaking.
Hatz pulls its training platform off TalentLMS and runs it inside the tenant.
See all Chatway alternatives → · See all Frill alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Chatway and Frill 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. Chatway and Frill 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 Chatway alternatives in Support are ranked by recent ship velocity. Browse the "Chatway alternatives" section above for the current picks, or visit /alternatives/chatway for the full list with editorial commentary on each.
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.