Find your fit
Who it is for
A support team handling questions from several storefront or messaging channels can work in one inbox instead of separate accounts. Re:amaze suits teams that want assignments, notes and reminders close to the customer conversation.
Teams with recurring questions can publish a FAQ and expose relevant articles in Chat. Businesses with more complex routing can configure workflows, but should test the conditions with their own messages before relying on automation.
The work it supports
Core capabilities
Shared inbox. Re:amaze gathers conversations from connected channels in one place for the team. Staff can coordinate with notes and assignments; confirm each channel’s setup and access before moving support traffic.
Live chat. Re:amaze provides a chat channel with configurable chat mode and office hours. Chat conversations are tied to an email channel so agents can follow up when a visitor leaves.
FAQ and knowledge base. Re:amaze lets teams create help articles and decide whether they are public, internal or still in draft. The FAQ can also appear inside the chat widget.
Understand the offer
Pricing and getting started
The current public pricing page lists seat-based monthly Basic at $29, Pro at $49 and Plus at $69 per team member. Its separate Starter volume plan is $59 monthly for unlimited team members and up to 500 responded conversations. These are different pricing structures; confirm the applicable plan, annual option and checkout total before budgeting.
Re:amaze advertises a 14-day trial with plan selection afterward. AI Agent resolution allowances depend on the seat plan; the current guide says usage above included amounts is billed at $0.85 per resolution and volume plans bill all resolutions at that rate. Check current plan entitlements and overage settings before enabling it.
Look a little closer
Before you choose
Channel setup. The official overview lists email, chat, social, SMS and voice, while plan details separate some channels into higher tiers. Verify the chosen plan and connect each address or account you need.
Chat continuity. Re:amaze requires each live chat conversation to be attached to an email address. Test what happens when a visitor leaves, and make sure your team’s reply address and office hours match customer expectations.
FAQ publishing. Articles can be public, internal or draft; the editor supports Markdown and HTML. Review the visibility and content of an article before using it in customer-facing chat or AI workflows.
Automation. Workflows depend on triggers, conditions and selected actions such as tagging, assignment or internal notes. Test a narrow route first and inspect what happens when conditions overlap.
Research scope. This profile uses current official public pages. No Re:amaze account, channel delivery, workflow execution, AI resolution, trial signup or checkout was tested.
12 distinct sources behind this profile. Research observed Oct 15, 2026. Features and offers can change.
View sources and research →
