Unified inbox: every customer conversation in one place

A lead fills in your website form, then texts you a photo of the job, then replies to your quote email with a question, then calls while you’re on a roof. That is four conversations in four places, and the person who picks up the next one usually sees only a slice of it.

This guide explains how a unified inbox fixes that: what it is, how to thread conversations per contact, the assign/snooze/close routine that keeps it clean, simple response targets, how to use templates and AI-suggested replies without sounding robotic, and the consent checks that need to travel with every message.

Why channel sprawl loses deals

Customers pick whatever channel is closest to hand. In a 2026 Pew Research Center survey of 5,511 US adults, 98% owned a cellphone and 91% owned a smartphone (Pew Research Center). That means most of your leads can text, email, call or use WhatsApp from the same device, and they will switch between them without thinking about it.

Your team, meanwhile, often handles each channel in a different tool: a Gmail tab, a texting app on the owner’s phone, WhatsApp on a tablet in the office, voicemail on the desk line. The result is predictable:

• Slow replies. Messages wait until someone happens to open the right app.
• Double replies. Two reps answer the same lead with different prices.
• Lost context. The rep calling back doesn’t know the customer already sent photos and a budget by text.
• No handoff. When a rep is out, their conversations are stuck in their personal phone.
• Compliance gaps. Someone texts a contact who replied STOP last week, because the opt-out lives in a different tool.

A unified inbox doesn’t make you faster by itself. It removes the reasons you’re slow.

What a unified inbox should include

At minimum, look for these pieces:

Capability	Why it matters
Email, SMS and WhatsApp in one view	You reply where the customer wrote without switching apps
Threading per contact	One timeline per person, not one per channel
Call history next to messages	Notes, recordings or summaries sit beside the texts they relate to
Assignment and ownership	Everyone knows whose conversation it is
Snooze and close	Conversations leave your view until they need you
Filters such as “mine” and “unassigned”	Each rep works their own queue; a lead can’t fall through the gap
Templates and saved replies	Common answers are consistent and fast
Consent and quiet-hours checks	Messages that shouldn’t go out don’t go out

If a tool only merges notifications into one feed but doesn’t tie each message to a contact record, it’s a notification center, not a unified inbox.

Thread conversations per contact

The core idea is simple: one person, one thread. When Maria texts from her mobile number, emails from her work address and messages on WhatsApp, all of it should land on Maria’s record.

That only works if your records are clean:

• Store every channel identifier on the contact. Mobile number, email and WhatsApp number (often the same as mobile) belong in the record, not just in the message.
• Fix duplicates quickly. If Maria exists twice, her conversation splits in two. See duplicate management for matching on email, phone and name.
• Link conversations to deals. A realtor juggling a buyer and a seller in the same family needs to know which deal a message is about. Keep the thread on the person and reference the deal in notes or tags.

For a contractor, this means the estimator sees the homeowner’s original form, the photos they texted and the “can you start in May?” email before calling. For an agency, it means the account manager sees the client’s WhatsApp voice-note summary next to the email thread about the retainer.

Assign, snooze and close

An inbox stays useful when every conversation is in one of three states: someone owns it and needs to act, it’s snoozed until a specific time, or it’s closed.

Assign

Every open conversation should have exactly one owner. Good default rules:

• If the contact already has an owner, new messages go to that person.
• If not, route new inbound conversations with the same rules you use for leads, such as round-robin. The lead routing guide covers the options.
• Someone (usually a manager) checks the unassigned filter several times a day. An unassigned conversation is nobody’s job.

Snooze

Snooze is for “not now, but definitely later.” The customer says “I’ll talk to my wife and get back to you Thursday.” Snooze the conversation until Thursday at 10 a.m. It disappears from your queue and comes back when it’s time to follow up. Snooze replaces sticky notes and mental reminders.

Close

Close a conversation when nothing is waiting on you: the question is answered, the appointment is booked, the lead said no. Closing isn’t deleting. The history stays on the contact, and a new message from them reopens the conversation.

A daily routine that works: start the day with your “mine” view, reply to everything you can, snooze what needs a later answer, close what’s done, then check “unassigned.” Aim to end the day with an empty “mine” view, apart from snoozed items.

