Train Your Team on the New Platform
Converge Team
Part of the HappyFox migration guide
How to train your support team when switching from HappyFox, including onboarding timelines and best practices.
Training Your Team After Switching from HappyFox
HappyFox uses a ticket-centric model with categories, statuses, and priorities. Moving to a conversation-based messaging platform means your team needs to adjust their mental model — from managing tickets to managing real-time conversations across channels. The good news: the core workflows (assign, reply, resolve) stay the same.
Concept Mapping: HappyFox → New Platform
Help your team translate familiar HappyFox concepts: Tickets become conversations or chats. Categories map to tags or labels for organizing conversations. Canned Actions become quick replies (reusable response templates). Smart Rules map to auto-reply rules and auto-routing. Ticket statuses (New, In Progress, On Hold, Closed) simplify to open/resolved/closed. Agent collision detection becomes real-time typing indicators showing when another agent is viewing the same conversation.
Day 1: Core Navigation (30 minutes)
Walk through the unified inbox where messages from all channels (email, WhatsApp, Telegram, Messenger, etc.) appear in one list. Show how to filter by channel, status, and assignment. Demonstrate the customer profile panel — similar to HappyFox's contact details sidebar but with cross-channel conversation history. Practice changing conversation status and assigning to team members.
Day 1: Productivity Features (30 minutes)
Show quick replies (replacing HappyFox's canned actions), customer tags (replacing categories for organization), internal notes (same concept as HappyFox's staff notes), and AI reply suggestions. If your team used HappyFox's ticket tagging, demonstrate the tag system and tag groups. Cover the search functionality — messaging platforms typically offer full-text search across contacts and message content.
Day 2: Advanced Workflows (30 minutes)
Train on auto-routing (round robin or load balanced — similar to HappyFox's assignment options), SLA policies (map your existing HappyFox SLA configurations), CSAT surveys (replacing HappyFox's satisfaction surveys), and working hours. If your team used HappyFox's task management (Pro plan), note that task workflows may need to be handled differently — some platforms don't have a separate task system.
Key Behavioral Shift: Tickets vs. Conversations
In HappyFox, agents work through a ticket queue — open a ticket, write a reply, set a status, move to the next. In a messaging-first platform, conversations are more fluid and real-time. Agents may handle multiple conversations simultaneously, with typing indicators showing customer activity. Encourage your team to think of it less like email ticketing and more like structured chat — faster responses, shorter messages, more back-and-forth.
Week 1: Guided Practice
Have agents handle real conversations with a team lead available for questions. Use internal team chat for quick support during the transition. If you ran parallel platforms during cutover, agents can compare the workflow side-by-side. Most teams report full comfort within 3-5 days of active use.
Pro tip: If your team relied heavily on HappyFox's Kanban board view for tickets, look for equivalent board or pipeline views in your new platform. Visual workflow management helps teams that are used to drag-and-drop ticket management.
Need the full migration guide?
This page covers train your team on the new platform specifically. For the complete step-by-step migration process:
Read the complete HappyFox migration guide →Ready to try Converge?
$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.
Start Free Trial