Train Your Team on the New Platform

Converge Team

• Updated March 12, 2026

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

Training Your Team After Switching from Drift

Drift is a sales-first conversational marketing tool. Your team's biggest adjustment isn't learning new buttons — it's shifting from a sales qualification mindset to a customer support mindset. Drift's core concepts (playbooks, CQL scores, meeting routing) don't have direct equivalents in a support platform.

Key Concept Mapping

Drift concepts translate like this: Playbooks (bot conversation flows) → Auto-reply rules and quick replies. CQL Score (Conversational Qualified Lead) → Customer lifecycle stages (visitor → engaged → lead → customer). Lead Routing (sales rep assignment) → Auto-routing (round-robin or load-balanced). Meetings (calendar booking) → No direct equivalent — meeting scheduling is a sales feature, not a support feature. Drift Email sequences → Separate email marketing tool. Conversations → Conversations (same concept, different context — support vs. sales).

Day 1: The Mindset Shift (30 min)

In Drift, the goal of every conversation is to qualify and route to sales. In a support platform, the goal is to resolve the customer's issue. Walk your team through this fundamental difference. Show how the unified inbox displays messages from all channels (not just website chat), explain conversation statuses (open → resolved → closed), and demonstrate that agents handle support requests — not sales qualification. If some team members handled both sales and support in Drift, clarify new role boundaries.

Day 1: Core Features (30 min)

Cover the essential daily tools: quick replies (your team's replacement for Drift's canned responses), customer tags for categorization, internal notes for team collaboration, conversation assignment, and AI reply suggestions. Show the full-text search across contacts and messages — Drift's search is limited to its own data model, while a multi-channel inbox searches across all platforms.

Day 2: Multi-Channel Training (30 min)

If your team only used Drift's website chat, they need training on channel-specific behaviors. WhatsApp has a 24-hour response window for customer-initiated messages. Telegram allows rich formatting and file sharing. Messenger and Instagram DMs have their own character limits and media types. Discord has server-based conversation threading. Walk through each connected channel's unique behaviors so agents know what to expect.

Week 1: Features That Don't Carry Over

Several Drift features won't exist in a support platform: Meeting scheduling — agents can share a calendar link manually but there's no built-in booking flow. ABM targeting (showing different bots to different accounts) — not applicable to support. Revenue dashboards (pipeline value, deal tracking) — support platforms track response times and CSAT, not revenue metrics. Salesforce opportunity sync — if your team relied on seeing deal data in Drift, they'll need to check the CRM directly.

The learning curve from Drift to a messaging-first support platform is typically 1-2 weeks. Agents who handled live chat in Drift will adapt quickly to the conversation interface. The biggest adjustment is for team members who relied on Drift's sales automation features — they'll need to learn a different workflow for qualification and handoff.