Field notesARTICLE
One Queue Instead of Five Tabs
The same customer asked on Instagram, then WhatsApp, then email. Three people answered and gave three prices. Nobody was careless — the three of them could not see each other.
Costa3 min read
Short answer
A customer who writes on three channels is one customer, and most support setups treat them as three. The fix is not discipline or a rota; it is a single queue where the second message arrives attached to the first, so the person answering can see what has already been promised.
Key facts
- OmniAI puts social, messengers and email into one thread per customer rather than one inbox per channel.
- A returning customer is matched by handle, phone or address, so the second message opens the first conversation.
- Whatever was quoted, promised or refused travels with the thread.
- When a person takes over, they take over the whole thread, not the latest message in it.
A shop we looked at answered the same customer three times in one afternoon and gave three different prices. Nobody was careless. The Instagram DM went to whoever had the phone, the WhatsApp message went to the sales line, and the email went to a shared address that two people watch. All three answered within an hour, which by most measures is a good day.
The customer read all three.
What each of them could see
The first answer quoted the list price, because that is what the catalogue says. The second offered the returning-customer discount, because that account had bought twice before and WhatsApp was where the previous order lived. The third said the item was out of stock, which was true that morning and had stopped being true by lunchtime.
Every answer was defensible on its own. Together they said the company does not know what it charges.
The join has to happen on the person
The usual fix is a shared inbox, and it does help: four apps become one screen. But a shared inbox joins the channels, not the customer. The same person still arrives as three threads, because their Instagram handle, their phone number and their email address have nothing in common as far as the software is concerned.
What has to happen instead is duller and more useful. When the WhatsApp message comes in, the number is matched against the CRM, the previous order surfaces, and the thread opens with the discount already visible. When the email arrives an hour later, it lands in the same thread rather than starting a new one.
Then the third answer is not an answer at all. It is somebody reading two lines of history and writing "as I said this morning".
Where the assistant sits in that
It answers first, on all three, and it is the same assistant, so the three replies agree. That is most of the value and it is unglamorous: consistency at the point where three humans, working normally, could not have produced it.
It also does the matching, and it asks rather than guesses. Two accounts with the same name and different numbers stay two accounts until somebody confirms. A wrong merge shows one customer another customer's order history, which is a much worse failure than an unlinked thread.
What the person gets
The handover is the whole thread, not the message on top of it. Someone picking it up at four in the afternoon can see the price already quoted at eleven, and will not undercut it by accident.
That is the actual change: not faster replies, though they get faster. It is that the company answers with one voice on a Tuesday, without anybody having to remember what somebody else said.
The assistant that does this is OmniAI, and the thing it needs from you first is a customer record it can match against. What else it needs is in an earlier note.
Questions this raises
- Is this not just a shared inbox?
- A shared inbox joins the channels. It does not join the customer: the same person still arrives as three threads because the address is different in each. The join has to happen on the customer, which is why it has to touch the CRM.
- What if the same person uses two phone numbers?
- Then the assistant asks, once, and links them. It does not merge two people on a guess — a wrong merge puts one customer's history in front of another and is much worse than an unlinked thread.
- Do we lose the channel-specific tone?
- No. The thread is joined; the reply still goes out in the channel it came from and reads like that channel. Nobody wants an email in their Instagram DMs.