What is a unified inbox?
A unified inbox is a single queue that holds every inbound customer conversation, no matter which channel it arrived on. Chat, email tickets, phone calls, social DMs, and SMS all share the same primitive: a conversation with a channel field.
Definition
Most customer-support platforms started as one-channel tools. Intercom was live chat. Zendesk was email tickets. Aircall was phone. When you wanted more channels you bolted another product on top, paid a separate per-seat fee for each, and reconciled the customer record across three databases.
A unified inbox collapses that. Every contact is the same kind of object, a conversation with a timestamp, a status, an assigned agent, and a thread of messages. The only thing that varies between a chat and a phone call is the value of one field, the channel.
The engineering model
In code, this is one resource with one schema. message.com's Conversations endpoint returns rows that look like this:
| Field | Meaning |
|---|---|
channel | chat, ticket, or call. The only thing that distinguishes a phone call from a chat. |
visitorId | Pointer to a single visitor record. One visitor has many conversations across channels. |
assignedAgentId | Whoever owns the conversation right now. Same field for chat agents and phone agents. |
status | Same state machine across all channels: open, pending, solved, spam. |
messages[] | The thread. Chat messages, email replies, and call transcripts all live here. |
The implication: an agent who answered a customer's chat last week sees that customer's incoming call land on the same conversation thread, with the chat history scrolled right above it.
Why it matters
Customer experience
Customers stop having to re-explain themselves. The agent who picks up the phone already sees the chat from yesterday and the order number that came in via email last Tuesday. No transfers, no "hold on while I pull up your account".
Agent efficiency
One queue, one set of keyboard shortcuts, one report. Agents stop swivel-chairing between five tabs.
Unit economics
One product on one bill. message.com charges a flat plan price for unlimited agents regardless of channel mix. The competing stack (Intercom live chat + Zendesk tickets + Aircall phones + a separate AI add-on) typically costs three to five times more per agent per month, plus the per-seat tax.
The AI implication
RAG-grounded AI quality is bounded by context. A separate-tool stack means the AI on each tool sees only that tool's history. With a unified inbox, the AI that drafts a reply has the customer's entire history across every channel, every chat, every ticket, every call transcript, as context. The drafts are dramatically better.
This is why the unified-inbox model is not just an interface choice. It is the precondition for the AI features we ship on top.
See AI overview for how the platform feeds the unified history into the model context window.
What it is not
A unified view stitched together from three separate APIs is not a unified inbox. If the underlying data lives in three databases, the consistency, search, and AI-context problems are all still there. The merger has to happen at the storage layer, not just the dashboard.
Related reading
- Conversation, the primitive itself.
- Channel, the field that distinguishes chat vs ticket vs call.
- Visitor vs contact vs user, the related identity model.
- Conversations API, how to read it.
- Omnichannel (Wikipedia), the broader industry term.