← Back to home
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

FeatureRe:amazeXurrent
SectorSupportSupport
Velocity score2.56.3
Sparks · 30d00
Top themescustomer-support, ai-agents, ecommerce, inbox-automationitsm, ai-agents, agent-governance, problem-management
Last editorial update2mo ago12d ago
WebsiteVisit →Visit →

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.

Read the full Re:amaze trajectory →

What is Xurrent?

Xurrent lets staff approve tasks inside Sera AI chat as October's update keeps growing.

Xurrent ITSM ships monthly update documents that grow week by week. September delivered six specialized Sera AI Agents plus Jamf CMDB and native ClickUp integrations. The October document now spans agent controls (scoping in Agent Designer, an Agent Actions inbox), core ITSM work (problem tasks, closing linked requests from a problem's resolution, team mentions) and, in its latest revision, approving and rejecting tasks in Sera chat, time entry privacy for directory accounts and a browsable knowledge library in Self Service.

Read the full Xurrent trajectory →

Re:amaze vs Xurrent: editorial side-by-side

R
Re:amaze
SUPPORT
2.5

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.

X
Xurrent
SUPPORT
6.3

Xurrent lets staff approve tasks inside Sera AI chat as October's update keeps growing.

◆ Current state

Xurrent ITSM ships monthly update documents that grow week by week. September delivered six specialized Sera AI Agents plus Jamf CMDB and native ClickUp integrations. The October document now spans agent controls (scoping in Agent Designer, an Agent Actions inbox), core ITSM work (problem tasks, closing linked requests from a problem's resolution, team mentions) and, in its latest revision, approving and rejecting tasks in Sera chat, time entry privacy for directory accounts and a browsable knowledge library in Self Service.

◆ Where it's heading

Sera is moving from a single assistant to a managed multi-agent system, and now into a place where routine decisions get made: approvals happen in the chat rather than in the record. Problem management and inbox workflows keep deepening alongside, and each month adds an iPaaS connector, which positions Xurrent as an ITSM coordination layer.

◆ Prediction

Expect further October revisions to add more actions that can be completed from Sera chat, beyond approvals; the entries don't show which ones.

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.

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.

  1. 14d agoXurrentXurrent adds task approvals in Sera chat, Self Service library
  2. 21d agoXurrentXurrent ITSM - October 2026 Product Updates
  3. 28d agoXurrentXurrent ITSM - October 2026 Product Updates
  4. 1mo agoXurrentXurrent ships six Sera AI Agents, Jamf CMDB, and ClickUp connector ⚡
  5. 1mo agoXurrentXurrent September mid-month: Sera AI agents and Jamf/ClickUp integrations beginning rollout
  6. 1mo agoXurrentXurrent: pooled reservations and Sera AI conversation-aware classification
  7. 2mo agoRe:amazeHow to Automate Your Support Inbox with AI Pre-Filter
  8. 4mo agoRe:amazeWhat’s New in Re:amaze: A Fresh Set of AI Customer Support Tools ⚡
  9. 4mo agoRe:amazeHow to Write Help Center Articles for Better AI Answers
  10. 5mo agoRe:amazeAmazon Prime Day 2026 Is Moving to June — How to Prepare
  11. 6mo agoRe:amazeAI Agent for Customer Support: Now Supports Email and SMS
  12. 6mo 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 6.3 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 6.3 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.