Unified Inbox: Managing WhatsApp, Instagram and Email in One Place

A unified inbox brings WhatsApp, Instagram, Messenger, email and website chat into one screen so your team answers customers from a single place instead of five. The VivoChat unified inbox goes a step further: an AI agent answers first across every channel using the same knowledge base, and your team picks up only what actually needs a person.

The problem it solves is not really about tabs. It is about the fact that a customer who asks the same question on WhatsApp and by email should get the same answer, and right now, in most stores, they don't.

The real cost of channel sprawl

Most online stores did not choose to be multichannel. It happened. You added a chat widget, then a support email, then WhatsApp because customers kept asking, then Instagram DMs because that is where your audience lives, then Messenger because it came with the Facebook page. Each one arrived for a good reason. Together they create four problems.

Response times get uneven.
The channel someone happens to be watching gets answered in minutes. The others get answered when someone remembers to check. Customers do not know which is which, so their experience of your brand is a lottery.

Answers drift.
Different people answering in different apps produce different versions of your returns policy. Nobody is lying. There is just no single source of truth.

Context disappears.
A customer messages on WhatsApp about a delayed order, then follows up by email. The second person to reply has no idea the first conversation happened, so the customer explains everything again. That is the moment goodwill evaporates.

Things get missed.
Not often, but expensively. The missed message is usually the pre-sale question from someone about to spend money.

None of this is a discipline problem. It is a structural one, and adding another app to check makes it worse.

What a unified inbox actually means

There is a weak version and a strong version of this idea, and the difference matters when you compare tools.

The weak version is aggregation: all your channels appear in one interface. Useful, and it saves your team from app-switching, but it is essentially a better window onto the same mess. You still answer everything manually, and consistency still depends on whoever is typing.

The strong version is consolidation: one inbox, one customer history, and one shared brain answering across all of them. The channel becomes a delivery detail rather than a separate workflow. That is the version worth paying for, and the one VivoChat is built around.

How the VivoChat unified inbox works

Every channel lands in one place. Website chat, email, WhatsApp, Instagram, Messenger and Telegram feed into a single inbox. Instagram messages, comments and DMs arrive there too, so questions from the channel your marketing actually works on do not sit in a separate app waiting for someone to notice them.

The AI agent answers first, everywhere. This is the part that changes the workload rather than just the interface. The Vivo AI Agent handles the repetitive volume, order status, shipping, returns, availability, product and policy questions, on whichever channel it arrives. VivoChat reports up to 70% of repetitive conversations automated from day one, average first response times near 30 seconds, and support costs cut by around half.

One knowledge base, so one answer. The assistant trains on the material you already have: help centre articles, FAQs, product pages, PDFs, Notion pages and your past conversations. Because every channel draws on the same source, the WhatsApp answer and the email answer match. Consistency stops being a training problem and becomes a configuration one.

Sales conversations get handled as sales conversations. Many inbox tools treat every message as a ticket. Alongside the support agent, the Vivo Shopping Assistant uses your product catalog and real-time shopping behaviour to recommend products, which matters because a large share of inbound messages, especially on social and WhatsApp, are pre-purchase questions from people deciding whether to buy.

Humans get the conversations that need humans. Complex, sensitive or ambiguous cases escalate to your team with the full conversation attached, so nobody starts from scratch and the customer does not repeat themselves.

It grows without a migration. When you need more, you add specialised agents for billing, onboarding, sales or retention from the marketplace in one click, instead of switching platforms.

Why the shared knowledge base matters more than the shared screen

If you take one thing from this article, take this. Putting five channels on one screen fixes your team's ergonomics. Putting five channels behind one knowledge base fixes your customer's experience.

Consider a customer who asks about your return window. On the website widget she gets 30 days. On WhatsApp, from a teammate working from memory, she gets "about a month." By email, from someone reading an outdated macro, she gets 14 days. Every answer was given in good faith. The customer's conclusion is that your store does not know its own policy, and that conclusion is expensive.

A single knowledge base makes that failure mode structurally impossible. Update the policy once and every channel is correct immediately. This is also why the knowledge base is the thing to invest in after launch: every conversation where the assistant answered poorly is a gap in your documentation that your customers just found for you.

What each channel is actually used for

The channels behave differently, and knowing how changes what you configure.

Website chat is the highest-intent channel. People here are on a product page, deciding. Speed and recommendation quality matter more than politeness, and this is where a shopping assistant earns its place.

Email is where longer, more complex issues live: disputes, warranty claims, B2B enquiries, anything with an attachment. Response expectations are looser, but the answers need to be thorough and traceable.

