Train Your Team on the New Platform

Converge Team

• Updated March 12, 2026

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

Training Your Team After Switching from Intercom

Intercom uses a dual-concept model: "Conversations" for real-time chat and "Tickets" for tracked issues that need back-office work. The AI-enhanced inbox with custom views, keyboard shortcuts, and workflow automations creates a specific workflow pattern. Moving to a messaging-first platform means your team shifts from managing tickets+conversations to handling unified conversations across all channels.

Key Concept Mapping

Intercom concepts translate to messaging platforms like this: Conversations + Tickets → Conversations (all interactions are conversations), Macros (saved replies with multi-step actions) → Quick Replies (pre-written messages), Inbox views (custom filtered lists) → Status tabs and filters (open/resolved/closed), Round-robin assignment → Auto-routing (round robin or load-balanced), Workflows (visual automation builder) → Auto-reply rules + routing rules, Fin AI Agent → AI reply suggestions (human-assisted, not autonomous), Product Tours → No direct equivalent (these are Intercom-specific). The biggest conceptual shift: Intercom separates "conversations" (chat) from "tickets" (tracked issues). On a messaging platform, everything is a conversation with status tracking.

Day 1: Core Navigation (30 min)

Walk through the unified inbox showing how all messages — from WhatsApp, Messenger, email, Telegram, Discord, and the website widget — appear in one conversation list. In Intercom, agents use custom views to filter between "My conversations," "Unassigned," and "All" with additional filters for channel, team, and status. On a messaging platform, conversations live in a single stream sorted by status and recency. Demonstrate how to filter by status (open, resolved, closed), use search across contacts and messages, and how conversation assignment works.

Day 1: Recreating Key Workflows (30 min)

Recreate your most-used Intercom macros as Quick Replies — focus on the reply text, and handle the automation actions (auto-tag, auto-assign) through routing rules separately. Set up customer tags to replace Intercom's tagging system. If you used round-robin assignment in Intercom (Advanced+ plan), configure equivalent auto-routing rules. Document any Intercom Workflow automations (multi-step conditional sequences) — these need to be decomposed into simpler auto-reply and routing rules.

Day 2: Features That Work Differently (30 min)

Intercom's Fin AI Agent autonomously resolves queries — on a messaging platform, AI provides reply suggestions that agents send with one click. The workflow is "AI assists human" instead of "AI handles autonomously." Intercom's help center articles (used by Fin) don't migrate — self-service is handled through the chat widget's FAQ feature instead. Intercom's outbound messaging (proactive campaigns) has no equivalent in messaging-focused platforms. The customer data sidebar works similarly — customer profiles with properties, tags, notes, and conversation history.

Week 1: Supervised Practice

Have agents handle real conversations with a team lead available for questions. Teams coming from Intercom typically adjust within 2–3 days because the core inbox workflow is similar. The main learning curve is losing the dual conversations/tickets model and adapting to status-based conversation management. Use internal team chat for quick questions during the transition period.

Most teams report the transition from Intercom takes 1–2 weeks. Agents who primarily used Intercom's Messenger chat adapt fastest. Those who relied heavily on Workflow automations and Fin AI take longest to adjust their processes.