Quick answer
HelloGrowthCRM's omnichannel inbox merges email, WhatsApp, SMS, Instagram DMs and web chat into one stream. Every conversation is linked to the lead or account it belongs to and assigned to an owner, so a rep works a single queue — with full context — instead of switching between a mailbox, a phone and the Instagram app.
Customers pick the channel. Your team pays for the switching.
A buyer emails on Monday, replies on WhatsApp on Tuesday, and asks a question in web chat on Wednesday. To them it is one conversation. To a team working five separate apps, it is three disconnected threads — and the cost shows up as missed replies and repeated questions.
✗ Channel-switching eats the day
Reps tab between a mailbox, a WhatsApp inbox, the SMS tool and the Instagram app. Something is always unchecked, and the slowest channel sets the response time.
✗ Context is split across tools
The email half of a conversation lives in one place and the WhatsApp half in another. Nobody sees the whole thread, so customers get asked what they already answered.
✗ Nobody owns the conversation
Without one assigned owner, two reps reply to the same customer — or everyone assumes someone else has it and no one does.
✗ You can't see where things are stuck
When each channel is its own silo, a thread can sit unanswered for hours with no single view that surfaces it.
The omnichannel inbox collapses those silos into one queue, with each conversation tied to the CRM record it belongs to.
What the omnichannel inbox does
One stream, full context, and an owner on every conversation.
One queue, every channel
Email, WhatsApp, SMS, Instagram and web chat merge into a single stream. A rep works one list instead of switching between an inbox, a phone and the Instagram app.
Per-channel sub-inboxes
Work everything together, or focus on one channel at a time. The same conversations are reachable both ways, so a WhatsApp specialist and a generalist can each work how they prefer.
Assignment and ownership
Conversations are assigned to an owner so two reps never reply to the same customer, and reassigned in a click when someone is out — with the full thread carried over.
Linked to the lead record
Every message, whatever channel it came on, is attached to its lead or account. The rep replying sees deal value, stage and history; nothing is a context-free message in a void.
One history across channels
A customer who starts in web chat, replies on WhatsApp and later emails is still one record with one timeline — not three threads nobody reconciles.
Response visibility across channels
Inbox analytics show where conversations are waiting across every channel at once, so a slow thread is caught before the customer has to chase.
How it works in 4 steps
Connect your channels
Link email, WhatsApp Business API, SMS, Instagram and web chat to the workspace. Each uses the same setup it would on its own — the omnichannel view simply gathers them.
Conversations merge into one stream
Every inbound message lands in the omnichannel inbox, attached to its lead or account. A per-channel sub-inbox is there too for reps who prefer to focus.
Assign, reply, and keep one history
A conversation is assigned to an owner who replies from the record. If the customer switches channel, the thread stays on the same lead — one history, not three.
Managers watch the whole queue
Inbox analytics show where conversations are waiting across all channels, so a slow thread is caught and reassigned before the customer has to follow up.
Omnichannel inbox vs the shared team inbox
They are related, not the same — and most teams end up using both.
Shared team inbox
A team works a single channel together — most often one shared WhatsApp number — with assignment and SLA tracking. Start here if WhatsApp is where almost all your conversations happen.
See the team inbox →Omnichannel inbox
The layer above: every channel — email, WhatsApp, SMS, Instagram, web chat — merged into one queue so reps stop switching apps. Use this when conversations arrive across several channels.
You are hereFrequently asked questions
What is an omnichannel inbox?
An omnichannel inbox merges conversations from every channel — email, WhatsApp, SMS, Instagram DMs and web chat — into one stream a rep can work from a single screen. In HelloGrowthCRM every conversation, whatever channel it arrived on, is linked to the lead or account it belongs to, so the rep answering has the full picture rather than one channel's half of it.
Which channels does the omnichannel inbox cover?
Email, WhatsApp, SMS, Instagram DMs and comments, and website web chat all flow into the omnichannel view. Each channel also has its own sub-inbox, so a rep can work everything together or focus on one channel at a time. X (Twitter) DMs are available in beta where enabled.
How is this different from the shared team inbox?
The shared team inbox is where a team works conversations together on a single channel — most often a shared WhatsApp number. The omnichannel inbox is the layer above it: it merges every channel into one queue so a rep does not switch between a WhatsApp inbox, an email client and the Instagram app. If you mainly need WhatsApp for a team, start with the team inbox; if conversations arrive across several channels, the omnichannel view is what keeps them in one place.
Is every conversation linked to a CRM record?
Yes. Whether a message arrives by email, WhatsApp, SMS or Instagram, it is attached to the lead or account it belongs to. The rep replying sees the deal value, stage, tags and past interactions, and the conversation history survives even if the customer switches channel mid-thread.
Can conversations be assigned and owned?
Yes. Conversations can be assigned to a specific rep so two people do not reply to the same customer, and reassigned when someone is out. Because the inbox is shared, a covering rep picks up a thread with its full history rather than starting cold.
Does the omnichannel inbox track response times?
Response-time and first-response visibility is part of the inbox analytics that sit alongside the omnichannel view, so managers can see where conversations are waiting across channels rather than inside each one separately.
Which plan is the omnichannel inbox on?
The omnichannel inbox is available on Growth and higher, and it is enabled per workspace — ask us to switch it on for yours. The individual channels it merges, such as WhatsApp and email, are set up the same way they are for the rest of the CRM.
Can a customer move between channels in one conversation?
That is exactly what the linked record is for. A customer who starts in web chat, replies later on WhatsApp and then emails is still one lead with one history. The rep does not have to reconcile three separate threads to understand what has already been discussed.
The point of omnichannel is one record, not more channels
"Omnichannel" gets used to mean "we are on a lot of channels", but adding channels without joining them up makes the problem worse, not better. Every new channel is another app to check, another place a message can sit unanswered, and another half of a conversation that nobody can see next to the other half. The value is not in the number of channels — it is in the single record underneath them. When email, WhatsApp, SMS, Instagram and web chat all write to the same lead, the channel the customer chose stops mattering to your team, because the context travels with the person rather than with the app.
That is the difference between the omnichannel inbox and working a stack of separate tools. A rep opens one queue, sees the conversations assigned to them regardless of channel, and replies with the lead's deal value, stage and history in view. When a customer who emailed last week sends a WhatsApp today, it lands on the same record, so the rep answers as a continuation instead of asking them to re-explain. If that rep is out, a colleague picks the thread up with everything already in front of them. It builds on the shared team inbox — which is how a team works one channel together — and extends the idea to every channel at once.
Because each conversation is a lead, the inbox also feeds the rest of the CRM rather than sitting beside it. A web-chat enquiry can become a pipeline deal; a WhatsApp thread can trigger a follow-up sequence that pauses the instant a human reply arrives; and inbox analytics show managers where conversations are waiting across channels so the slow one is caught early. The omnichannel inbox is available on Growth and higher and is enabled per workspace — ask us to switch it on, and we will connect your channels with you.
The teams that get the most from it are the ones whose customers do not stay on one channel. A local service business takes enquiries by WhatsApp and web chat and sends quotes by email; an online seller fields Instagram DMs, support emails and SMS order updates; an agency juggles client threads across every channel at once. In each case the cost of fragmentation is the same — a conversation half-answered because the other half was in a different app, or a customer who went quiet because the reply landed in a tab nobody had open. Putting the channels into one queue does not change how customers reach out; it changes whether your team keeps up without heroics. And because every message is still a lead, the inbox is the front door to the same pipeline, so a first message on any channel can become a qualified opportunity, a task or a closed deal without being retyped anywhere. That is the test worth applying to any "omnichannel" claim: not how many logos sit on the channel list, but whether a conversation that crosses three of them is still one record your team can act on.
Related resources
The channels and inbox features that make up omnichannel.