What is a WhatsApp shared inbox?
A WhatsApp shared inbox is one WhatsApp business number that several agents answer from a shared view of the conversations. The customer still sees a single number; the team sees who replied, what was said, and what happens next.
It exists because WhatsApp is a one-to-one channel and a business is not one person. The free WhatsApp Business App effectively ties a number to a single phone, so a second agent either shares the device or works blind.
A shared inbox requires the WhatsApp Business Platform (the Cloud API). The number is connected to software rather than to a handset, and the conversation history lives against the business, not against whoever happened to be holding the phone.
- One number for customers, many agents behind it.
- One thread per customer, not one thread per device.
- Internal notes the customer never sees.
- Per-message state: what the customer has read, and what WhatsApp has delivered.
- Where the conversation came from: in BNex a message that arrived from a Meta ad is badged with the ad it came from, and the contact keeps its ten most recent ad clicks.
Why does a single WhatsApp phone stop working?
A WhatsApp Business App number effectively belongs to one device, so the business has one queue and one operator. As volume grows, customers wait, nobody can see who already replied, and the same question gets answered twice.
The failure is rarely dramatic. It shows up as replies that arrive hours late, a second agent asking a customer to repeat themselves, and no way to tell whether a message was ever answered at all.
Moving to the WhatsApp Business Platform turns the number into a shared resource. Many agents can work the same number, and the platform keeps one conversation thread per customer rather than one per device.
Can multiple agents use one WhatsApp number?
Yes. On the WhatsApp Business Platform, one number can serve any number of agents, each signed in as themselves. On the free WhatsApp Business App, a number is effectively tied to one device and one message history.
- Agents sign in individually; customers never see an agent’s personal number.
- Read state is per message, so two people cannot both answer the same reply by accident.
- Notes written for colleagues stay inside the inbox and are never delivered to the customer.
- Delivery state comes from WhatsApp itself — sent, delivered, read — so an agent can tell the difference between “ignored” and “not delivered”.
What a shared number does not do by itself is decide who answers what. That is a process decision, and most tools — including ours — will happily let you leave it undefined.
How do you set up a WhatsApp shared inbox?
Setting up a shared inbox is one afternoon of configuration and one meeting about rules. The configuration decides where messages land; the meeting decides whether customers get answered once, by one person, in time.
- 1
Choose how the number connects
Either you connect the number to the Cloud API directly, or you use a provider that runs the connection and gives you the inbox. Both are legitimate; the difference is who owns the plumbing and how the per-message Meta fees are paid.
- 2
Decide who owns an unassigned conversation
Either a round-robin rotation or a shared pool anyone can claim. Pick one and write it down. A shared pool with no rule is the most common reason two agents answer the same customer.
- 3
Decide when a conversation leaves an agent
Set explicit triggers: time since last reply, topic, or the customer asking for a person. Without a trigger, conversations stay with whoever happened to open them — including when that person is off shift.
- 4
Decide what counts as finished
Agree a state everyone uses, so the inbox does not fill with conversations nobody is sure are closed. If your tool does not persist an open/closed state, the convention has to live in your process.
- 5
Write the internal-note convention
Notes are where context lives that the customer must not see but the next agent must. That separation — not the shared screen — is the main operational gain over a phone.
- 6
Train on the 24-hour window as a deadline
Any conversation approaching the end of the window should be answered while a plain reply is still allowed, rather than after it has become a paid template.
What is the 24-hour rule, and why does it decide your inbox rules?
You can reply freely for 24 hours after the customer’s last message. After that, reaching them again requires an approved template, which is charged differently and reads differently to a customer.
- Every inbound customer message restarts the 24 hours.
- Inside the window, agents can send normal replies, media and documents.
- Outside the window, only pre-approved templates can be sent.
- Since 1 October 2026, replies classified as service messages are charged per message after the first 1,000 free service messages per number each month, so most small teams still pay nothing for replies — the free allowance is per number, not per agent.
This is why “reply before the window closes” belongs in the team’s process, not only in the software. The cost of missing it is a paid template that feels less like a conversation.
Which kind of shared inbox tool fits which team?
There are four practical routes to a shared WhatsApp inbox — the free Business App, the Cloud API plus your own build, a hosted provider, and a self-hosted inbox — and they differ mainly in who pays per seat, who owns the plumbing, and how much of the work you take on.
| Route | What you get | The catch |
|---|---|---|
| WhatsApp Business App (free) | One number, one device, no per-message fees | Not a shared inbox: no real multi-agent access, history lives on a handset |
| Cloud API plus your own build | Full control, your data, per-message Meta fees only | You build and maintain the inbox, read state, retries and reporting |
| Hosted provider (WATI, Respond.io, AiSensy and similar) | Ready-made inbox with campaigns and automation | Pricing is usually tied to seats or usage — verify the current published rates for your team size |
| Self-hosted inbox (for example Chatwoot) | No per-seat licence; runs on your own servers | You operate the infrastructure, and you still need a connection to the WhatsApp API |
| BNex | Shared inbox for WhatsApp and Instagram text DMs, campaigns and visual automation on the official Cloud API, with no per-seat fee | Conversation assignment and closed states are not persisted yet — see the limits below |
When is a shared inbox the wrong answer?
A shared inbox is the wrong purchase when one person already handles WhatsApp comfortably, when nobody can reply inside 24 hours, or when what you actually need is per-agent numbers or full automation rather than a shared human queue.
| Your situation | What actually fits |
|---|---|
| One person answers WhatsApp | The free WhatsApp Business App is enough; the Platform adds setup and per-message cost for no gain |
| Nobody can reply within 24 hours | Fix the staffing first — outside the window every reply becomes a paid template |
| Each agent needs their own WhatsApp number | A shared inbox deliberately shows one number to the customer; several numbers is a different design |
| You want customers handled entirely by a bot | Automation first, humans on exceptions. A shared inbox is the human layer |
| You need per-conversation ownership enforced by the software today | Check that the tool actually persists assignment as a field. With BNex that ownership is currently a team convention, not a system record |
What does BNex do today, and what does it not do yet?
BNex gives a team one shared view of a WhatsApp number, internal notes, roles, and per-message read and delivery state on the official WhatsApp Cloud API. Per-conversation assignment and an enforced open/closed lifecycle are not persisted features yet. A connected Instagram professional account can be added to the same workspace, bringing its text direct messages into the same inbox.
- One shared conversation view per workspace, with tenant isolation between businesses.
- Instagram text direct messages from a connected professional account appear in the same inbox, and support text replies and internal notes only.
- Internal notes that stay inside the inbox and are never charged as messages.
- Canned and template replies, with media and delivery state from WhatsApp.
- Two read concepts kept deliberately separate: whether the agent has read the message, and whether WhatsApp has delivered it.
- Team members and roles managed per workspace.
Not yet persisted: who owns a specific conversation, and formal open/closed states. We would rather say that on the page than let a feature list imply otherwise — if enforced assignment is a hard requirement for you today, ask us and we will tell you honestly whether BNex fits.
Common questions
Platform rules and pricing on this page are Meta’s and can change. Meta updates WhatsApp pricing only on the first day of a quarter and gives advance notice, but always confirm current rates against Meta’s own documentation before committing a budget. This page was reviewed on 10 November 2026.
Related reading
API vs Business App
The WhatsApp Business App is a free phone-based app for a single operator with no API, while the WhatsApp Business Platform (often called the WhatsApp Business API) is a paid, multi-agent, programmable service built for teams, automation and broadcast at scale.
Pricing explained
Since 1 July 2025 Meta charges per delivered message rather than per conversation, categorised as marketing, utility, authentication and — from 1 October 2026 — service. Every business phone number gets 1,000 free service messages a month, so most small businesses still pay nothing for replies, while high-volume automated support now carries a real per-message cost.
Choosing a provider
WhatsApp Business API providers differ far less in features than in commercial model and ownership: who holds the WhatsApp Business Account, how message markup is charged, and what leaving costs. Ask about those first, because they are the parts a demo never shows.
Why BNex
BNex is a WhatsApp Business Platform suite that combines a shared team inbox, broadcast campaigns and workflow automation in one product, built on Meta’s official Cloud API rather than an unofficial automation workaround.