Train Your Team on the New Platform

How to train your support team when switching from Reamaze, including onboarding timelines and best practices.

How do you train your support team after switching from Re:amaze?

Training a support team after switching from Re:amaze takes 2–4 working days for most teams. The core work is mapping Re:amaze's vocabulary — Conversations, Cues, Workflows, Response Templates, Departments — onto the new platform's terms, then running supervised practice on real tickets before cutting the old account. The interface concepts behind Re:amaze's inbox (status filters, assignments, tags, macros) carry over almost everywhere; what changes is where the buttons live and which features no longer exist.

Key Concept Mapping

Re:amaze's vocabulary, per its official help center, maps cleanly to most messaging platforms. Conversations (email, chat, social threads)Conversations. States (Unresolved / Pending / Resolved)Open / Resolved. Response TemplatesQuick Replies or macros. Workflows (trigger-based automations)Auto-reply rules. Cues (proactive in-app messages)Widget popup messages or suggested replies. TagsTags. Departments (Plus only)Role-based assignment groups. FAQ articlesHelp center articles or widget FAQ entries. Peek (co-browsing, Plus only) and Video Calls have no direct equivalent on messaging-only platforms — flag these to the team early so nobody hunts for a missing menu.

Day 1: Core Navigation (30 min)

Re:amaze's left-hand navigation (Dashboard, Conversations, Contacts, FAQ, Settings) has a near-identical counterpart on most modern inboxes. Walk agents through the unified inbox where every channel surfaces in one list, the open/resolved filters, the assignment dropdown, and the contact/customer search. Call out the one difference that trips people up: Re:amaze splits social channels and email under separate sidebar filters, while most newer platforms merge them into a single channel-agnostic stream. Have each agent close five real conversations under supervision before lunch.

Day 1: Recreating Workflows (30 min)

Export your Re:amaze Response Templates (SettingsResponse Templates) and rebuild the top 20 as Quick Replies on the new platform — that covers about 80% of usage for most teams. Recreate your tag taxonomy first, because most Workflows and reports depend on it. Rebuild trigger-based Workflows as auto-reply rules with working-hours conditions. Document each Cue (welcome message, exit-intent, product-page prompt) and rebuild it as a widget popup or suggested message. Skip rarely-used templates: dead templates pile up in every Re:amaze account.

Day 2: Features That Work Differently

Re:amaze's AI Agent (Beta) is built to answer customers autonomously. Most alternatives expose AI as reply suggestions that an agent reviews before sending — slower for volume, but it removes the brand risk of an autonomous bot hallucinating policy. Re:amaze's FAQ/Knowledge Base is a hosted self-service portal; on a messaging-first platform, the same content usually lives as widget FAQ entries or a separate help-center product. Re:amaze's Peek (co-browsing) and Video Calls (both Plus-only) don't exist on messaging-focused tools — plan a Zoom or Google Meet fallback before training, not after the first customer asks.

Day 2: Adjusting Reporting & CSAT Habits

Re:amaze's CSAT surveys and Staff Shifts are gated to the Plus tier ($69/user/month per its pricing page). Teams switching off Plus often discover that CSAT, SLA tracking, and shift scheduling are bundled into lower tiers — or included flat — on alternatives, which changes the daily reporting routine. Walk team leads through where the new platform stores: response-time reports, first-contact resolution, CSAT score, agent activity, and conversation volume by channel. Re:amaze's Departments-based reporting becomes role- or team-based reporting on most newer platforms; the cuts are similar but the filter UI moves. Decide on day one which two or three metrics will replace whatever leadership pulled from Re:amaze's Reports tab, then standardize on those.

Common Mistakes During the First Week

Five recurring mistakes show up in week-one Re:amaze migrations. 1. Importing every Response Template. Half are stale; rebuild only the top 20. 2. Skipping the tag taxonomy step. If tags don't match, every saved view and report breaks. 3. Leaving the old Re:amaze chat widget live. Customers message both inboxes; agents miss replies. Remove the snippet on day one. 4. Trying to replicate the AI Agent verbatim. Agent-assisted suggestions need different prompts and a different escalation policy — design fresh, don't port. 5. Cancelling Re:amaze before two billing cycles. Keep it read-only for 30–60 days so agents can reference historical threads while customers' replies flow into the new inbox.

Week 1: Supervised Practice

Have each agent handle live conversations on the new platform with a team lead in a shared channel for questions. Agents who mainly used Re:amaze's shared inbox adjust in 2–3 days. Agents who relied on the AI Agent's autonomous mode take longer, because their daily workflow changes from "review what the bot sent" to "review the suggestion before sending." Set a daily 15-minute retrospective for the first five days to capture missing macros, broken auto-replies, and customer-facing copy that didn't transfer.

Most teams report the Re:amaze learning curve is 2–4 days. The biggest single adjustment is moving from AI Agent's autonomous mode to agent-assisted suggestions, followed by adapting Re:amaze's three-state model (Unresolved / Pending / Resolved) to a simpler open/resolved flow, and accepting that Peek and Video Calls don't have direct replacements on messaging-first platforms.

Re:amaze training: FAQ

How long does it take to train a team to switch off Re:amaze?

Plan for 2–4 working days of supervised practice for a team that mainly used Re:amaze's inbox, tags, and Response Templates. Add 2–3 extra days if your team relied on the AI Agent's autonomous mode, because agents need to adjust to reviewing suggestions before they send. Run live conversations from day one with a team lead on standby — classroom-only training rarely sticks for support work.

Do agents need to relearn macros when switching from Re:amaze?

Yes, but not from scratch. Re:amaze's Response Templates port directly in concept to Quick Replies or macros on any modern inbox — the trigger words and variables change, but the content is reusable. Export your templates first, audit which ones are still in active use (usually the top 20 cover most volume), and rebuild only those. Re:amaze's Workflow triggers are the harder migration: they get rebuilt as auto-reply rules and need fresh testing against real incoming conversations.

What's the hardest part of moving away from Re:amaze's AI Agent?

The hardest part is the operating-model change. Re:amaze's AI Agent (Beta) is built to answer customers without an agent in the loop. Most alternatives expose AI as a suggestion an agent reviews before sending, which is slower per message but gives the team direct control over tone, policy, and escalation. Teams that ran the AI Agent autonomously usually need to redesign their escalation rules — what used to be "AI handles tier-1, agents handle tier-2" becomes "AI drafts, agents send" — and that change to the daily rhythm takes longer to absorb than any UI difference.