Omnichannel support: WhatsApp, Instagram and email in one inbox

A customer sends an Instagram DM asking about pricing. She doesn't hear back, so the next day she sends a WhatsApp message. The teammate who handles WhatsApp replies without knowing about the DM, and the sales rep who handles email sends a proposal that no longer fits. Nobody did anything wrong on their own. The problem is that each channel lives in its own app, and nobody sees the whole picture.

Bringing every channel into one unified inbox fixes most of this, but only if it comes with rules: who picks up each conversation, what status it's in, how long it can wait, and what happens when it moves from a bot to a person. This guide walks through setting up that inbox step by step and measuring whether it works.

It's part of our complete guide to selling on WhatsApp, but it applies to any team that talks to customers on more than one channel.

Multichannel and omnichannel aren't the same thing

The two terms get used interchangeably. It's worth separating them:

• Multichannel means being available on several channels: WhatsApp, Instagram, Facebook Messenger, email, SMS, phone. Each channel can have its own team, its own tool and its own records.
• Omnichannel means those channels share the same contact record. A customer starts on Instagram, continues on WhatsApp and wraps up over email, and whoever helps them sees the full conversation, in order, without asking them to repeat anything.

In practice, almost every small business is already multichannel without ever deciding to be. Customers pick the channel, not you. What's missing is the second step. A unified inbox is the tool that gets you from multichannel to omnichannel, because it forces every message to land in one place and attach to the same contact.

What goes wrong when every channel has its own app

If your team currently answers WhatsApp on a phone, Instagram in another app and email in Outlook or Gmail, these will sound familiar:

• Missed messages. A notification pops up on a phone sitting in a drawer, someone opens it to take a quick look, it's no longer "unread," and nobody replies.
• Duplicate or conflicting replies. Two people answer the same customer, or one quotes one price and the other quotes another.
• Broken history. To figure out what was agreed, you have to open three apps and scroll through each.
• Dependence on one person. WhatsApp lives on the sales rep's phone. When they go on vacation or leave the company, the conversations leave with them.
• No measurement. You can't tell how long customers wait or how many conversations went unanswered, because the data is scattered.
• No access control. Whoever has the phone sees everything. There's no simple way to give partial access or log who replied to what, which also makes privacy compliance harder.

How to set up a unified inbox

1. Connect the channels your customers already use

Start with the real list, not the ideal one. Look at where your recent customer conversations came from and connect those channels first. For most small businesses that means WhatsApp, Instagram, Facebook Messenger and email, sometimes SMS.

WhatsApp comes with a decision: QR code connection or the official API. The first is quick and needs no approval, but it depends on the linked phone staying connected. The second is more stable and lets several agents use the same number. We cover the differences in detail in WhatsApp Business App vs API.

2. Make sure everything lands on the contact record

Every message needs to be tied to a contact, and that contact has to be the same no matter the channel. Before you connect everything, decide how duplicates get merged. If a customer writes on Instagram and later on WhatsApp, someone needs to merge the two records once it's clear they're the same person (for example, when they share a phone number or email). Without this, the inbox is unified but the history is still split.

3. Set up assignment: every conversation has an owner

The most important rule of all: no open conversation goes without an owner. There are three common ways to route:

Write it down in a short doc the whole team knows.

4. Keep conversation statuses few and well defined

Statuses show where each conversation stands. Too many cause confusion; a few clear ones are enough:

• New: it came in and nobody has picked it up.
• Open: it has an owner and is waiting on the team.
• Waiting on customer: the team replied and the ball is in the customer's court.
• Closed: the issue is resolved. If the customer writes again, it reopens.

The golden rule: "closed" means resolved, not "I replied once." Also agree on what happens to conversations that sit in "waiting on customer" for a long time, such as an automated follow-up and, with no reply, closing it out.

5. Prepare canned responses

Some questions come in every day: hours, pricing, location, turnaround times, payment options. Write a template reply for each, with room to personalize the name and the specifics.

Keep the list short and review it monthly, deleting anything nobody uses. If you need a starting point, our WhatsApp sales message templates work for Instagram and email too.

6. Use internal notes instead of side chats

