Spiceworks
Spiceworks covers the Microsoft 365 outage from the help desk's side.
Comparison · Support
Re:amaze vs Xurrent
A side-by-side editorial comparison of Re:amaze and Xurrent — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ai-agents
Re:amaze vs Xurrent: at a glance
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.
What is Xurrent?
Xurrent's November update blocks unverified email senders from changing records.
Xurrent ITSM publishes a monthly update page that grows week by week. The November 12 revision stops unverified email senders from updating records, creates the major incident request group when a major incident is accepted, brings Sera AI summaries to problems and adds iPaaS Lookup Tables. It builds on the first November revision, which put Closure Agent sign-off drafts and reopen suggestions in the Inbox.
Re:amaze vs Xurrent: editorial side-by-side
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.
Xurrent
5.0SUPPORT
Xurrent's November update blocks unverified email senders from changing records.
◆ Current state
Xurrent ITSM publishes a monthly update page that grows week by week. The November 12 revision stops unverified email senders from updating records, creates the major incident request group when a major incident is accepted, brings Sera AI summaries to problems and adds iPaaS Lookup Tables. It builds on the first November revision, which put Closure Agent sign-off drafts and reopen suggestions in the Inbox.
◆ Where it's heading
After September's Sera agent launch, each revision spreads AI summaries and agents into another record type while tightening controls around them. This month adds a security fix for email-driven updates alongside more integration plumbing.
◆ Prediction
Expect later November revisions to bring Sera summaries or agents to more record types, such as changes, and more iPaaS building blocks.
Alternatives to Re:amaze and Xurrent
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 Re:amaze or Xurrent.
DoneDone
DoneDone's editor gets tables, spreadsheet paste and text colors.
Twilio
Twilio's voice AI stops cutting callers off mid-sentence, using its own turn-taking model.
LiveAgent
LiveAgent 5.71 starts letting bots work chats over MCP and answer the phones.
Chatway
Chatway adds a Ticket Center, moving from live chat toward a full helpdesk.
Faveo Helpdesk
Faveo Helpdesk's free edition has shipped mostly security patches and stack upgrades since 2019.
See all Re:amaze alternatives → · See all Xurrent alternatives →
Recent activity from Re:amaze and Xurrent
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoXurrentXurrent blocks unverified email senders, adds Sera problem summaries
- 9d agoXurrentXurrent ITSM - November 2026 Product Updates
- 16d agoXurrentXurrent adds Outlook, Jira Cloud connectors and agent time reports
- 1mo agoXurrentXurrent adds task approvals in Sera chat, Self Service library
- 1mo agoXurrentXurrent ITSM - October 2026 Product Updates
- 1mo agoXurrentXurrent ITSM - October 2026 Product Updates
- 2mo agoRe:amazeHow to Automate Your Support Inbox with AI Pre-Filter
- 4mo agoRe:amazeWhat’s New in Re:amaze: A Fresh Set of AI Customer Support Tools ⚡
- 5mo agoRe:amazeHow to Write Help Center Articles for Better AI Answers
- 6mo agoRe:amazeAmazon Prime Day 2026 Is Moving to June — How to Prepare
- 7mo agoRe:amazeAI Agent for Customer Support: Now Supports Email and SMS
- 7mo agoRe:amazeAI Customer Intent Detection, Now Smarter in Re:amaze
Frequently asked questions
What is the difference between Re:amaze and Xurrent?
Both compete on the same themes — ai-agents — within Support. Xurrent is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 Re:amaze better than Xurrent?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Xurrent is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 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.
What are the best alternatives to Xurrent?
Top Xurrent alternatives in Support are ranked by recent ship velocity. Browse the "Xurrent alternatives" section above for the current picks, or visit /alternatives/xurrent for the full list with editorial commentary on each.