Set response targets per channel

A service-level target is just a written promise to yourselves: “We reply to new leads within X during business hours.” Pick numbers you can actually hit, then measure misses.

Channel	Suggested target (business hours)	Notes
New lead SMS	Within 5–15 minutes	Texts feel conversational; long gaps feel like silence
WhatsApp	Within 15–30 minutes	Free-form replies are only allowed inside the 24-hour customer service window
Email from a lead	Within 1 hour	Faster for hot leads and replies to quotes
Missed call	Call or text back within 15 minutes	Leave context in the thread for whoever calls back

These are starting points, not industry rules. A roofing company in storm season and an agency with retainer clients will set different numbers.

WhatsApp deserves a specific note. Meta’s documentation says that when a WhatsApp user messages or calls you, a 24-hour customer service window opens, and that once it closes, “you can only send pre-approved template messages” (Meta for Developers). A WhatsApp lead you ignore for a day can’t receive a normal reply anymore. That alone is a good reason to give WhatsApp a tight target. The WhatsApp CRM guide covers the window and templates in more detail.

Use templates without sounding templated

Templates save time on the questions you answer ten times a week: service area, availability, what to expect at a first appointment, how to accept a quote. Keep them good:

• Write them like you talk. Short sentences, no corporate phrases.
• Use merge tags for the obvious (first name, appointment time, rep name) and leave a gap for one personal line.
• Keep SMS templates short. One idea per text and a clear next step.
• Separate saved replies from outbound templates. A saved reply (“Here’s how our estimates work…”) is for conversations already underway; outbound templates start new ones and need more care with consent.
• Review quarterly. Delete templates nobody uses and fix the ones customers keep misunderstanding.

The sales email templates guide has eight ready-to-use examples.

AI-suggested replies: helpful, with a human check

AI can draft a reply from the conversation history in seconds: answering a question about hours, confirming an appointment, summarizing next steps after a call. Used well, it cuts the time between reading and replying.

Ground rules that keep it safe:

• A person reads every suggestion before it sends. Edit for tone and facts.
• Never let AI invent prices, dates or promises. If the answer depends on something not in the record, write it yourself.
• Watch for confident mistakes. A draft that sounds right but references the wrong job is worse than a slower reply.

Consent and opt-outs must follow the contact

When every channel lives on the same record, you can see at a glance which channels a contact has agreed to and which they’ve turned off. That matters, because people don’t always opt out in the channel you expect.

The CTIA Messaging Principles and Best Practices (May 2023) say message senders should “support multiple mechanisms of opt-out, including phone call, email, or text” (CTIA). The FCC’s 2024 order on revoking consent says consumers may revoke consent to robocalls and robotexts “in any reasonable manner,” and that callers must honor do-not-call and revocation requests “within a reasonable time not to exceed 10 business days of receipt” (FCC).

In practice: if a customer emails “please stop texting me,” the person reading that email needs to be able to switch off SMS for that contact right there. This is general information, not legal advice; the SMS consent management guide goes deeper.

How Exa helps

Exa’s unified inbox threads two-way email, SMS and WhatsApp conversations per contact, with call history (including AI transcripts, recordings and summaries) on the same timeline. You can assign, snooze and close conversations, filter by “mine” or “unassigned,” use templates with merge tags and saved replies, and start from an AI-suggested reply that you edit before sending. New leads can be spread across the team with round-robin assignment.

Consent, opt-outs and quiet hours are enforced on every send. Consent is stored per channel, STOP, START and HELP replies update it automatically, and opted-out numbers are blocked server-side, so a rushed rep can’t text someone who said no. WhatsApp’s 24-hour window and template rules are handled for you. See security and compliance for the details.

Final thoughts

A unified inbox is less about software and more about habits: one thread per person, one owner per conversation, snooze instead of remembering, close when you’re done, and consent that travels with the contact. Get those right and response times usually improve on their own, because nothing is hiding in an app nobody opened.

Start small. Connect the channels your leads actually use, write five good templates, set one response target per channel, and check the unassigned queue every morning and afternoon for a month. Then look at what slipped through and tighten from there.