LiveAgent vs Forethought
Side-by-side trajectory, velocity, and editorial themes.
LiveAgent wires its ticketing engine into the Claude ecosystem via MCP.
LiveAgent is in dense maintenance mode — multiple version trains and a backport branch all shipping fixes and security patches almost daily — but the AI integration thread has sharpened. The 5.64 release adds an AI Agent Work Distributor for tickets, a new add_note MCP tool, and OAuth 2.1 on the MCP server with the explicit goal of letting claude.ai connect as a custom connector. Earlier May releases switched the MCP protocol to Streamable HTTP and renamed MCP tokens for clarity.
The product is positioning MCP as its core integration substrate. Each release adds another MCP refinement — protocol upgrade, naming cleanup, ticket-level AI work distribution — pointing toward a model where Claude or any MCP-aware agent triages and acts on tickets natively. The parallel backport lines (5.62.x, 5.63.x) suggest the AI work is being layered on without forcing customers off the legacy install base.
Expect the AI Agent Work Distributor to grow into more autonomous resolution flows, with new MCP tools added incrementally (search, reply, escalate), and a more explicit Claude-Connector-ready posture in product marketing.
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.
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.
See more alternatives to LiveAgent →
See more alternatives to Forethought →