Formbricks
Formbricks 6.0 RC cycle reveals commercial hardening: lower self-hosted cap, MCP OAuth, and Act as Beta
Comparison · Support
LiveAgent vs Re:amaze
A side-by-side editorial comparison of LiveAgent and Re:amaze — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:customer-support
LiveAgent vs Re:amaze: at a glance
What is LiveAgent?
LiveAgent launches Svelte 5 frontend migration and multi-model AI simultaneously.
LiveAgent is in a structural consolidation phase with two parallel tracks running at once. The August 27 release was its most significant in the window — launching a Svelte 5 umbrella to progressively replace a decade-old GWT frontend, adding Gemini and Anthropic as selectable AI providers, shipping voice call transcription, and connecting Answer Suggestion to ticket context via MCP. The weeks since have been operational cleanup: fixing a DB query that hit 1.83 million rows per poll at 92% CPU, patching stuck-chat queue logic, and closing multiple MCP authorization gaps.
What is Re:amaze?
Re:amaze keeps adding stages to the pipeline before a human sees a ticket
Re:amaze publishes a blog that doubles as its release channel, and the run since January is a single continuous build: the AI Agent launched as a knowledge-base-backed chatbot, gained smarter intent detection, extended to email and SMS, then a mid-year roundup added visibility into how the agent works and ways to test it before it goes live. The newest entry introduces an AI Pre-Filter that sorts the inbox before any of that runs — separating marketing mail, shipping notices, social mentions and spam from the customers who actually need an answer.
LiveAgent vs Re:amaze: editorial side-by-side
LiveAgent
6.3SUPPORT
LiveAgent launches Svelte 5 frontend migration and multi-model AI simultaneously.
◆ Current state
LiveAgent is in a structural consolidation phase with two parallel tracks running at once. The August 27 release was its most significant in the window — launching a Svelte 5 umbrella to progressively replace a decade-old GWT frontend, adding Gemini and Anthropic as selectable AI providers, shipping voice call transcription, and connecting Answer Suggestion to ticket context via MCP. The weeks since have been operational cleanup: fixing a DB query that hit 1.83 million rows per poll at 92% CPU, patching stuck-chat queue logic, and closing multiple MCP authorization gaps.
◆ Where it's heading
Two architectural moves are now running in parallel. The GWT-to-Svelte 5 migration is a multi-year undertaking that will unblock faster UI iteration once the foundation is stable — the 'progressive replacement' framing means it won't land visibly for a while, but it signals intent to shed significant technical debt. The multi-model AI support (Anthropic, Gemini, OpenAI, MCP-based context) suggests LiveAgent is positioning AI as customer-configurable infrastructure rather than a fixed feature, letting enterprise buyers bring their own models.
◆ Prediction
The next likely moves are broader Svelte-based agent panel rollout and tighter MCP governance — permission scopes and authentication hardening are already recurring themes in recent fixes. The WhatsApp channel has absorbed an unusually high volume of bug fixes, suggesting a WhatsApp reliability sprint or a targeted feature push (auto-replies just shipped) is close.
Re:amaze
2.5SUPPORT
Re:amaze keeps adding stages to the pipeline before a human sees a ticket
◆ Current state
Re:amaze publishes a blog that doubles as its release channel, and the run since January is a single continuous build: the AI Agent launched as a knowledge-base-backed chatbot, gained smarter intent detection, extended to email and SMS, then a mid-year roundup added visibility into how the agent works and ways to test it before it goes live. The newest entry introduces an AI Pre-Filter that sorts the inbox before any of that runs — separating marketing mail, shipping notices, social mentions and spam from the customers who actually need an answer.
◆ Where it's heading
The company is working backwards from the reply toward the inbox. First the agent answered questions, then it understood them better, then it reached more channels, then it became inspectable and testable. Pre-filtering is the logical next step upstream: deciding what is even a support conversation. The supporting content — how to write help centre articles for better AI answers, how much support AI should handle — is aimed at customers who have to decide how much of the queue to hand over.
◆ Prediction
Expect the pre-filter and the agent to be connected into a single routing decision, with escalation rules for the VIP case the announcement explicitly calls out as needing a person.
Alternatives to LiveAgent and Re:amaze
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 LiveAgent or Re:amaze.
SolarWinds Service Desk
SolarWinds Service Desk is loading its Labs pipeline with native Entra ID automation, IT asset tracking, and compliance-ready task management.
Freshchat
Freshchat keeps product moves off the public record — changelog offers nothing to track.
Freshdesk
Freshdesk's changelog feed contains only marketing copy — no substantive release data available.
TeamViewer
TeamViewer's scraped feed contains only community marketing fragments—no actual release data.
Xurrent
Xurrent is weaving Sera AI deeper into its ITSM automation layer while opening iPaaS connectivity to third-party builders.
See all LiveAgent alternatives → · See all Re:amaze alternatives →
Recent activity from LiveAgent and Re:amaze
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoLiveAgentGA4 event tracking added; queued chat routing and FlowHunt chatbot fixed
- 9d agoLiveAgentWidget asset caching, DB performance fix, and security hardening
- 9d agoLiveAgent92% DB CPU from full-table chat COUNT(*) fixed; widget asset caching hardened
- 14d agoLiveAgentFlowHunt ticket ID passthrough; widget font and email decoding fixes
- 14d agoLiveAgentFlowHunt button fix and private API usage stats endpoint repaired
- 20d agoLiveAgentSvelte 5 frontend, Gemini and Anthropic AI providers, and voice transcription ship together ⚡
- 29d agoRe:amazeHow to Automate Your Support Inbox with AI Pre-Filter
- 2mo agoRe:amazeWhat’s New in Re:amaze: A Fresh Set of AI Customer Support Tools ⚡
- 3mo agoRe:amazeHow to Write Help Center Articles for Better AI Answers
- 4mo agoRe:amazeAmazon Prime Day 2026 Is Moving to June — How to Prepare
- 5mo agoRe:amazeAI Agent for Customer Support: Now Supports Email and SMS
- 5mo agoRe:amazeAI Customer Intent Detection, Now Smarter in Re:amaze
Frequently asked questions
What is the difference between LiveAgent and Re:amaze?
Both compete on the same themes — customer-support — within Support. LiveAgent is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Is LiveAgent better than Re:amaze?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. LiveAgent is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
What are the best alternatives to LiveAgent?
Top LiveAgent alternatives in Support are ranked by recent ship velocity. Browse the "LiveAgent alternatives" section above for the current picks, or visit /alternatives/liveagent for the full list with editorial commentary on each.
What are the best alternatives to Re:amaze?
Top Re:amaze alternatives in Support are ranked by recent ship velocity. Browse the "Re:amaze alternatives" section above for the current picks, or visit /alternatives/reamaze for the full list with editorial commentary on each.