Unified Inbox for WhatsApp, SMS, and Email: One Screen for All Chats
Stop tab-switching between three apps to answer one customer.
A unified inbox is exactly what it sounds like: one screen where every WhatsApp message, SMS, and email from your customers shows up, sorted by conversation, assigned to a person, and tied to the same customer record no matter which channel they used. No tab-switching between WhatsApp Web, a texting app, and Gmail to answer one person.
The reason this matters more than it sounds: customers don't stay on one channel. Someone messages you on WhatsApp on Monday, doesn't hear back fast enough, and emails on Wednesday. Without a unified inbox, that looks like two unrelated interactions handled by two different people who have no idea the other conversation exists.
Why one inbox matters
Picture Thistle & Vine, an online boutique. A customer named Elena messages on WhatsApp asking about a delayed order, gets no reply for a day, and emails support directly. In a three-app setup, the WhatsApp agent and the email agent each answer from a blank slate — one might promise a refund the other already denied.
In a unified inbox, both messages sit under Elena's one contact record. Whoever opens either conversation sees the full history: the WhatsApp message, the email, and any past order notes — instantly, without asking her to repeat herself.
The cost of a fragmented inbox isn't visible until a customer gets two different answers to the same question from two different agents. That's the moment trust breaks.
There's a second cost that's less dramatic but adds up faster: time. An agent who has to check WhatsApp Web, then a separate SMS app, then Gmail, then piece together which conversation happened first, is spending minutes per ticket just navigating tools before they've answered anything. Multiply that across a team handling dozens of conversations a day, and the "just switch tabs" tax becomes a real drag on response time — one that shows up nowhere on a spreadsheet until you measure it directly.
Channels WaSMS unifies
Three channels feed the same inbox:
- WhatsApp — using your own business number through your own gateway
- SMS — sent and received through your Android phone acting as the gateway
- Email — inbound and outbound through your connected inbox (see Inbound Email Management)
Each conversation is tagged with its channel so agents know exactly where a reply will land, but they're listed together, sorted by recency or by assignment — whichever view your team prefers.
Replying from the unified inbox sends through the correct channel automatically — an agent typing a reply to Elena's WhatsApp conversation doesn't need to open WhatsApp separately; the message goes out over WhatsApp because that's the channel the conversation is tagged with. The same applies to SMS and email. One composer, three delivery paths, no manual switching.
Search across everything at once
Because every channel sits in the same data layer, searching for a customer's name, phone number, or a keyword like "refund" returns matches across WhatsApp, SMS, and email together — not three separate searches in three separate tools. For a team fielding a repeat question, that means finding "did we already tell this person our return policy" takes one search instead of three.
Assigning and collaborating
Every conversation has an owner. When a new message comes in on any channel, it either auto-assigns based on your routing rules or lands in an unassigned queue for the next available agent to claim.
Once claimed:
- Internal notes let a teammate leave context on a thread without the customer seeing it — useful when Dr. Chen's clinic front desk needs to flag "patient asked about billing, forward to accounts" without that note going out over WhatsApp.
- Reassignment is one click, with the full history following the ticket.
- Status (open, pending, resolved) is visible to the whole team, so nobody re-answers something that's already closed.
For a small team, this collaboration layer matters just as much as the unification itself. It's common for a two- or three-person support team to informally split channels — "I handle WhatsApp, you handle email" — precisely because there's no shared view otherwise. A unified inbox with clear ownership removes the need for that informal, brittle division of labor, and makes it trivial to cover for a teammate who's out for the day without them having to hand over separate login credentials for three different apps.
AI in the inbox
Every conversation in the unified inbox — regardless of channel — can have an AI-drafted reply waiting, built from your business's own past conversations and FAQ content, not a generic script. An agent reviews and sends, or lets a defined set of low-risk replies go out automatically. See AI for Customer Service for how the draft-and-review flow works channel by channel.
Because AI sees the combined history across WhatsApp, SMS, and email for a given customer, its drafts are informed by everything that customer has ever asked — not just the current channel's thread.
Reporting across channels
Reports roll up by channel and by combined total, so you can see:
- Average first-response time per channel
- Ticket volume trends across WhatsApp vs. SMS vs. email
- Which agents are handling the heaviest load, across all three
That combined view is what makes it possible to answer questions like "should we push customers toward WhatsApp instead of email?" with real numbers instead of a guess. Pair this with the Free CRM for Conversations guide to see how contact-level history builds automatically from this same unified data.
For Dr. Chen's clinic, that reporting view showed something the team hadn't noticed while working from three separate apps: WhatsApp messages were getting answered in minutes, while emails to the same practice were sitting for most of a day. That single number — visible only because the channels were reported together — was the reason the clinic moved appointment confirmations to WhatsApp-first, a change covered in more detail in the appointment reminder software guide.