Train Your Team on the New Platform

Converge Team

• Updated March 12, 2026

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

Training Your Team After Switching from Front

Front is built around an email-inspired inbox with workspaces, shared drafts, and collision detection. The biggest adjustment for your team is moving from Front's workspace-organized, email-centric model to a unified conversation inbox where all channels appear in a single stream.

Key Concept Mapping

Front concepts translate like this: Workspaces → Not directly mapped (all conversations are in one inbox, filtered by status and tags), Shared drafts → Collaborative editing works differently; agents work on individual replies, Macros → Quick Replies (pre-written responses with variable support), Message templates → Quick Replies, Rules → Auto-reply rules and auto-routing, Tags → Customer tags (applied to contacts rather than conversations), Front Chat → Chat widget (embeddable on your website), Contact lists → Customer filters and lifecycle stages. The main shift: Front organizes by workspace and inbox, while unified inbox platforms present all conversations in a single view sorted by status.

Day 1: Core Navigation (30 min)

Walk through the unified inbox showing how all messages — from WhatsApp, Messenger, Telegram, email, and widget — appear in one conversation list. Unlike Front's redesigned inbox with Open/Later/Done sections and separate workspaces, unified inbox platforms use status tabs (open/resolved/closed) and assignment filters. Show how to switch between conversations, change status, assign to team members, and use the customer profile sidebar for contact details and notes.

Day 1: Replacing Front Workflows (30 min)

Recreate your most-used Front macros as Quick Replies with variables. Set up customer tags to replace Front's tag system. If you used Front's rules for auto-assignment (e.g., "if message comes from WhatsApp, assign to Workspace A"), configure equivalent auto-routing rules. Front's @mentions and internal comments are replaced by team chat and customer notes — show agents how to use these for internal collaboration.

Day 2: Features That Work Differently

Front's shared drafts with collision detection don't have a direct equivalent — in most platforms, one agent handles a conversation at a time via assignment. Front's snooze and schedule send features may not have direct equivalents. Front's app switcher sidebar (right-side panel for CRM integrations like Salesforce, HubSpot) is replaced by the customer profile view. Front's calendar and meeting scheduling features (available on email channel types) are not replicated — your team may need a separate tool for scheduling.

Week 1: Guided Practice

Have agents handle real conversations with a team lead available for questions. Front users typically find the transition to a messaging-focused inbox takes 2-3 days. The most common friction point is adjusting from Front's workspace separation (different inboxes for different teams or clients) to seeing all conversations in one view — use tags, assignment, and status filters to recreate that separation.

Most teams report the learning curve from Front is 1-2 weeks. The biggest hurdle is unlearning the workspace-per-team mental model — in a unified inbox, filtering and routing replace workspace boundaries.