How to manage WhatsApp, Instagram, and web chat from one inbox
Stop switching between four apps to answer one customer. A practical guide to consolidating your channels into a single queue.
Most small teams do not choose to run four inboxes. They arrive at it. WhatsApp Business goes on someone’s phone because a customer asked. Instagram DMs stay with whoever runs the account. A chat widget gets added to the website during a redesign. Messenger has been on since the Facebook page existed.
Each one made sense on its own day. Together they produce a specific kind of failure: nobody can answer the question “how many people are waiting for us right now?”
The three costs of a split inbox
Response time becomes a function of who happens to be looking. A message on the channel nobody has open sits there. It is not that the team is slow; it is that the queue is invisible.
Context does not travel. A customer who asked about availability on Instagram and then messaged WhatsApp to book is two strangers to you. They have to repeat themselves, which is the single most reliable way to make a fast reply feel slow.
Nothing is countable. You cannot improve a response time you cannot measure, and you cannot measure one that lives in four apps with four different notions of “read”.
What “one inbox” actually has to do
Consolidation gets sold as a feature. It is really four separate problems, and a tool that solves three of them still leaves you switching apps.
1. One queue, with a real state per conversation
Merging messages into one list is the easy half. The half that matters is that every conversation carries a state — open, in progress, escalated, resolved, abandoned — and that the state is the same word on every channel. Without it you have a longer list, not a queue.
Pay particular attention to abandoned. Conversations that go quiet are the ones a split inbox hides best, and they are the ones worth counting: they are the shape of demand you failed to serve.
2. One contact, not one contact per channel
The same person messaging from Instagram and WhatsApp must resolve to one record, with one history. This is the requirement most often skipped, because it is invisible until the moment it matters — which is always a moment when a customer is being asked something they already told you.
3. Routing that survives the channels growing
Assign people to channels and numbers rather than to individual conversations. “Whoever sees it first” works at two channels and fails at five. If your tool makes you route by hand, you have moved the problem rather than solved it.
4. One place where outcomes are recorded
A conversation that ends is either won, lost, resolved, or still open. If that outcome lives in a spreadsheet next to the inbox, it will drift within a month. It has to be a property of the conversation.
The order to do it in
Teams usually try to connect everything on day one, and the rollout stalls because the busiest channel is also the most disruptive to move.
A better order:
- Start with the channel with the most volume, alone. One channel in the new inbox, everything else where it is. You learn the tool on the traffic you understand best.
- Add the channel with the most value next — usually not the same one. For most businesses that is WhatsApp, because it is where buying conversations happen.
- Add the rest together. By now the queue states and the routing rules are settled, so the remaining channels are configuration rather than change management.
- Turn off the old surfaces deliberately. A phone with WhatsApp Business still installed will keep receiving messages that never reach the queue. This step gets forgotten and it is the one that undoes the project.
What to measure once it is one queue
The point of consolidating is that these become answerable at all:
- First response time, per channel — the number that tells you whether the queue is staffed
- Resolution time — whether conversations end or just stop
- Abandoned conversations — demand you did not serve
- Share of conversations handled without a human — the only honest measure of whether automation is helping
If you cannot get those four out of your setup, the inbox is unified in appearance only.
Where an AI agent fits
The repetitive half of most inboxes is genuinely repetitive: opening hours, availability, price, where is my order, do you do X. An agent that answers those from your own information does not replace the queue — it shortens it, so the conversations a person sees are the ones that needed a person.
The thing to insist on is that the agent answers from what you gave it and nothing else. An agent that improvises is worse than no agent, because it produces confident answers you have to go back and correct.
Fellix puts WhatsApp, Instagram, Messenger and website chat in one queue, with one contact record behind them and an AI agent answering the repetitive half. See how the Front Desk works.