Channel Breadth
Email (standard MX/forwarding setup), Chat (via Freshchat), Phone (via Freshcaller), Facebook, X/Twitter, WhatsApp Business, Apple Business Chat, Instagram DM, and Line in supported regions. Each channel needs distinct setup: email requires SPF/DKIM records and either MX delegation or forwarding from your existing inbox; WhatsApp requires a Meta Business Manager verified account and a 24-hour service window awareness; Instagram needs the page connected at the Meta side and accepted at the Freshchat side. Don’t enable channels you don’t have agents to staff — every connected channel inherits SLA expectations.
Unified Ticketing
All channels create tickets in one queue under Freshdesk Omnichannel. Agents see the source channel as a colored badge and routing rules can branch on it. Customer experience stays consistent because contact records merge across channels using email and phone as primary keys. The platform deduplicates a customer who emails on Monday and chats on Tuesday into one contact with both threads linked. The catch: WhatsApp identifies by phone number while email identifies by address, so a customer using a personal phone and a corporate email looks like two contacts until you manually merge them or set up the contact merge automation.
Routing
Skill-based routing across channels uses the IntelliAssign engine. Agents are tagged with skills (spanish, tier_2, billing, enterprise_account) and incoming tickets carry tags from the dispatcher. Ticket-based routing handles email and social (assign once, agent works async), real-time routing handles chat and phone (must assign to an online agent within seconds or fall back to a queue). Configure overflow groups for every real-time channel — without them, a chat that arrives when no skilled agent is online sits in limbo and the customer abandons.
Agent Experience
Single agent UI across channels means one inbox, one history view, one set of keyboard shortcuts. Response templates (canned responses) can be tagged per channel — a formal email template for email replies, a short conversational version for chat. Agents switch channels with Cmd+K quick actions. Audio and video calls launch from the contact card if Freshcaller is provisioned. Private notes are channel-agnostic, so internal comments stay attached to the ticket regardless of where the customer reached out.
Reporting
Channel mix (volume share per channel), handle time per channel (chat is typically 3-5x faster than email), CSAT per channel, and first-response time per channel. Use these metrics to drive staffing decisions — if 60% of volume comes from chat but 60% of headcount is on email, response times will diverge. Build a weekly stacked bar of inbound by channel and overlay agent capacity; the gap is where you reassign.
Common Failure Modes
The big three. First, WhatsApp’s 24-hour service window: agents respond to a customer message after 24 hours and the message bounces with a 131047 template-required error — train agents to use approved Message Templates for follow-ups. Second, email loops created when an auto-responder on the customer side replies to your auto-responder; add a Precedence: bulk header check or a same-subject suppression rule. Third, social-channel rate limits (Instagram caps DMs per page per hour); large promotions trigger throttling and tickets pile up out-of-order.
Implementation Sequence
Start with email + one chat channel. Run for 30 days. Add phone next because real-time routing requires the most operational change. Add social channels last because each platform’s policy quirks (Meta Business verification, X API tier costs) need procurement involvement. Don’t try to launch all channels in one week.
What to do this week
Audit which channels are enabled but unstaffed. Disable any channel without a named agent group and a published SLA — an unstaffed channel is worse than no channel because customers feel ignored.