WhatsApp is the highest-expectation channel. Customers treat it like texting a friend, so a delay of hours reads as being ignored. It is also where order tracking and quick pre-sale questions concentrate, which makes it ideal for automation.

Instagram is the channel most stores handle worst, and the one with the most upside. DMs and comments arrive in bursts tied to campaigns and posts, they come from people at the top of the funnel who have just discovered you, and comments are public, so a slow reply is visible to everyone else considering the product. Treating Instagram as marketing's problem rather than support's is why so many of these conversations never turn into orders.

Messenger tends to be lower volume than it used to be, but it stays connected to your Facebook presence and to ad traffic. Its main risk is being forgotten, which is exactly the risk a unified inbox removes.

Telegram is regionally concentrated but heavily used where it is used, and often skews toward repeat and more technical customers. Cheap to support once it sits in the same inbox, easy to neglect when it does not.

What changes after you consolidate

Three things move, and they are worth measuring separately so you know what you actually got.

First response time. This drops immediately and across every channel, because the AI answers before a person is available. It is the easiest win and the one customers notice first.

Ticket volume reaching your team. The repetitive questions stop arriving as work. Your team's queue becomes shorter and, importantly, more interesting, which is not a small thing for retention on a support team.

Revenue from conversations. This is the one most stores never measure. Pre-sale questions answered in seconds convert better than pre-sale questions answered in an hour, and messages that used to sit in a neglected social inbox turn into orders.

If you only track deflection, you will see half the value and undersell the project internally.

Setting it up

The sequence that works, in order:

1. Install and connect the store. VivoChat installs on Shopify in minutes with no code.
2. Feed the knowledge base first. Policies, FAQs, product documentation, past conversations. Do this before connecting more channels, because it is what the assistant answers from.
3. Add channels one at a time. Start with the two that carry the most volume, usually website chat and email, then WhatsApp, then the rest. Adding all five on day one makes it harder to see what is working.
4. Set escalation rules explicitly. Decide what the assistant must never answer alone. Anything medical, legal, financial or dispute-related belongs with a human.
5. Read transcripts weekly for the first month. Failed conversations are your content backlog. Fix the knowledge base, not the prompt.
6. Then expand. More channels, more specialised agents, more automation, once the basics are reliable.

Who this is for

A unified inbox is worth the effort if you recognise two or more of these: your team checks more than three apps to answer customers, the same question gets different answers depending on who replies, social DMs go unanswered for a day or more, customers repeat their story when a conversation moves channels, or your first response time is fine on one channel and embarrassing on another.

If you are a single founder answering everything from one inbox, you probably do not need this yet. You will, and sooner than you expect.

‍

FAQ

What is a unified inbox?
‍A single interface where customer messages from every channel arrive together: WhatsApp, Instagram DMs and comments, Messenger, Telegram, email and website chat. The strong version also shares one customer history and one knowledge base across those channels, so answers stay consistent no matter where the question came from.

Do I need separate tools for WhatsApp and email support?
‍No, and using separate tools is what creates inconsistent answers and lost context. Handling both in one inbox means a customer who switches from WhatsApp to email does not have to explain their situation twice.

Will the AI answer on every channel or only on the website?
‍On every connected channel. That is the point of a shared knowledge base: the assistant is not a widget feature, it is the layer answering first wherever the message arrives.

What happens when the AI cannot answer?
‍It escalates to your team with the conversation attached, so whoever picks it up has the full context. You define which topics must always go to a human.

Does consolidating channels mean customers get slower replies?
‍The opposite. Uneven response times come from channels nobody is watching. When everything lands in one place and an AI agent answers first, the slowest channel improves the most.

Can I start with just one or two channels?
‍Yes, and you should. Connect your highest-volume channels first, get the knowledge base right, then add the rest.

How much does it cost?
‍VivoChat is free to start, so you can validate the setup on real traffic before spending anything

‍

Bring every channel into one inbox

If your customer conversations are currently spread across a chat widget, a support mailbox, WhatsApp, Instagram DMs and comments, Messenger and a Telegram account nobody owns, the fastest way to see what consolidation is worth is to run it on your own traffic for a week. VivoChat brings all of it into one inbox, trains on the FAQs, policies and past conversations you already have, answers the repetitive volume automatically across every channel with the same source of truth, recommends products to shoppers who are still deciding, and escalates the rest to your team with full context. It installs on Shopify in minutes with no code and it is free to start, so you can measure the effect on response time, ticket volume and revenue before committing a budget. Get started for free, or see how the product works first.

‍