What is the difference between an omnichannel inbox and a shared inbox?

A shared team inbox lets many agents work one WhatsApp number; an omnichannel inbox combines several channels into one workspace. Most omnichannel inboxes include shared-inbox features for each channel.

Can an omnichannel inbox reply on WhatsApp after 24 hours?

Only with an approved template. The inbox sends replies through the WhatsApp Cloud API, so WhatsApp's rules still apply: free-form messages within the 24-hour service window, templates outside it.

How does an omnichannel inbox know two messages are from the same customer?

By matching identifiers such as a phone number or email address across channels. Reliable inboxes merge only on verified matches and let agents merge or split profiles by hand.

Is omnichannel the same as multichannel?

Not quite. Multichannel means offering several channels; omnichannel means connecting them so history, routing and reporting are shared. An omnichannel inbox is what makes that connection visible to agents.

Ledger entryNo. 167294

Omnichannel Inbox

Also called: Unified inbox · Multichannel inbox · Unified agent workspace

Support & operations
Foundation
Support teams
Business owners

Definition: One agent workspace that merges WhatsApp, Instagram, Messenger, SMS and email conversations into a single queue and customer timeline.

Support & operations

Mode · venn

Work it out

How many of your customers live on more than one channel?

4 / 4

Overlap

In all three sets

8504.0% of everyone

Customers who wrote on all three channels. Without an omnichannel inbox, each of them could be answered by three agents who cannot see each other's replies.

Audience counts
Audience	Total	Only here
WhatsApp	12,000	11,150
Instagram DM	4,200	3,350
Email	6,500	5,650
In all three	850
Unique people	21,000

Illustrative counts of customers who contacted a retailer by WhatsApp, Instagram and email in a quarter. Step through each set, then the overlap — the people who need one merged timeline most.

What is an omnichannel inbox?

An omnichannel inbox is a single agent workspace that collects customer conversations from several messaging channels — typically WhatsApp, Instagram Direct, Facebook Messenger, SMS, email and website chat — into one queue, with one timeline per customer and shared assignment, tagging and reporting. An agent answering a WhatsApp chat can see that the same customer emailed yesterday and sent an Instagram DM last week.

Behind the screen, each channel is still its own integration. WhatsApp messages arrive through Cloud API webhooks, Instagram and Messenger through Meta's Messenger Platform webhooks, SMS through an operator or aggregator, and email through IMAP or an inbound-mail service. The inbox normalises them into one conversation model and sends each reply back on the channel it came from, respecting that channel's rules.

It is not the same as a shared team inbox. A shared team inbox lets many agents work one WhatsApp number together; an omnichannel inbox adds the cross-channel layer on top. It also differs from omnichannel orchestration, which decides which channel a business should use to send outbound messages, whereas the inbox is where inbound conversations are handled.

Key takeaways

An omnichannel inbox puts WhatsApp, Instagram, Messenger, SMS and email conversations into one queue and one customer timeline.
Its hard problem is identity: matching a phone number, an Instagram account and an email address to the same person.
Each channel keeps its own rules — WhatsApp's 24-hour service window and templates do not apply to email, for example.
A shared team inbox is many agents on one WhatsApp number; an omnichannel inbox is many channels in one workspace.

Why does an omnichannel inbox matter?

Customers do not think in channels. When one person messages on WhatsApp, follows up by email and complains on Instagram, separate tools mean three agents, three answers and no single history. A merged timeline stops duplicate work, lets supervisors staff one queue instead of five, and makes metrics such as first response time comparable across channels. It also makes it obvious which channel carries the most volume, which shapes where automation pays back first.

How does an omnichannel inbox work?

Connect each channel
Link the WhatsApp Business API number, the Instagram professional account and Facebook Page, the SMS sender and the support mailbox. Each brings its own webhook or polling connection and credentials.
Normalise into one model
Every inbound item becomes a message with a channel, an external ID (for WhatsApp, the wamid), a sender identifier and content. Unsupported content types are shown as placeholders rather than dropped.
Resolve identity
Merge identifiers into one customer profile using deterministic matches — a phone number seen on WhatsApp and SMS, an email captured in a WhatsApp Flow — and let agents merge or split profiles by hand when matching is uncertain.
Route one queue
Apply the same auto-assignment, skills and SLA rules across channels, optionally weighting chat channels above email because customers expect faster replies there.
Reply on the right channel
Send the answer back where the customer wrote, applying that channel's rules: on WhatsApp, free-form inside the 24-hour service window and an approved template outside it.

Costly mistakes

Common mistakes with an omnichannel inbox

Merging profiles too eagerly
Matching on a name or a shared office phone can merge two customers and expose one person's history to another. Merge on verified identifiers only and keep a manual unmerge.
Applying one channel's rules to all
Email has no 24-hour window, WhatsApp does, and SMS in India needs DLT-registered templates for commercial traffic. The inbox must enforce each channel's rules at send time, not assume WhatsApp's for everything.
Blending SLAs that should differ
A five-minute target suits WhatsApp chat but not email. Set targets per channel or priority, then report them together.
Losing rich content in translation
Buttons, lists, reactions and Flows do not exist on every channel. Show what the customer actually saw and do not send an interactive message to a channel that cannot render it.

The figures

An omnichannel inbox: key facts and limits

Typical channels: WhatsApp, Instagram, Messenger, SMS, email, web chat
WhatsApp reply rule: Free-form within 24 h of the customer's last message; template after
Instagram and Messenger: Separate Meta webhooks with their own messaging windows
WhatsApp billing: Per delivered message by category since 1 July 2025
Hardest problem: Matching identities across channels

Example: An Ahmedabad fashion retailer merges three channels

An Ahmedabad apparel brand gets about 2,500 WhatsApp chats, 900 Instagram DMs and 600 support emails a week, handled in three tools by three teams. After moving to an omnichannel inbox it finds that roughly one in eight customers used two or more channels for the same order. Merged timelines end duplicate refunds, one roster covers all channels, and the team sets a 10-minute target for chat channels and a 4-hour target for email.