Unified Inbox

How it works

Without a unified inbox, a support team monitors separate platforms: a live chat tool, a shared Gmail inbox, a WhatsApp Business account, and possibly a social media monitoring tool. Tickets can be missed when an agent assumes another team member is covering a specific channel. Context is siloed — the agent handling chat doesn't know what the same customer said by email yesterday.

A unified inbox solves this by routing all inbound messages to a single queue with a shared assignment system. Tickets can be claimed, assigned, or auto-routed. Agents see the customer's full channel history in the conversation sidebar. SLA timers run from first contact regardless of channel.

The quality of a unified inbox depends on the depth of integration. Surface-level unification shows all channels in one place but doesn't share customer identity or conversation threading. True unification matches the customer across channels and presents a single timeline.

When you'll encounter it

Unified inbox is a marketing term used by almost every support platform. You'll encounter it in product tours, vendor comparisons, and enterprise RFP requirements. Always test cross-channel context persistence during a trial — does context actually carry across channels, or is each channel's history visible only in that channel's tab?