Getting email and WhatsApp into one inbox view

The request usually arrives in one sentence. We need WhatsApp messages handled in the same inbox view as email, without asking anyone to check two apps. It sounds like a straightforward requirement and it is not, because there are two very different products sold under that description and the demo looks identical for both.

The first kind puts the channels side by side. Two lists in one window, each with its own conversations, its own assignment, its own history. The second kind puts the client at the centre, so a person who emailed on Tuesday and messaged on Thursday is one relationship with one record and one thread of context. You find out which one you bought about six weeks in, when someone asks what a client was told and the answer is in the channel nobody thought to search.

What does unifying customer conversations actually mean?

Four levels, and vendors use the same words for all of them. Working out which level you are being shown is most of the evaluation.

• **One login.** Both channels are in one product, but they are separate sections. This is the most common thing sold as unified, and it saves you a browser tab and nothing else.
• **One queue.** Conversations from every channel arrive in a single list you can assign, tag and filter together. Genuinely useful. Your team stops missing WhatsApp because it was in a different section.
• **One contact.** The same person is recognised across channels, so their email history and their messages appear on one timeline. This is where the tool starts doing work a human was doing.
• **One record.** On top of the timeline, the tool keeps what was promised, what is outstanding and how the relationship is trending, regardless of which channel any of it happened on. Very few products reach this level.

Most teams asking for one inbox think they are asking for the third or fourth, and most demos are showing the first or second. It is not deception exactly. It is that the first two are what the category has meant for a decade.

Why is WhatsApp the hard channel?

Email and web chat are easy to add to an inbox. WhatsApp is not, for reasons that are structural rather than technical, and they are worth understanding before you evaluate anything.

• **A business number is not a mailbox.** WhatsApp Business numbers connect through the WhatsApp Business Platform via a provider, and the free WhatsApp Business app on a phone cannot be shared by a team at all. Any real multi-user setup means moving the number onto the platform first.
• **There is a 24-hour window.** Outside 24 hours since the customer's last message, you cannot send free-form text. You send a pre-approved template, and templates cost money per message. This shapes how follow-up works in ways email never does.
• **Identity is a phone number.** Matching a WhatsApp number to the person whose email you already have is not automatic. If the tool cannot do it, you get two records for one client, which is the exact problem you were trying to solve.
• **History does not arrive by default.** Connecting a number does not usually bring the conversations that happened before you connected it. Ask about import explicitly.

The mechanics of the platform, the window and template pricing are covered properly in our WhatsApp shared inbox guide. The short version for an evaluation is that a vendor who has genuinely solved WhatsApp will talk about the 24-hour window unprompted, and one who has not will call it just another channel.

Which vendors unify channels, and how far do they go?

Public capability as of September 2026. Tiers change what is included, so check against the plan you would actually buy.

Two things stand out from that table. Most of the market has added WhatsApp, so channel coverage alone no longer separates anyone. And almost everything unifies at the conversation or ticket level rather than at the relationship level, which is fine for support and thin for account work.

What does a client switching channels actually break?

This is the part worth testing during a trial, because it is where side-by-side setups fail in ways a demo will never show you.

• **The commitment gets orphaned.** You promise something over email on Monday. The client asks about it on WhatsApp on Friday. Whoever picks up the message has no reason to know a promise exists, and the client has to repeat themselves.
• **Ownership splits.** The account manager owns the email thread. Whoever is on the messaging rota picks up the WhatsApp. Two people, one client, no shared view of what the other said.
• **Reporting double counts.** Two conversations with the same person about the same thing become two entries in whatever you report on, which quietly makes your response numbers look better than reality.
• **Quiet goes unnoticed.** A client who stops emailing but keeps messaging looks like churn risk in one system and a healthy account in the other. Neither picture is true.

The last one is the expensive one and the slowest to show up. A relationship that has gone quiet across every channel at once is the signal worth having, and you can only compute it if the channels are one record. Split them and you have two half-signals that cancel each other out.

How to evaluate this in a two-week trial

Five tests, all of which you can run with one real client and about an hour of attention.

• Email a contact from the tool, then message the same person on WhatsApp. Do you see one record or two? This is the whole evaluation in one test.
• Make a commitment in the email, then ask the tool what you owe that client. If the answer only covers one channel, you have side-by-side.
• Have a colleague reply on the other channel. Does your view update, and can you tell what they said without switching sections?
• Wait 25 hours and try to send a WhatsApp message. If the tool does not surface the template requirement clearly at that moment, your team will hit it at the worst possible time.
• Connect a mailbox with real history and check whether past conversations arrive. Being briefed from day one is the difference between a tool you trust in week one and one you trust in month three.

If a vendor cannot get through those five in a trial, that is your answer, and it is a much cheaper answer than the one you get in month three. The related question of how to run a trial without disrupting the team is covered in switching without migrating.

When you do not need this at all

Worth saying plainly, because unification has a cost. If your clients only ever email you, adding a messaging channel because a tool supports it creates a new place to miss things. If your inbound is mostly one-off questions from people you will never hear from again, a support desk with a good ticket model will serve you better than a relationship record. And if your team is three people in one room, the coordination problem this solves is one you currently solve by talking.

The case for unifying is specific: you have named clients, they reach you on more than one channel, and the cost of a dropped promise is measured in retained revenue rather than in a support metric. If that is you, unify at the record level or do not bother, because unifying at the window level moves the problem rather than solving it.