Re:amaze vs Discourse
Side-by-side trajectory, velocity, and editorial themes.
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.
Discourse opens its AI bot to any external MCP server, treating the forum as an agent host.
Discourse runs on a monthly main release plus periodic security intermediates, and the editorial focus across recent posts is clearly AI plumbing. March added Bring-Your-Own MCP server support to the Discourse AI Bot, alongside documented AI credentials management and SSO auto-provisioning for forum admins. The team has also been adjusting its release-communication process, with backdated intermediate-release topics filling earlier gaps.
Discourse is positioning the forum as an environment that hosts agents, not just a place that uses AI features. By accepting any MCP-compatible tool provider as a backend, it makes itself the substrate community managers extend with arbitrary external capabilities — search, ticketing, knowledge bases, whatever the host wires in. SSO auto-provisioning and structured form templates round out the admin surface that this agent-host posture needs.
Expect deeper agent UX inside topics — more entry points and persona configuration — alongside audit and observability tooling for what external MCP tools do on a forum. Community trust depends on that side staying explainable.
See more alternatives to Re:amaze →
See more alternatives to Discourse →