Customer service
Omnichannel inbox: manage WhatsApp, Instagram, Messenger, TikTok and web chat in one place
An omnichannel inbox puts every customer conversation, from every messaging channel, into one shared workspace with one history per customer. Here is how it works, what to look for, and how to set one up.
MonoChat Team Updated: 7 min read
On this page
- What is an omnichannel inbox?
- Why move to an omnichannel inbox?
- Which channels belong in an omnichannel inbox?
- Channel rules still apply in one inbox
- What features should an omnichannel inbox have?
- How to set up an omnichannel inbox in 7 steps
- Common omnichannel inbox mistakes to avoid
- How MonoChat brings every channel into one inbox
- Sources
An omnichannel inbox is one shared workspace where messages from WhatsApp, Instagram, Facebook Messenger, TikTok, web chat and other channels arrive in a single list. Your team answers, assigns and follows up from there, and each customer has one profile and one timeline across channels. It replaces the routine of checking four apps, copying context between them and guessing who already replied.
This guide explains what an omnichannel inbox does, how it differs from simply being on several channels, which channel rules still apply, and how to set one up step by step. If your team is mainly on WhatsApp today, our guide to WhatsApp multiple users and team inboxes covers that case in detail.
What is an omnichannel inbox?
At its core, an omnichannel inbox does three things:
- Collects messages from every connected channel into one queue.
- Assigns each conversation to an owner, by rule or by hand.
- Remembers the customer across channels, so the next reply starts with context.
Everything else, such as automation, AI answers, reporting and campaigns, builds on those three.
Multichannel vs omnichannel: what’s the difference?
| Multichannel | Omnichannel | |
|---|---|---|
| Where agents work | One app per channel | One inbox for all channels |
| Customer history | Split by channel | One profile and timeline |
| Ownership | Often unclear | One owner per conversation |
| Switching channels | Customer repeats themselves | Agent sees the earlier chat |
| Reporting | Per app, hard to compare | One set of metrics |
| Automation | Set up separately per channel | Shared rules and assistants |
Being on many channels is multichannel. Connecting them is omnichannel.
Why move to an omnichannel inbox?
- Fewer missed messages. An Instagram DM no longer waits because everyone was watching WhatsApp.
- No double replies. Ownership shows who is handling each chat.
- Faster answers. Agents don’t switch apps or hunt for earlier conversations.
- Consistent tone. Saved replies and one set of guidelines across channels.
- Real numbers. First response time and resolution time measured the same way everywhere. See chat support metrics and SLAs for what to track.
A typical moment it fixes:
Customer on Instagram: Hi, I messaged you on WhatsApp yesterday about the blue sofa. Any update? Agent: Hi Ayla, yes, I can see that chat. The blue sofa arrives in our warehouse on Thursday. Shall I reserve one for you?
Without a shared history, that agent would have to ask what the customer wrote yesterday, and where.
Which channels belong in an omnichannel inbox?
Start with the channels your customers already use to reach you. Common ones:
- WhatsApp Business API: support, order updates, bookings and campaigns with approved templates.
- Instagram DMs: product questions, story replies and comment-to-DM journeys. See Instagram DM automation.
- Facebook Messenger: Page messages and click-to-Messenger ads.
- TikTok: DMs from business accounts and messaging ads. See TikTok business messaging.
- Web chat: a widget on your website for visitors who don’t want to leave the page.
- Telegram, SMS and voice: depending on your market and audience. Telegram for business covers bots and broadcasts.
Channel rules still apply in one inbox
Putting channels side by side doesn’t merge their rules. Each platform keeps its own messaging windows, and your team needs to see them.
| Channel | When you can reply freely | After that |
|---|---|---|
| 24 hours after the customer’s last message or call (customer service window) | Only pre-approved template messages | |
| Messenger | 24 hours after the person’s last message (standard messaging window) | Approved options only, such as the human agent tag for manual replies within 7 days |
| 24 hours after the user’s message | A human agent tag allows manual replies outside the window | |
| TikTok | TikTok’s own reply windows and message caps | Limited follow-ups until the user writes again |
| Web chat | While the visitor is on your site or reachable | Follow up by email or another channel they gave you |
Practical consequences for an omnichannel team:
- Prioritize by window, not only by arrival time. A WhatsApp chat that is 22 hours old is more urgent than a fresh one, because after 24 hours you can only reply with a template.
- Keep templates ready for the follow-ups you know you’ll need. Our template message examples help.
- Use the human agent tag only for real human replies on Messenger and Instagram, never for promotions. Details in the Messenger 24-hour rule.
- Offer a way to a person. WhatsApp’s Business Messaging Policy requires prompt, clear and direct escalation paths when you use automation.
What features should an omnichannel inbox have?
Use this checklist when you compare tools:
- Native connections to the official APIs of each channel, not screen scraping or unofficial apps.
- Assignment and routing by channel, topic, skill, language or workload.
- One customer profile that merges history across channels.
- Internal notes and transfers so colleagues can hand over without the customer noticing a gap.
- Saved replies that work on every channel.
- AI and automation that answer first and hand over with context.
- Templates and campaigns for WhatsApp and the other channels that support outbound messages.
- Roles and permissions so each team sees what it needs.
- Reporting on response time, resolution time, volume and satisfaction, per channel, team and agent.
- Mobile access for agents who aren’t at a desk.
How to set up an omnichannel inbox in 7 steps
- Map your channels. List every place customers contact you today, including the ones nobody officially owns.
- Pick an owner per topic. For example:
Orders, delivery, returns -> Support team
Prices, quotes, stock -> Sales team
Bookings and changes -> Front desk
Invoices and payments -> Billing
Anything else -> First available agent- Connect the channels through their official APIs, starting with the two busiest.
- Write routing rules that match the ownership list.
- Agree on reply targets per channel and set business hours and an away message for after hours.
- Add automation carefully. Start with an AI assistant or flow for the top five questions, with a clear handover to a person. See AI-to-human handoff for triggers and wording.
- Review weekly. Look at unassigned chats, response times by channel and conversations that bounced between teams.
Common omnichannel inbox mistakes to avoid
- Connecting everything on day one. Five new channels at once means five sets of rules to learn. Add one or two, settle the routing, then add the next.
- One queue for everyone. If every agent sees every chat, nobody owns any of them. Route by topic or team, and keep a small “unassigned” view that a lead watches.
- Copying the same reply to every channel. A long paragraph that works in web chat feels heavy in an Instagram DM. Keep saved replies short and adapt formatting per channel.
- Ignoring the windows. A chat that waited 25 hours on WhatsApp needs a template to reopen it. Sort by time left, not only by newest.
- Automating without a way out. Customers who can’t reach a person leave, or complain on another channel. Always show how to get to a human.
- Measuring per app. If WhatsApp, Instagram and web chat are measured with different definitions, you can’t compare them. Use one definition of response and resolution time for all channels.
How MonoChat brings every channel into one inbox
MonoChat’s unified team inbox brings WhatsApp Business API, Instagram, Facebook Messenger, TikTok, Telegram, web chat on your website, SMS through Twilio and voice calls over SIP into one shared workspace. Each conversation keeps its channel, its owner and its history.
What your team works with
- One customer, one thread. When the same customer writes on WhatsApp today and on Instagram tomorrow, your team sees one profile and one timeline, so nobody asks the same question twice.
- Assignment and smart routing. Conversations can be routed by channel, agent skill, workload and priority, and agents or team leads can also assign them by hand.
- Team collaboration. Agent assignment, internal notes, shared ownership and conversation transfer, described on our omnichannel inbox for support teams page.
- Quick replies and smart suggestions for faster, consistent answers, plus team grouping, roles, permissions and working hours on the multi-agent call center page.
- AI first, people next. An AI assistant can answer common questions on every connected channel and hand over to an agent with the conversation.
- Your website, too. The live chat widget adds web chat to any site where you can paste a code snippet, and its conversations land in the same inbox.
- On the go. MonoChat is available on the App Store and Google Play, and the mobile apps are included in every plan.
Getting started
- Sign up at app.monochat.ai. The free Basic plan includes 1 agent and 1 channel, enough to try the inbox on your busiest channel.
- Connect WhatsApp through the official API. If you use the WhatsApp Business app today, Coexistence lets you keep it on the same number.
- Add Instagram, Messenger, TikTok or web chat as you grow, and compare team plans on the pricing page.
Sources
Put this into practice with MonoChat