WhatsApp Shared Inbox for Teams: Complete Guide
Your business runs on one WhatsApp number. Three people answer it — but only one phone holds the chats. So a customer messages on Tuesday, a different teammate picks it up Thursday with no idea what was already said, two agents reply to the same person an hour apart, and the lead who asked for a quote on Monday is still waiting because everyone assumed someone else had it.
That's the gap a WhatsApp shared inbox closes. It puts one number in front of a whole team, with each conversation owned by a person, visible to everyone, and carried in the business instead of on someone's personal phone.
This guide is the hub for that topic: why teams hit a wall with the standard WhatsApp Business app, the features a shared inbox actually needs, how groups and the API fit in, and a practical plan to roll one out without disrupting the number your customers already message.
What a WhatsApp shared inbox is (and isn't)
A WhatsApp shared inbox is a workspace where multiple teammates send and reply from one WhatsApp number at the same time, each working their own assigned conversations, with full shared visibility into the rest. Think of it as a team email inbox — but for WhatsApp, with assignment, internal notes and roles built in.
It is not the same as a few people logging into one phone, and it isn't WhatsApp's own "linked devices" feature. Linked devices mirror the same chat list onto four screens — handy for one person across a laptop and phone, useless for a team, because there's no ownership, no note, no audit of who replied. A real shared inbox adds the team layer on top of the number:
- One number, many agents — everyone works concurrently without passing a handset around.
- Ownership per chat — each conversation is assigned to a person, so nothing is "everyone's job and no one's".
- Shared context — anyone can see the full history, internal notes and status of a chat before they reply.
- Accountability — you can see who said what, when, and what's still open.
If you're still deciding between the plain app and something built for a team, our companion piece is the WhatsApp Business app enough for teams? walks through where the free app gives out.
Why teams outgrow the WhatsApp Business app
The free WhatsApp Business app is genuinely good — for one person, one phone. It breaks the moment a second human needs to help. Here's where, in roughly the order it starts to hurt.
Only one device really "owns" the number
You can link a handful of devices, but they all show the identical inbox. There's no way to split the workload, no way to say "Priya owns the new leads, Arjun owns support". Everyone sees everything and so everyone touches nothing — or two people touch the same thing. For the mechanics and the workarounds, see WhatsApp for multiple users on one number and the related question of running two phones on one WhatsApp number.
No assignment, so leads fall through
Without a way to assign a chat, coverage depends on memory and goodwill. The classic failure: a buyer messages overnight, three agents glance at it in the morning, each assumes another is on it, and it sits unanswered until lunch. Assignment turns "someone should reply" into "this is yours".
No internal notes, so context lives in people's heads
When a teammate takes over a conversation, they need the backstory — what was promised, what the customer's budget is, why they went quiet. On the plain app there's nowhere to record that without the customer seeing it. So context walks out the door at the end of every shift.
The number lives on a personal phone
This is the quiet killer. If the business number is really one agent's handset, then your customer relationships, history and half-finished deals leave with that agent. There's no clean way to off-board them, and no way to keep the conversation going seamlessly when they're on leave.
No reporting, no SLAs, no roles
You can't see response times, who's overloaded, or which chats have been waiting too long. And everyone has the same god-mode access — there's no way to give a junior agent reply access without also handing them the ability to export your whole contact list.
A shared inbox is the answer to all five at once. The rest of this guide is about what a good one looks like.
The must-have features of a WhatsApp shared inbox
Not every "team inbox" is equal. These are the capabilities that separate a real shared inbox from a glorified group login. Treat this as your evaluation checklist.
1. Chat assignment and ownership
Every conversation should be assignable to a specific teammate — manually, or automatically by rules (round-robin, by tag, by who's online). The owner is responsible; everyone else can see it's handled. This is the single feature that stops leads slipping. We go deep on the mechanics in assigning WhatsApp chats to agents, including auto-assignment and load-balancing.
2. Internal notes and @mentions
The team layer that the customer never sees. Drop a note on a chat — "this one's price-sensitive, already quoted ₹X" — and @mention a colleague to pull them in. Handoffs stop losing context, and a new teammate can get up to speed on a thread in seconds. See internal notes & @mentions on WhatsApp.
3. Canned replies
Your team answers the same fifteen questions all day — pricing, hours, location, returns. Canned replies (saved snippets you insert with a shortcut) keep answers fast and consistent across every agent, so the new hire sounds like the veteran. Setup and a starter library are in canned replies for WhatsApp.
4. Roles and permissions
Not everyone should be able to do everything. A shared inbox needs roles — who can reply, who can see all chats versus only their own, who can broadcast, who can export. This is what makes the inbox safe to scale past three people. More in roles & permissions for a WhatsApp inbox.
5. A contact record under every chat
A message thread isn't enough. Each conversation should hang off a real contact — name, custom fields, tags, history — so you're talking to a person you know, not a phone number you don't. This is the bridge from "inbox" to "CRM", which we'll come back to.
6. Group support
Most teams don't only do one-to-one DMs — a huge share of real business happens in WhatsApp groups (broker groups, customer cohorts, distributor channels). A shared inbox that can't show you groups is showing you half your conversations. This is also where most tools quietly fail, for a structural reason we'll get to next.
7. Notes on the number itself: stays in the business
The whole point is that the conversation history, contacts and notes live in the workspace, not on a handset — so an agent leaving is an off-boarding task, not a data loss.
| Capability | Free WhatsApp app | Linked devices | Real shared inbox |
|---|---|---|---|
| Multiple agents on one number | Sort of (shared view) | Same view, 4 screens | Yes, with ownership |
| Assign a chat to a person | No | No | Yes |
| Internal notes / @mentions | No | No | Yes |
| Roles & permissions | No | No | Yes |
| Contact record + CRM | No | No | Yes |
| Works inside groups | Yes (manually) | Yes (manually) | Yes (as a team) |
| History stays if agent leaves | No | No | Yes |
Groups and the API: the thing most tools get wrong
Here's the trap. When teams outgrow the free app, the obvious next step looks like the WhatsApp Business API — the engine behind tools like WATI, AiSensy, Interakt and DoubleTick. For templated notifications and chatbot flows, the API is a reasonable choice. But for a shared inbox, it has one limitation that catches teams off guard:
The official WhatsApp Business API cannot access groups. This isn't a missing feature in one product — it's structural. The API simply has no concept of group conversations, so no API-based tool can show you, let alone let your team work, your WhatsApp groups. If a meaningful chunk of your business lives in groups, an API shared inbox is blind to it. We cover this in depth in can the WhatsApp Business API access groups?.
The API route also brings two costs that surprise teams: message templates need Meta's approval before you can send them, and you typically pay per conversation or per message on top of the tool's subscription. For a high-volume support or sales team, that meter adds up fast.
The alternative is a shared inbox built on your existing number — the same number, linked by scanning a QR code, no new SIM and no porting. Because it's your real number rather than an API line, it can see and work your DMs and your groups, with no template approvals and no per-message fee. That's the model we'll describe in the Tenashi section. If you want to compare the two paths head-on first, read WhatsApp Business vs WhatsApp Business API.
From inbox to workspace: why a CRM belongs underneath
A shared inbox solves coverage — everyone can work one number without colliding. But coverage alone still leaves your customer data trapped in chat threads. The next layer up is where the real leverage is: a CRM under the inbox.
When every conversation is tied to a contact record, the inbox stops being a list of messages and becomes a system that remembers. You get:
- Custom fields — budget, source, plan, renewal date — on every contact, so any agent picks up with full context.
- Deals and a pipeline — drag a lead from New to Qualified to Won on a board, without leaving the chat it came from.
- Follow-up reminders — "ping them in two weeks" that actually fires, instead of relying on memory.
This is the difference between a shared inbox and a true WhatsApp workspace. The inbox handles today's conversations; the CRM makes sure none of them are forgotten next month. Our WhatsApp CRM guide goes deep on running sales this way, and WhatsApp team collaboration: a playbook covers the day-to-day rituals that make a shared number actually work for a team.
Support teams have a parallel need: tickets, SLAs and a knowledge base sitting on top of the same inbox, so a "where's my order?" message becomes a tracked ticket with a response deadline rather than a chat someone hopefully remembers. That's the WhatsApp customer support side of the same workspace.
How to roll out a WhatsApp shared inbox
A migration sounds heavy. In practice, moving a team to a shared inbox on your existing number is a same-day job if you sequence it well. Here's a clean rollout.
Step 1 — Pick the number you'll share
Use the number your customers already message. The whole value is continuity — they keep texting the same place, you get the team layer behind it. If your business runs on more than one line, a good workspace can hold multiple numbers in one inbox, so you don't have to consolidate first.
Step 2 — Link it (no porting, no new SIM)
With a workspace built on your existing number, connecting is a QR scan — the same flow as linking WhatsApp Web. No new SIM card, no number porting, no waiting on Meta approval. The number stays exactly where it is; you're just giving your team a shared way into it.
Step 3 — Invite the team and set roles
Add your agents and assign roles before anyone touches a chat. Decide who replies, who sees all conversations versus only their own, who can broadcast, who can export contacts. Getting roles & permissions right on day one saves a cleanup later.
Step 4 — Set up assignment rules and canned replies
Decide how chats get owned: round-robin to the team, by tag, or by who's online. Then load your ten most common answers as canned replies so the team is fast and consistent from the first message. These two settings do most of the heavy lifting.
Step 5 — Bring your contacts and groups in
Import your existing contact list (CSV is fine) so chats attach to real records, and pull your business groups into the inbox so the team can finally work them together — not just DMs. This is where teams coming from an API tool feel the difference most.
Step 6 — Agree the team rituals
Tools don't fix behaviour on their own. Agree a few norms: assign on receipt, note before you hand off, clear your queue before end of day, @mention rather than DM a colleague about a customer. The team collaboration playbook has a starter set you can adopt as written.
Step 7 — Watch the safety side
If your team also sends proactive messages or broadcasts, do it carefully. Sudden bursts from a number that normally chats one-to-one are exactly what trips WhatsApp's spam detection. Use a tool that paces sends and warms up gradually — more on that below.
Where Tenashi fits
Tenashi is the WhatsApp workspace for teams — a shared inbox plus a real CRM, support desk, automations and safe broadcasts, all on your existing WhatsApp number. You link it with a QR scan: no new SIM, no porting, no Meta template queue. Within minutes your whole team is working one number together.
The shared inbox does the things this guide describes, as first-class features: assign any chat to a teammate (manually or by rule), leave internal notes and @mention colleagues, fire canned replies, and control who can do what with roles and permissions. Every conversation hangs off a real contact with custom fields, deals and a drag-drop pipeline, plus follow-up reminders — so the inbox doesn't just cover today, it remembers next month. And because Tenashi runs on your real number rather than the API, it works inside your groups too — the part the official WhatsApp Business API structurally can't reach.
There are no template approvals and no per-message fees; you pay a flat price. For teams that also push proactive messages, sends are ban-protected — human-paced with jitter, typing presence, gradual warm-up, and duplicate/burst guards, with a safety log — which meaningfully reduces risk to your number (risk reduction, not a guarantee; WhatsApp's policies can change). On the Growth and Scale plans, AI can suggest replies, summarize a noisy group thread, read text from images (OCR) and translate messages inline — handy when one inbox serves customers in several languages.
Pricing is Starter $18/mo, Growth $27/mo, Scale $56/mo, with a 3-day Growth trial, no card.
Start your free trial → · See every feature
Related guides
- Cluster hub: you're reading it — the WhatsApp shared inbox pillar.
- How to share one WhatsApp number with a team
- WhatsApp for multiple users on one number
- Assigning WhatsApp chats to agents
- Internal notes & @mentions on WhatsApp
- Canned replies for WhatsApp
- Multi-number WhatsApp inbox: how it works
- WhatsApp team collaboration: a playbook
- Roles & permissions for a WhatsApp inbox
- Adjacent pillars: Best WhatsApp CRM in 2026 · Using WhatsApp groups for business · WhatsApp customer support: tickets, SLAs & KB
FAQ
What is a WhatsApp shared inbox?
A WhatsApp shared inbox lets several teammates send and reply from one WhatsApp number at the same time, each owning their assigned chats while everyone shares full visibility. It adds assignment, internal notes, roles and a contact record on top of the number — the team layer the plain WhatsApp app doesn't have.
How is a shared inbox different from WhatsApp linked devices?
Linked devices mirror the same chat list onto up to four screens for one person — there's no ownership, no notes and no audit of who replied. A shared inbox adds a team layer: each chat is assigned to a person, anyone can see context before replying, and history stays in the business rather than on a personal phone.
Can multiple agents use one WhatsApp number?
Yes — with a shared inbox, multiple agents work the same number concurrently, each handling their own assigned conversations without colliding. The free WhatsApp app can't split work this way; everyone sees the identical inbox with no assignment, which is exactly why teams move to a shared inbox built for one number.
Does a WhatsApp shared inbox work with groups?
It depends on how it's built. Tools on the official WhatsApp Business API can't access groups at all — that's a structural limit. A shared inbox built on your existing number, like Tenashi, can show and work your groups as a team alongside your DMs: read, reply, assign and note on group chats from one place.
Do I need a new number to set up a shared inbox?
No. With a workspace built on your existing number, you connect by scanning a QR code — no new SIM, no porting and no Meta approval. Customers keep messaging the same number they always have; your team just gets a shared, assignable way to work it.
Will using a shared inbox tool get my WhatsApp number banned?
A shared inbox for replying to inbound chats is low-risk. The risk comes from proactive blasts. Choose a tool with built-in ban-protection — Tenashi paces sends like a human, adds jitter and typing presence, warms up gradually and guards against duplicate or burst patterns, which reduces the risk, though no tool can guarantee against WhatsApp's policies.
Stop passing one phone around. Start a free trial and put your whole team on one WhatsApp number — with assignment, notes and a CRM under every chat — built for how teams actually work.