WhatsApp Shared Inbox: One Number, Your Whole Team

What is a WhatsApp shared inbox?

A shared WhatsApp inbox is one WhatsApp number that several people answer, each from their own login, with every conversation assigned to whoever is handling it and visible only to the people who should see it.

That is the whole idea, and WhatsApp does not sell you one. The number belongs to a handset. Everything a team needs on top of it — logins, assignment, permissions, a record of who said what — is added by a platform sitting on Meta's WhatsApp Business Platform.

So the question underneath "how do I get a shared WhatsApp inbox" is really two. How far does the phone in your pocket already go, and what does the alternative cost once the team grows. Both have published answers, and this page uses nothing else: WhatsApp limits from WhatsApp's own Help Centre and Meta's developer documentation, and every competitor price read off that competitor's live pricing page on 22 August 2026, with the plan named.

• What is a WhatsApp shared inbox?
• How many people can use one WhatsApp Business account?
• What does the WhatsApp Business Platform give a team instead?
• Why does hiring the sixth person change your WhatsApp bill?
• Do all WhatsApp platforms charge per agent?
• Can a shared inbox stop the wrong agent reading a conversation?
• Can your team share the number that is already on your phone?
• Who does not need a shared WhatsApp inbox?

How many people can use one WhatsApp Business account?

Further than most articles admit, and then it stops for reasons that are documented rather than mysterious.

WhatsApp's Help Centre article on multi-agent publishes both numbers in one table: without multi-agent you can "connect up to four devices to your account", and with it "connect up to 10 devices to your account" (WhatsApp Help Centre, About multi-agent). The same article adds that the maximum is determined by the benefits included in your Meta Verified or Meta One subscription — so ten is what the feature offers today, not a floor you can plan a decade around.

There is a footnote on that worth reading twice. If you cancel the subscription, or its benefits change, only your four most recently active devices remain linked. Six people are answering, a payment lapses, and two of them are logged out by a rule rather than by a decision.

The paid tier is better than its reputation. On multi-agent you assign a chat by holding it and choosing an agent, and inside an open chat you can tap a message to see which agent sent it and what device was used. Customers see none of that: the article states plainly that they cannot see which agent or device a message came from, or who their chat was assigned to.

So "the app is for one person" is out of date. The honest version is that the app now does small-team messaging, and still does not do team management.

Every WhatsApp Business app row above comes from that one Help Centre article, read on 22 August 2026. Help Centre wording is revised without notice, so the linked page is authoritative and this table is not.

Two rows carry more weight than the rest. The broadcast list row means the one job you would want a laptop for is the one the laptop does not get. The 14-day row means the whole arrangement is a phone with helpers attached — if that phone is lost, replaced or left in a drawer, the helpers stop.

The deeper comparison, including what broadcast lists actually reach, is in the WhatsApp Business app versus the API.

What does the WhatsApp Business Platform give a team instead?

Four things the app has no version of, and they are the only four worth paying for.

A login per person. Not a device borrowed from one handset — an account, with a password, that can be created on Monday and switched off on Friday without anybody re-scanning a QR code.

Assignment and routing. A conversation belongs to a named agent. It can be assigned by hand or handed automatically to whoever is least busy among the people allowed to take it, so nothing sits unclaimed while three people each assume somebody else has it.

A record. Every message, with a sender, a timestamp and a delivery status, filterable and exportable. This is what makes response time measurable rather than a matter of opinion.

Walls. Which agents can see which number, and which of them can broadcast, export or change billing. This is the part most shared inboxes treat as a checkbox, and it is the section further down.

The trade is real and worth stating. The Platform has no screen of its own, Meta approves your business on its own schedule, and a new number starts on a low messaging tier rather than reaching your whole list on day one.

It also puts a clock on every conversation. Meta's developer documentation states that when a WhatsApp user messages you or calls you, "a 24-hour timer called a customer service window starts", and that when the window closes "you can only send pre-approved template messages" (Meta, Send messages). A good inbox shows that countdown on the thread instead of letting a reply fail silently. What the platform layer does in full is in the WhatsApp Business API explainer.

Why does hiring the sixth person change your WhatsApp bill?

Because on most platforms the bill has a seat in it, and a seat is the one input that grows exactly when your business is going well.

Here is the arithmetic on six published price lists, at three team sizes. "Agents" means people with a login. Each row takes that vendor's cheapest published route to that team size and names the billing commitment it depends on, because the commitments differ. The WabaCRM column assumes a workspace holding 10,000 contacts, which is what its price actually depends on.

Every figure was read off that vendor's own pricing page on 22 August 2026. All are before tax: DoubleTick states "Additional 18% GST chargeable" and Interakt prints "(+taxes)" beside every plan, while the others do not say so on the card.

Two caveats belong under that table. WabaCRM's ₹960 is a monthly rate with no commitment, compared here against competitors' discounted annual and yearly rates rather than their monthly ones. And these are not identical products — Gallabox meters AI credits, Wati meters automation triggers, AiSensy sells its chatbot builder and its AI agent as separate ₹2,500 and ₹3,500 monthly add-ons. The table compares what a seat costs, not what a platform is worth.