When someone needs help with a conversation, the instinct is to ask in a team chat. The result is that the information ends up outside the customer record. Internal notes fix that: they stay in the conversation, only the team can see them, and you can mention a teammate to pull them in.

One caveat: put only what's needed to serve the customer well in notes. Sensitive data or personal opinions about the customer don't belong there, and privacy laws like GDPR or state privacy rules are one more reason to keep notes clean.

7. Make the history useful on the contact record

The contact record should show, on one screen, conversations from every channel, notes, the pipeline stage, appointments and tags. That's what lets anyone on the team pick up a conversation midway without asking "have we talked before?"

Internal SLAs and business hours

An internal SLA is a promise the team makes to itself: "we reply to new conversations within X during business hours." It doesn't need to be a contract, but it does need to be written down and known.

A few guidelines:

• Differentiate by channel and type. People tend to expect faster replies on messaging apps than on email. A hot quote request deserves more urgency than a question about an old invoice.
• Tie the SLA to your hours. An SLA that counts the middle of the night will always fail. Define your support hours and measure within them, or track after-hours conversations separately.
• Tell customers what to expect. After hours, an automated reply explaining when the team is back beats silence. If you have an AI agent, it can handle the simple stuff and leave the rest for the morning.
• Measure first, then promise. Before you set a target, watch how long the team takes today for a few weeks. For example, if your current median first response is two hours, promising ten minutes next week isn't realistic.

There's a technical detail on WhatsApp worth keeping in mind: with the official API, once 24 hours have passed since the customer's last message, you can only start a conversation using approved message templates. One more reason to reply on time.

Handing off from AI to a human

More and more businesses put an AI agent on the front line to reply instantly, ask qualifying questions and book meetings. It works well when the handoff to a person is well designed. When it isn't, the customer gets stuck in a loop that goes nowhere.

Define these before switching the agent on:

1. When it hands off. The customer asks for a person; there's a complaint; the question falls outside the knowledge base; the customer is ready to buy and needs specific terms.
2. Who it hands off to. The same routing rule as the inbox: the customer's rep, the general queue or the specialist.
3. What the person receives. The full conversation plus a summary of what the customer wants and the details already collected. Nobody should have to start with "how can I help?"
4. What the customer hears. An honest line: "I'm passing you to a teammate who'll reply shortly." And, after hours, when that will happen.
5. When the AI goes quiet. After the handoff, the agent doesn't reply in that conversation again until the person closes it or hands it back.

We go deeper in how to implement an AI agent in customer service.

Metrics: what to track and how to define it

Two metrics are enough to start. What matters is writing down the definition, because every tool and every person counts differently.

First response time

The time between the customer's first message in a conversation and the first reply sent by a person on your team. Decide and write down:

• whether automated replies (welcome message, after-hours notice) count. We recommend tracking them separately, since an automated reply doesn't solve anything;
• whether the clock runs only during business hours;
• whether you use the average or the median. The median is less skewed by a handful of conversations forgotten over a weekend.

Resolution time

The time between a conversation opening and the moment it's marked "closed" because the issue was resolved. The definition of "closed" is everything here: if the team closes conversations just to clear the inbox, the number improves and the service doesn't.

Implementation checklist

1. List the channels your recent customer conversations came from.
2. Pick a tool and confirm it connects all of those channels to the same contact record.
3. Decide between WhatsApp by QR code and the official API.
4. Add your users and set permissions for each person.
5. Write the assignment rule (queue, round robin or specialty).
6. Define the four statuses and what "closed" means.
7. Write canned responses for the most common questions.
8. Set your support hours and after-hours message.
9. Measure your current baseline for a few weeks before setting internal SLAs.
10. If you use AI, write the handoff rules before turning it on.

Where Elooo System fits

In Elooo System, the multichannel inbox brings together WhatsApp, Instagram, Facebook Messenger, email and SMS, with several people working the same channels and the history tied to the contact and the pipeline. AI agents, available from the Premium plan, reply and hand the conversation to a person when it makes sense. If you're comparing tools with a WhatsApp focus, see our page on the best CRM with WhatsApp.

Tags: #omnichannel support #unified inbox #whatsapp #instagram #customer service

Share