One inbox for Instagram, Telegram, WhatsApp and Viber
Your customers do not think in channels. They open whichever app is already on the screen. The cost of that lands on one manager with six tabs open.
A Ukrainian store with three people in support typically runs six inboxes: an Instagram business account on someone's phone, a Telegram bot, WhatsApp Business, Viber, the chat widget on the site, and a shared mailbox. Each one has its own notifications, its own history and its own idea of who replied last.
Nothing about that setup is unusual. It is simply how a business grows: a channel is added the week a customer asks for it, and nobody ever goes back to consolidate.
What an omnichannel inbox actually is
An omnichannel inbox is one queue that receives messages from every channel through the platforms' official APIs, and sends replies back out through the same channel the customer wrote in. The customer stays in Instagram. Your manager stays in one window.
Three things make it different from simply having several apps open:
- One identity per customer. A person who wrote in Viber in March and in Instagram today is one profile with one history, not two strangers.
- One queue with one order. New, waiting, assigned, resolved — for all channels at once, so nothing is answered twice and nothing waits because a tab was closed.
- One place where the answer lives. The order, the delivery policy and the past conversation are next to the message, not in four other systems.
Omnichannel is not about being present in more places. It is about the customer never noticing how many places you are in.
The hidden costs of the six-tab setup
History disappears with the phone
When Instagram lives on a personal phone, the conversation history belongs to that phone. A manager leaves, and three years of context leaves with them. Every returning customer starts from zero.
Nobody can see the actual load
If a team has six inboxes, nobody can answer "how many questions came in yesterday, and how long did people wait?" The answer exists in six places and in none of them. Planning shifts becomes guesswork. Read more on this in support metrics that are worth counting.
The same question is answered five different ways
Without a shared source, each manager answers delivery questions from memory. The answers drift apart, and the customer who asks twice gets two different rules.
Sales fall through the gap
A first message in Direct is a lead. In a personal inbox it is a lead nobody tracks — no owner, no source, no follow-up. We wrote about closing that gap in selling in Direct without losing orders.
What to check before you choose one
Most tools show the same screenshot of a unified inbox. The differences live under it.
| Check | Why it matters |
|---|---|
| Official APIs for every channel | Grey integrations that log into an account with a password get blocked, and take your account with them |
| One customer profile across channels | Without identity merging you have a channel list, not an omnichannel inbox |
| Full history retained on transfer | A ticket handed to a colleague must carry the whole thread, not a screenshot |
| Assignment rules | Route by channel, language, keyword and load, or your queue is just a longer list |
| Knowledge attached to the reply | An answer without a source cannot be checked, by a manager or by a customer |
| Pricing model | Per seat pricing punishes you for adding the colleague who answers twice a week |
Message windows differ by platform. Instagram and WhatsApp restrict what you may send after a period of customer silence, and the rules are the platform's, not the tool's. Any vendor promising unlimited outbound messaging in those channels is describing something that will eventually be blocked.
Moving six channels into one queue
A migration that works in practice takes about a week, and the order matters.
- Start with the noisiest channel, not the smallest. If most questions arrive in Instagram, connect Instagram first. The team feels the benefit immediately and the rest becomes easy to argue for.
- Write down the twenty questions you answer every day before connecting anything else. These become the first knowledge base entries — see how to build a knowledge base an AI can actually answer from.
- Decide who owns what. Assignment rules encode decisions you are already making informally: who takes Instagram, who takes email, what happens to a question in Polish.
- Connect the remaining channels one per day. One at a time keeps a failed connection from looking like a failed project.
- Keep the old apps open, read-only, for two weeks. Confidence comes from seeing that nothing is missing, not from being told.
- Then turn on AI drafts. Once the knowledge base has real content behind it, the drafts have something to be right about.
What changes in the first month
The number teams notice first is the first response time — it usually drops from tens of minutes to under two, because a message is seen the moment it arrives instead of when someone opens the right app. The second is the share of questions answered without asking a colleague, which is what a shared knowledge base buys you.
The one nobody predicts: the evening queue disappears. Questions that used to pile up between 18:00 and 09:00 get answered as they arrive, because the simple ones do not need a person at all.
Supporter is an omnichannel inbox with the knowledge base built in: AI drafts the answer from your own documents and shows the paragraph it used, and a manager approves anything it is not certain about. See how the AI decides what it knows.
Frequently asked
Is an omnichannel inbox the same as a chatbot?
No. A chatbot answers on its own from a script or a model; an omnichannel inbox is the workplace your team answers from. Supporter has both: the inbox is the product, and AI drafts replies inside it for a person to approve.
Will customers know we moved to a new tool?
No. Replies go back through the same channel by its official API, so a customer sees a normal Instagram or Telegram message from the same account.
Can we keep our CRM?
Yes, and you should. An inbox handles the conversation; the CRM keeps the orders and the money. They should exchange data, not replace each other — see HelpDesk or CRM.