Train Your Team on the New Platform

Converge Team

• Updated March 12, 2026

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

Training Your Team After Switching from LiveAgent

LiveAgent is a ticket-centric platform where every interaction — email, chat, call, social message — becomes a "ticket" in a Universal Inbox. Transitioning to a messaging-focused platform means shifting your team's mental model from tickets and departments to conversations and channels. Here's a structured training plan.

Key Concept Mapping: LiveAgent → Messaging Platform

Help your team understand how familiar LiveAgent concepts translate: Tickets → Conversations (no ticket IDs, just ongoing threads per customer). Departments → Tags and assignment (route by assigning to agents rather than departmental queues). Canned messages → Quick replies with variables. Automation rules → Auto-reply and auto-routing rules. Agent panel sidebar → Unified inbox with channel filters. Ticket statuses (New, Open, Answered, Resolved) → Conversation statuses (Open, Resolved, Closed). The biggest shift: agents won't "pick up" tickets from a queue — conversations are assigned or auto-routed directly.

Day 1: Core Navigation (30 minutes)

Walk through the unified inbox showing how messages from WhatsApp, Telegram, Messenger, email, and other channels all appear in one view. Demonstrate channel-specific icons so agents can identify the source platform at a glance. Show how to filter by channel, by assignment, and by status. In LiveAgent, agents use multiple ticket tabs and sidebar filters — your new platform likely uses a simpler conversation list with search and filters instead of the tab-based workflow.

Day 1: Essential Features (30 minutes)

Cover: sending and receiving messages, using quick replies (LiveAgent's canned messages equivalent), viewing customer profiles and conversation history, assigning conversations to team members, changing conversation status, and adding internal notes. If your team relied on LiveAgent's ticket merging or ticket splitting features, explain how conversation-based systems handle multi-issue contacts differently — typically through tags and separate conversations rather than ticket operations.

Day 2: Advanced Features (30 minutes)

Train on auto-routing rules (replacing LiveAgent's department-based auto-assignment), SLA policies (similar concept but different configuration path), AI reply suggestions (may be new to your team if you weren't using LiveAgent's AI Answer Assistant), CSAT surveys, and team chat for internal communication. If your team used LiveAgent's gamification features (badges, levels, leaderboards), note that most messaging platforms don't include gamification — focus instead on analytics dashboards for performance visibility.

Week 1: Supervised Practice

Have agents handle real conversations with a team lead available for questions. Common friction points from LiveAgent migration: agents looking for ticket IDs (conversations don't have them), trying to "transfer" conversations between departments (use assignment instead), and expecting to see all historical interactions in a single ticket thread (messaging platforms show per-customer conversation history differently). Use internal team chat for quick questions during the transition period.

Expect a 1-2 week adjustment period. LiveAgent's interface has a steeper learning curve, so agents who've mastered it typically pick up simpler messaging-focused tools quickly. The main hurdle isn't complexity — it's unlearning the ticket-centric workflow in favor of a conversation-centric approach.