Train Your Team on the New Platform

Converge Team

• Updated March 12, 2026

Part of the Zendesk Chat migration guide

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

Training Your Team After Switching from Zendesk Chat

Zendesk Chat has a dedicated Chat Dashboard with its own interface for managing conversations, shortcuts, and triggers. Modern unified inbox platforms consolidate all messaging into a single conversation view. The transition is straightforward, but your team needs to learn where familiar features now live.

Key Concept Mapping

Zendesk Chat concepts translate to unified inbox platforms like this: Chats → Conversations (same concept, broader scope across channels). Shortcuts (slash commands like /greeting) → Quick Replies (searchable, with variable support). Departments (routing groups) → Auto-routing rules (round-robin or load-balanced). Chat Triggers (proactive messages based on visitor behavior) → Auto-reply rules. Chat Ratings (good/bad) → CSAT surveys (5-star scale). Banned Visitors → Visitor banning. Pre-chat Form → Widget profile collection settings. The biggest shift: Zendesk Chat shows only chat conversations, while a unified inbox includes messages from every connected channel in one stream.

Day 1: Core Navigation (30 min)

Walk through the unified inbox. In Zendesk Chat, agents had a dedicated chat window with a visitor list showing active chats. In a unified inbox, all conversations — from chat widget, WhatsApp, email, Telegram — appear in a single list sorted by status and recency. Show how to filter by channel, status (open/resolved/closed), and assignment. Demonstrate how customer profiles display visitor information similar to Zendesk Chat's visitor details panel.

Day 1: Recreating Workflows (30 min)

Convert your Zendesk Chat shortcuts into Quick Replies. If you exported shortcuts via the API, use the message content to create Quick Reply templates. Set up auto-reply rules to replace Chat triggers — for example, a trigger that sent "How can I help you?" after 30 seconds of browsing becomes an auto-reply that greets new conversations. Configure customer tags to replace Chat's tagging system for categorizing conversations.

Day 2: Features That Work Differently

Zendesk Chat's visitor monitoring (seeing who's browsing your site in real-time) doesn't have a direct equivalent in most inbox platforms, but widget analytics and visitor tracking provide similar insights into page views and customer journeys. Zendesk Chat's concurrent chat limits (restricting how many chats an agent handles simultaneously) map to auto-routing with load balancing. The Chat Dashboard analytics (wait times, chat duration, agent activity) are replaced by employee analytics and response time tracking.

Week 1: Supervised Practice

Have agents handle real conversations with a team lead available for questions. The adjustment from a chat-only tool to a multi-channel inbox typically takes 2-3 days for teams used to Zendesk Chat's simpler interface. Use team chat for internal questions during the transition. Most agents report that once they adjust to seeing all channels in one place, they prefer it to the chat-only view.

Tip: Create a simple "cheat sheet" mapping Zendesk Chat features to their equivalents on the new platform. Pin it in your team chat channel for the first week so agents can quickly find where things are without interrupting their workflow.