Train Your Team on the New Platform

Converge Team

• Updated March 12, 2026

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

Training Your Team After Switching from Crisp

Crisp's interface is organized around a shared inbox with conversation statuses (Pending, Unresolved, Resolved, Deleted, Spam), a left sidebar with Dashboard, Inbox, Contacts, Knowledge Base, Analytics, and Settings. Moving to a new platform means adjusting to a different navigation structure and understanding how Crisp concepts translate.

Key Concept Mapping

Crisp concepts translate to a messaging platform like this: Conversations (all channel messages) → Conversations (direct equivalent), Conversation statuses (Pending/Unresolved/Resolved) → Open/Resolved/Closed, Hugo AI (autonomous AI chatbot agent) → AI reply suggestions (agent-assisted, not autonomous), Triggers (automated chatbox events) → Auto-reply rules, Shortcuts (canned responses) → Quick Replies, Knowledge Base articles → FAQ entries in chat widget, Routing rules (Essentials+) → Auto-routing (round robin or load-balanced), Segments (email routing tags) → Customer tags, MagicBrowse/Video calls → No equivalent (messaging-focused platform).

Day 1: Core Navigation (30 min)

Crisp's left sidebar (Dashboard, Inbox, Contacts, etc.) will map to a similar navigation in most messaging platforms. Walk through: where all messages appear from every connected channel in one list, how to filter by status (open, resolved, closed), how conversation assignment works, and how to use full-text search across contacts and messages. The key difference from Crisp: conversations from WhatsApp, Telegram, Messenger, email, and the widget all appear in a unified stream without separate inboxes per channel.

Day 1: Recreating Workflows (30 min)

Recreate your most-used Crisp Shortcuts as Quick Replies. Set up customer tags to replicate any tagging or segment system. If you used Crisp's routing rules (Essentials+), configure auto-routing rules with your preferred strategy (round robin or load-balanced). Document Triggers that handled common tasks — welcome messages, FAQ responses — and rebuild these as auto-reply rules with working hours modes and optional A/B testing variants.

Day 2: Features That Work Differently

Crisp's Hugo AI is an autonomous chatbot that handles full conversations (credit-based, ~$0.05/conversation). On most messaging platforms, AI works differently — as reply suggestions that agents review and send, rather than autonomous responses. This gives agents more control but requires them to be present. Crisp's Knowledge Base is a standalone self-service portal; on a messaging platform, this may translate to FAQ entries in the chat widget that customers browse before starting a conversation. Crisp's MagicBrowse (co-browsing) and video calls have no equivalent on messaging-focused platforms.

Week 1: Supervised Practice

Have agents handle real conversations with a team lead available for questions. The adjustment from Crisp typically takes 2–3 days for agents who primarily used the inbox. Agents who relied heavily on Hugo AI for autonomous responses may take longer to adjust to agent-assisted AI suggestions. Use team chat for internal questions during the transition period.

Most teams report the learning curve from Crisp is 2–4 days. The biggest adjustments are moving from Hugo AI's autonomous mode to agent-assisted suggestions, and from Crisp's five-status system (Pending, Unresolved, Resolved, Deleted, Spam) to a simpler three-status model.