Message fees sit outside all of it, and each vendor quotes them differently. Wati's plan card says usage is "Charged based on WATI rate card"; AiSensy and Interakt each publish their own per-template rates. WabaCRM adds nothing to Meta's fees and could not: a Meta Tech Provider is not permitted to resell them, so Meta bills your own card against your own WhatsApp Business Account.

WabaCRM's row does not move because agents are not an input. The bill is ₹96 per 1,000 contacts a month, the first 1,000 contacts are free with no expiry, and unlimited team members ship on every plan including that free one. A workspace with three agents and one with thirty pay the same, because they are being charged for the same thing. The full pricing page shows the slider and the arithmetic.

Do all WhatsApp platforms charge per agent?

No, and a page claiming otherwise would be the kind of claim this page exists to avoid. Here is what six platforms publish about team size, read on 22 August 2026.

Three of the six publish a per-seat price. One caps its plans and quotes anything above the cap on request. Two do not charge for seats at all. That is worth knowing precisely rather than approximately, because it means the seat question is not the only question.

Look at the Interakt row again, because it is the more interesting one. Agents are genuinely unlimited from its cheapest tier — but the plan cards say those agents all hold the owner role until Advanced at ₹3,799 a month plus taxes. The Growth feature list separately names "Access Permissions for Agents", so the two statements on that page do not quite agree, which is a fair thing to ask them about before you buy.

Unlimited agents who can all do everything is a different product from unlimited agents you can wall off from each other, and only one of those is a team inbox. The switching comparison for the seat-priced end of the market is on our Wati alternative page.

Can a shared inbox stop the wrong agent reading a conversation?

This is the question that separates a group chat from a team product, and almost nobody asks it during a demo.

WabaCRM's answer is departments. A department decides which agents can see which WhatsApp number, so the people answering your support line cannot read the sales pipeline, and a franchise partner working one number cannot see another's customers. Assignment, auto-routing, message logs and exports all narrow to the same wall.

The part worth borrowing as a test: ask whether the wall holds on the vendor's API, not just in the browser. A permission enforced in the interface is enforced where a customer would notice it and nowhere else, and an integration, a mobile app or an exported report will walk straight around it.

We know that shape because we found it in our own product. A security audit on 19 August 2026 established that the department wall lived in the inbox query alone: a member restricted to one number saw only their own threads on screen, and every workspace conversation through the REST API.

It now lives in one visibility check that every by-id route runs through, and the same audit moved the check onto the realtime feed, so a workspace-wide broadcast carries identifiers and a timestamp rather than message text.

Two smaller things belong to the same argument. Switching a teammate off has to end their sessions and revoke their API tokens, or a departed agent's phone keeps sending as the business. And a button hidden from a role has to be refused by the server as well, because hiding a control is a courtesy and refusing an action is a permission.

None of that is visible in a screenshot; all of it is answerable by asking. The rest of the inbox — the 24-hour countdown, quick replies, media, reactions, auto-routing by department — is on the features page.

Can your team share the number that is already on your phone?

Usually, yes, and this is the part people assume they have to give up.

Meta calls it coexistence: the number stays registered in the WhatsApp Business app on the owner's handset and connects to the Cloud API at the same time, with messages mirrored both ways. The owner keeps replying from their thumb, the team works the same conversations in a browser, and the customer sees one number behaving normally.

It has a price in limits rather than money. Meta's documentation gives such a number "a fixed throughput of 20 mps", and lists four things switched off in the phone app: disappearing messages, view once messages and live location are disabled for all one-to-one chats, and broadcast lists are disabled with no new ones creatable.

Whether your past chats appear in the new inbox is your platform's decision rather than Meta's. WabaCRM deliberately does not import them, so a shared inbox starts empty and fills from the next message.

The full set of trade-offs, including the ones that only bite in month two, is in the coexistence guide.

Who does not need a shared WhatsApp inbox?

Plenty of businesses, and it is cheaper to find out now.

If one person answers the phone and your customers already have your number saved, the WhatsApp Business app is doing the job, and a platform adds cost, a Meta verification wait and a template approval step for nothing you are missing. If two or three share the load and nobody needs to be prevented from seeing anything, linked devices cover it, and the multi-agent tier adds assignment without changing anything else.

The line is not customer count. It is the first time one of these is true: a conversation was answered twice, or not at all, and nobody could tell which; you need to know how fast your team replies and cannot measure it; or somebody has to be stopped from seeing a set of conversations. Those are the three failures a shared inbox is for, and none of them arrives gradually.

If none has happened yet, prove the channel on the app first. Moving later costs you nothing you have built — the number stays yours, in your own Meta business portfolio, and coexistence means the handset need not go quiet on the day you move.

Every WhatsApp and Meta claim here was checked against WhatsApp's Help Centre and Meta's developer documentation on 22 August 2026 and is linked to its source above. Every competitor price was read off that vendor's own live pricing page on the same date, with the plan and the billing commitment named beside it; prices change without notice, and the vendor's page is authoritative rather than this one. Where a figure is not published — the cost of an eleventh DoubleTick agent — it is marked as not published rather than estimated.