LiveAgent vs Re:amaze
Side-by-side trajectory, velocity, and editorial themes.
After a mid-May AI-agent and MCP push, LiveAgent has dropped into hardening mode.
LiveAgent's last two weeks are almost entirely defensive: bug fixes across chat handoff, email rendering, API custom fields, and a ticket-history query that degenerated at scale. The substantive feature work — an AI Agent Work Distributor, add_note and search MCP tools, and OAuth 2.1 on the MCP server for a claude.ai custom connector — landed on May 18 and now sits behind a wall of stabilization releases.
The pattern is a product consolidating a large agent/MCP feature drop rather than extending it. Release tags split across two trains (5.63.x and 5.64.x) shipping near-daily, all carrying fixes, which reads as cleanup after the integration push rather than new direction.
Expect the fix cadence to taper, then a return to MCP/AI-agent feature work once the 5.64.x line stabilizes. The entries don't show what that next feature is.
Re:amaze is rebuilding its helpdesk around an AI agent — multi-channel rollout, smarter intent, sharper positioning.
Re:amaze launched its AI Agent in January, expanded it to email and SMS in April, and upgraded the underlying customer-intent detection a week earlier. Supporting content is making the explicit argument that AI should handle a growing share of ecom support volume.
The product is being repositioned from a multichannel ecom helpdesk into an AI-first support platform with humans on top. Each recent release tightens the AI Agent's reach (more channels) or accuracy (intent detection). Competitive content frames the choice as outgrowing legacy helpdesks rather than feature-matching them.
Expect the AI Agent to extend into voice or social DMs next, plus structured handoff rules between agent and human. A pricing-tier reshuffle tied to AI resolution volume looks likely, given how directly the marketing now anchors on AI deflection rate.
See more alternatives to LiveAgent →
See more alternatives to Re:amaze →