Plain
Plain built an autonomous support agent, and has now built the controls to trust it.
A side-by-side editorial comparison of Forethought and Hatz AI — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Forethought | Hatz AI |
|---|---|---|
| Sector | Support | Support |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | ai-customer-support, browser-agents, agent-testing, orchestration | msp-channel, phone-agents, model-selector, multi-tenant-admin |
| Last editorial update | 3mo ago | 4d ago |
| Website | Visit → | — |
Forethought pivots from answering questions to executing outcomes via Orchestrator and Browser Agents.
Forethought is in the middle of a deliberate platform-narrative shift. April shipped two foundational pieces: Orchestrator, which routes business signals into deterministic AI actions across channels, and Browser Agents, which can take actions in apps that don't expose APIs. Test Suite landed alongside as the validation tooling for agent behavior before deployment. The CEO's 'Next Chapter' post frames the same direction in plain language: AI moving from answering to resolving.
Hatz sells through MSPs, and its roadmap has started to serve the partner more than the end user
Most of Hatz's window is model-selector maintenance — Claude Opus 5, Kimi K3, GLM 5.2 Fast, DeepSeek V4 Flash, the Gemini 3.x line — plus a steady buildout of the phone agent, which has gained pausing, duplication, reassignment, drafts, silence tolerance, business hours, and caller memory. Against that routine, Hatz Activate stands apart: a rollout console built for the managed service providers who resell the platform.
Forethought is in the middle of a deliberate platform-narrative shift. April shipped two foundational pieces: Orchestrator, which routes business signals into deterministic AI actions across channels, and Browser Agents, which can take actions in apps that don't expose APIs. Test Suite landed alongside as the validation tooling for agent behavior before deployment. The CEO's 'Next Chapter' post frames the same direction in plain language: AI moving from answering to resolving.
The company is repositioning from a customer-support intent and triage AI to an outcomes-execution layer for enterprise customer experience. Browser Agents are the bet that the long tail of CX work lives in apps without proper APIs — making the agent capable of clicking through them is the moat. Orchestrator and Test Suite are the deterministic-control and validation pieces that make this defensible enough for enterprise procurement.
Expect a tightening of the integration story — pre-built Browser Agent flows for common CX systems like Zendesk and Salesforce Service Cloud — and an explicit outcomes-priced packaging emerging over the next quarter as the company moves past per-seat or per-resolution pricing.
Most of Hatz's window is model-selector maintenance — Claude Opus 5, Kimi K3, GLM 5.2 Fast, DeepSeek V4 Flash, the Gemini 3.x line — plus a steady buildout of the phone agent, which has gained pausing, duplication, reassignment, drafts, silence tolerance, business hours, and caller memory. Against that routine, Hatz Activate stands apart: a rollout console built for the managed service providers who resell the platform.
Two arcs run in parallel. The phone agent is being hardened into a product an MSP can deploy repeatedly across client sites — duplicate it onto a new number, reassign it to a different tenant, cap its minutes — while Activate supplies the partner with the shadow-AI scan and enablement material that starts the sales conversation. Model additions continue but carry no direction; they are table stakes restated every few weeks.
Expect more tenant- and partner-scoped administration, since renaming tenants and invoicing over the API both landed this window and point at MSPs managing many clients programmatically. The phone agent's usage-based pricing suggests metering and limits will keep expanding ahead of any new end-user capability.
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 Forethought or Hatz AI.
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.
A teaser-only content feed making one argument: AI in the contact center fails on knowledge, not models.
A steady SEO blog on SMS basics, with the occasional ecommerce integration walkthrough.
See all Forethought alternatives → · See all Hatz AI alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Forethought and Hatz AI 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. Forethought and Hatz AI 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 Forethought alternatives in Support are ranked by recent ship velocity. Browse the "Forethought alternatives" section above for the current picks, or visit /alternatives/forethought for the full list with editorial commentary on each.
Top Hatz AI alternatives in Support are ranked by recent ship velocity. Browse the "Hatz AI alternatives" section above for the current picks, or visit /alternatives/hatz-ai for the full list with editorial commentary on each.