Omnichannel inbox: managing every message in one place

Short answer

Managing WhatsApp, Instagram and website messages from one place takes more than connecting the channels to one screen. A shared omnichannel inbox works when every conversation has one owner, a clear status and a visible bot state, and the team works from the same views (saved filters). The technology connects in a day; the rules need to be written in the first two weeks.

This guide sets out the inbox's daily operating model: which views you need, how ownership is assigned, how the bot and an agent share one conversation, and which numbers show the inbox is healthy.

What an omnichannel inbox is, and is not

An omnichannel inbox is a workspace where messages from every written channel appear in one list, tied to one customer profile. The agent does not log in to WhatsApp, Instagram and the website panel separately: everything is on one screen, and the reply goes back to the channel the customer wrote in.

The inbox is not the strategy. Which channels to connect, how to design the customer experience and what outcome to expect are separate decisions — covered in the omnichannel customer service guide. This piece is about the part of that strategy that runs every day.

What separate windows cost

When channels are run separately, the problems pile up quietly. Nobody says "we lost a message", but the same symptoms keep coming back:

• A question on Instagram goes unanswered because everyone was watching WhatsApp that day.
• Two agents give the same customer different answers — one in a DM, the other on WhatsApp.
• A customer who writes from a second channel has to introduce themselves again.
• A manager cannot answer "how many enquiries went unanswered yesterday?" because the count lives in five places.

All of these have one cause: nowhere records who owns the conversation and what state it is in.

Five rules for a shared inbox

• One conversation, one owner. Unowned conversations get their own view and stand out.
• Every conversation has a status: open, waiting (on the customer), needs an agent, closed.
• Internal notes never reach the customer and everyone sees them in the same place — not in a WhatsApp group.
• Whether the bot is active in this conversation is visible at a glance.
• Channel differences are written down: which answers go in a public comment and which in a private message.

Views: what the team should look at

A view is a saved, filtered list of the inbox. When every agent looks at the full list, the important conversation sinks to the bottom. Five views are enough for most teams:

1. 1UnassignedNew conversations without an owner. This is the shift lead's main screen.
2. 2My conversationsThe agent's own open conversations, oldest unanswered first.
3. 3Needs an agentConversations where the bot stopped or the customer asked for a person.
4. 4LeadsConversations where a number or clear interest appeared and that must go to sales.
5. 5WaitingConversations waiting on the customer — nobody needs to rush here.

How ownership is assigned

Ownership comes about in one of two ways: automatically by rule (by channel, rotation or workload), or an agent picks the conversation up. Whichever you use, one condition holds: once a conversation is taken, nobody else replies in it. A second agent who wants to help writes an internal note.

When an agent goes off shift, open conversations are either closed or handed over to a named colleague. A conversation left with "I'll look tomorrow" becomes tomorrow's most delayed one. The distribution rules themselves — which channel goes to whom, what happens outside working hours — belong in a separate routing policy.

The bot and the agent in one inbox

Some conversations in the inbox are being answered by a bot. The single most important fact for an agent is whether the bot is still talking in this conversation. When it is unclear, two mistakes happen: the agent writes at the same moment as the bot and the customer gets two answers, or everyone assumes the bot is handling it when it has already stopped.

The rule is simple: when an agent enters a conversation, the bot stops in that conversation and the screen shows it. Whether to switch the bot back on when the agent is done is a separate decision. The handover moment itself is covered in moving from chatbot to a live agent.

Channel differences when replying

One screen does not make the channels the same. Agents need to know the differences, or the right answer goes out in the wrong form:

• WhatsApp: once 24 hours have passed since the customer's last message, free-form text can no longer be sent — only an approved template. That is why a late reply "does not go".
• Instagram and Facebook: a public reply to a comment is visible to everyone. Prices, phone numbers and personal details belong in a private message.
• Website widget: the visitor may be anonymous, and closing the page ends the chat. Ask for contact details early.
• Phone: a call appears in the inbox as a note and an outcome, but nobody replies to it in writing.

A daily rhythm

1. 1Morning, 10 minutesOvernight and unassigned conversations are distributed; WhatsApp chats close to the 24-hour limit go first.
2. 2Every hourThe shift lead checks the Unassigned and Needs-an-agent views.
3. 3AfternoonOld conversations in Waiting get one reminder or are closed.
4. 4End of dayEvery open conversation is closed or handed to a named colleague, with an internal note.

An illustrative example

This is an illustrative example. In a furniture shop, four agents watched WhatsApp, Instagram and the website chat separately. In the first week on a shared inbox it became clear that some Instagram DMs stayed unowned until morning: a question written at night got lost beneath the morning WhatsApp queue.

The team added two rules: the first ten minutes of the morning go to the Unassigned view only, and no conversation is left without an owner at the end of the day. In the following weeks they started tracking how many conversations were still unanswered each morning.

How to measure the inbox's health

• The number of unassigned conversations, and the age of the oldest one.
• Time to the first human reply — separately per channel.
• Cases where two different agents wrote to the same customer on the same day.
• Conversations reopened within 48 hours of being closed.

Measuring response time correctly across channels is a topic of its own: you have to agree in advance when the clock starts and when it stops.

Limitations

A shared inbox does not fix a wrong answer: if the knowledge base is out of date, the bot and the agents will keep quoting the old price. Platform limits remain too — WhatsApp's 24-hour rule and Instagram's comment rules do not depend on your inbox. Finally, an inbox does not replace headcount: if the volume of enquiries exceeds what the agents can handle, the views will only show the problem more clearly.

The inbox in Vexvon

In Vexvon, messages from WhatsApp (the official Business API), Instagram, Facebook, TikTok, Telegram and the website widget land in one inbox and are written to one customer profile. A conversation can be assigned to an employee, closed and searched; an agent can switch the bot off in a conversation or pause it for 30 minutes with the company's stop symbol. The agent's reply goes back to the channel the customer used. Internal notes are not sent to the customer. The channel list and how to connect them are on the integrations page.

Next step

Run one simple check this week: how many conversations across all channels have no owner right now, and how many hours has the oldest one been waiting? The answer shows which of the five rules to write first. More articles are in the omnichannel communication section, and we can set up the inbox with your own channels during a demo.