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 Formbricks — 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.
Formbricks spends a whole RC train on making enterprise SSO stop breaking.
The 5.4 branch is deep in RC hardening and the subject is authentication. Three release candidates landed on 28 August, each a cumulative restatement of the last: Microsoft multi-tenant authorities failing on both native SSO and generic OIDC, local auth factors surviving an SSO recovery, OAuth state rejections no longer paging on-call, and MCP OAuth resource seeding made recoverable. The one piece of new capability is observability — every SSO callback outcome is now recorded.
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 5.4 branch is deep in RC hardening and the subject is authentication. Three release candidates landed on 28 August, each a cumulative restatement of the last: Microsoft multi-tenant authorities failing on both native SSO and generic OIDC, local auth factors surviving an SSO recovery, OAuth state rejections no longer paging on-call, and MCP OAuth resource seeding made recoverable. The one piece of new capability is observability — every SSO callback outcome is now recorded.
The substance of 5.4 shipped in 5.4.0-rc.1 — metered workflow runs, Hub feedback filters, the unify-feedback surface — and everything since is the cost of that release meeting real identity providers. Nearly all of it is backported by a single engineer, which suggests a branch being nursed to a final rather than a team still building. Notably the MCP OAuth path is now being maintained alongside human SSO, so agent access is carrying the same auth burden as user access.
The pattern points at a 5.4.1 final once the multi-tenant fixes stop arriving, with the new SSO callback telemetry the most likely source of the next round of fixes. Substantive product work should resume on the Hub and the metered workflow_runs price rather than on this branch.
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 Formbricks.
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.
Hatz pulls its training platform off TalentLMS and runs it inside the tenant.
Twilio keeps absorbing the plumbing customers used to run themselves — certificates, migrations, consent state.
See all Chatway alternatives → · See all Formbricks alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Chatway is currently shipping more aggressively (velocity 6.3 vs 5.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. Chatway is currently shipping more aggressively (velocity 6.3 vs 5.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 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 Formbricks alternatives in Support are ranked by recent ship velocity. Browse the "Formbricks alternatives" section above for the current picks, or visit /alternatives/formbricks for the full list with editorial commentary on each.