Train Your Team on the New Platform

Converge Team

• Updated March 12, 2026

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

Training Your Team After Switching from Deskpro

Deskpro is a ticket-centric helpdesk with a 4-panel agent workspace (Navigation Panel, View Panel, Content Panel, Properties Pane), departments, queues, and extensive customization. The biggest adjustment is moving from structured ticket workflows with departments and queues to a conversation-based unified inbox.

Key Concept Mapping

Deskpro concepts translate like this: Tickets → Conversations, Departments → Routing rules or tags, Queues → Inbox filters and status tabs, Macros → Quick Replies (pre-written responses), Snippets → Quick Replies (text shortcuts), Triggers → Auto-reply rules and routing logic, Escalations → SLA breach notifications, Labels → Customer tags, Stars → No direct equivalent (use status or tags), SLA Policies → SLA policies (direct equivalent), Lite Agents → Not needed with flat pricing (all agents have full access). Deskpro separates "Admin" from "Agent" interfaces; unified inbox platforms typically combine everything into one interface.

Day 1: Core Navigation (30 min)

Walk through the unified inbox showing how all messages — from WhatsApp, Messenger, email, and widget — appear in one conversation list. Unlike Deskpro's queue-based View Panel where tickets are organized by department and custom queues, a unified inbox presents all conversations sorted by status and recency. Show status transitions (open → resolved → closed) and how conversation assignment replaces Deskpro's department-based routing.

Day 1: Recreating Workflows (30 min)

Recreate your most-used Deskpro macros and snippets as Quick Replies. Set up customer tags to replace Deskpro's label system. If you used triggers for auto-assignment (e.g., "if ticket department is Sales, assign to Sales team"), configure equivalent auto-routing rules. Document any escalation rules (time-based actions like "notify manager if no reply in 2 hours") — these may need to be mapped to SLA breach notifications in your new platform.

Day 2: Features That Work Differently

Deskpro's Lite Agents (limited-access view-only agents) don't exist in flat-rate platforms — all team members have full access. Deskpro's ticket forms (structured intake with conditional fields per department) don't have a direct equivalent — customer data is collected through conversation and profile fields. Deskpro's Help Center (knowledge base, guides, community forums, news) is a standalone feature that your new platform may not fully replicate. Deskpro's built-in voice features won't carry over to messaging-focused platforms.

Week 1: Supervised Practice

Have agents handle real conversations with a team lead available for questions. The adjustment from Deskpro's 4-panel ticket workspace to a real-time conversation inbox typically takes 2-3 days. Agents who relied heavily on custom queues and department filters may need extra time to adapt to a simpler inbox model. Use the team chat feature for internal questions during transition.

Most teams report that the learning curve from Deskpro to a messaging-focused platform is 1-2 weeks. The biggest adjustment is moving away from the structured department-and-queue model to a flatter conversation-based workflow.