Add to Preferred Sources
WhatsApp multiple users access means letting more than one person read and reply to the same business number, and there are three ways to do it: link up to four extra devices to the WhatsApp Business app, connect the number to the API through a shared inbox, or run both together through Meta's coexistence feature. Which one fits depends on whether several people reply at the same time, whether chats need a named owner, and whether you need groups and broadcast lists. The wider WhatsApp marketing guide for South Africa covers the channel; this post covers the team-access question on its own.
Most answers stop at "link four devices". The limits that bind a South African team sit further down: five devices in total on the standard app, a disconnection risk if the main phone goes unused for about two weeks, no way to assign a chat to a named person, and a feature trade-off when you move to the API. This post counts the seats and shows which route breaks first.
Quick Answer
On the standard WhatsApp Business app, one number can be used on the primary phone plus up to four linked devices, so five devices in total. That covers a small team that replies in turns. A team where several people answer at once, or where chats need a named owner, needs a shared inbox on the API. Coexistence lets the app and the API share one number during that move, but onboarding unlinks every companion app (they must be re-linked) and drops group chat support and blocks new broadcast lists.
Not sure how many people your number can really carry?
Send us how many staff reply to customers and when, and we will tell you which of the three routes breaks first for your setup.
Get a setup reviewHow Does WhatsApp Multiple Users Access Work on One Number?
One WhatsApp number can serve a team through three routes: the app with linked devices, the API behind a shared inbox, or coexistence, which runs the app and the API on the same number. The first needs no new software. The second is built for teams. The third is a bridge between them.
| Route | How people get in | Seat ceiling | What you give up | Best for |
|---|---|---|---|---|
| Business app with linked devices | Scan a QR code from the main phone on a laptop, tablet or second phone | Primary phone plus four linked devices (five in total) | No chat assignment or internal notes; the main phone must stay in use | A small team that replies in turns, using no more than five devices |
| API with a shared inbox | Each agent logs in to the inbox software of your provider | Set by your inbox provider's own plan, not by Meta or the app | The app's day-to-day chat screen; setup, provider fees and per-message charges on Cloud API messages | Teams that need assignment, notes and reporting |
| Coexistence (app plus API on one number) | Staff keep the app while the API runs campaigns and automation; companion apps are unlinked at onboarding and must be re-linked | The app's limits apply to the app side, and the five-device count restarts at re-linking (Windows and WearOS companions are not supported) | Group chats, new broadcast lists (existing ones become read-only) and disappearing messages on that number | Teams moving to the API without abandoning the app overnight |
The seat ceiling in the first row comes from WhatsApp's own announcement of multi-device support, which says you can link your phone as one of "up to four additional devices", and that team members can answer customers from their own phones under the same WhatsApp Business account (WhatsApp blog). The detail on the other two rows comes from Meta's documentation and is covered below.
Counting Your Five Seats Before You Hand Out QR Codes
A seat count is the number of devices signed in to one WhatsApp Business number, and the app caps it at five: the primary phone plus four linked devices. The cap is on devices, not people, so a team of three can already use most of it, and WhatsApp multiple devices set-ups fill up faster than owners expect.
One practitioner guide reports that each browser session counts separately, so two WhatsApp Web tabs on one laptop use two of the four linked slots (Replai). Treat that as a practitioner report rather than a Meta statement, and test it before you rely on it.
Worked example (hypothetical): a panel beater's front office runs one main phone kept at the counter, a reception desktop, a workshop tablet for quote photos, and the owner's laptop. That is one primary phone plus three linked devices, so four of the five device slots are used. Adding the owner's own phone as a linked device fills the last slot, and the next hire has nowhere to go.
Count by device, not by head count. Write the list down before anyone is added, because the slot you give a part-timer is the slot you cannot give a second sales rep.
What Breaks First When a Team Shares the App
A shared-app failure point is a limit that stops a team from using one WhatsApp Business number safely, and with WhatsApp Business multiple users there are three: the main phone, chat ownership and feature gaps on linked devices. Each shows up before the five-device ceiling does.
The main phone has to stay in use. Meta's coexistence documentation says a primary device inactive for approximately 14 days triggers disconnection, and approximately 30 days for companion devices (Meta). Two practitioner guides describe the same 14-day rule for linked devices on the standard app (Chatarmin, Replai). If the main phone is a spare handset in a drawer, a long closure could lock the whole team out. Keep it charged, connected and opened regularly, and follow the habits in the backup and restore guide.
In South Africa that advice has a local edge. Load-shedding can flatten a counter phone that nobody plugged into a power bank, and many owners let staff reply from personal phones, which puts customer chats on devices the business does not control. Decide which phone is the main device, keep it on backup power, and treat any personal phone as a linked device that must be removed when the person leaves.
The app has no ownership model. Chatarmin's guide says assignment, roles and notes sit in the API tooling and not in the app, summing it up as "The app solves the device question. The team question stays open." Two staff can answer the same customer, or both assume the other has. Agree who owns which chats before it happens (see the ground rules below).
Some actions stay with the main phone. The same guides report that features such as live location, broadcast lists and status updates are limited on companion devices. Check the features your team uses daily against a linked device before you commit.
Customer chats hold personal information, so there is a compliance angle. POPIA section 19 requires a responsible party to secure personal information against "unlawful access to or processing of personal information", by identifying foreseeable risks, maintaining safeguards and checking they work (section 19, as published at popia.co.za). Every linked laptop is a place where customer chats are readable, and a former employee's linked device is an access point you must remember to remove.
If you add an inbox provider, it will likely process those chats on your behalf, and POPIA section 21 calls for a written contract that requires such an operator to maintain the same security measures and to report suspected unauthorised access (section 21, as published at popia.co.za). Whether Meta or your provider counts as an operator in a given set-up is a question for your own legal adviser.
Takeaway: the team problem is not the seat count
For WhatsApp multiple users on one number, the standard app lets up to five devices share the account, but it has no way to assign a chat to a named person, and linked devices depend on the main phone staying in use. A team that replies in turns can live with that; a team where several people answer at once, or where customers get dropped, cannot.
The API Bridge: Shared Inbox, Coexistence and What Gets Switched Off
The Cloud API route moves conversations out of the phone and into inbox software, so agents log in to that software instead of sharing a handset. Seat count, assignment and reporting are then whatever your inbox provider's plan offers; that is the provider's choice, not a Meta rule. The Cloud API is hosted by Meta, and a business phone number on the API alone can send up to 80 messages per second by default (Meta Cloud API overview). Most small businesses are unlikely to need that throughput; the draw is the shared inbox for WhatsApp multiple agents. The explainer on the Business API covers the basics, and the app-versus-API comparison sets out the trade-offs.
Coexistence is Meta's option for running the WhatsApp Business app and the Cloud API on one number. Meta describes it as a way to connect an existing app account to the API, so a business can send high-volume messages while keeping one-to-one messaging in the app (Meta coexistence documentation). The same page lists what changes:
- The business must be on WhatsApp Business app version 2.24.17 or higher, and onboarding is done by a Solution Partner or Tech Provider.
- Chat messages from the most recent 6 months can be synchronised, and the sync must be completed within 24 hours of onboarding.
- All companion apps are unlinked at onboarding, and the business can then re-link supported ones; Windows and WearOS companions are not supported.
- Group chats are not supported. Disappearing messages, view-once messages and live location are disabled for one-to-one chats.
- New broadcast lists cannot be created, and existing ones become read-only.
- Throughput on a coexistence number is capped at 20 messages per second, against the 80 default for an API-only number above.
- Messages sent in the app stay free, while Cloud API messages incur standard charges.
Those limits decide the route for many SMEs. A business that sends offers through broadcast lists can no longer create new ones on a coexistence number; the broadcast lists versus groups comparison shows what you would be replacing it with.
On cost, Meta has charged per delivered message since 1 July 2025, with rates set by message category and the recipient's country calling code (Meta pricing documentation). Meta's page lists rate and free-message changes effective 1 October 2026, so this post prints no rates; use the API pricing breakdown and Meta's current rate card for your budget. Inbox software and provider fees come on top and vary by provider.
Planning a move from the app to a shared inbox?
Tell us your monthly chat volume and team size and we will give you a straight fit assessment, including what you would lose on the way.
Request a fit assessmentWhich Route Fits Your Team: A Decision Table
The right route for WhatsApp multiple users South Africa teams is the one whose hard limit your team will not hit this year. The table keys the choice to constraints you can check today rather than to a headcount threshold: the trigger for moving off the app is several agents answering at once or chats without a named owner, not the number of staff on the payroll.
| If your situation is... | Route | Why | Watch out for |
|---|---|---|---|
| Staff reply in turns, each chat has one clear owner, and the devices fit within five | App with linked devices | Costs nothing extra and fits within the five-device ceiling | Keeping the main phone in use; deciding who owns each chat |
| Several agents answer at the same time, chats have no named owner, or customers go unanswered | API with shared inbox | Assignment and notes stop two agents answering the same person | Per-message charges and inbox fees; app features you will no longer use |
| Heavy use of broadcast lists or groups, but a team that has outgrown the app | Test before committing | Coexistence blocks new broadcast lists, makes existing ones read-only and does not support groups | Replacing lost features, and re-linking companion apps, before you migrate |
| Need to connect chats to a CRM or run automation | API, or coexistence for the transition | Cloud API messaging is what integrations hook into | Fields and consent records that must be mapped; see the CRM integration guide |
| Need more than five devices but not yet ready for the API | Ask Meta about your account's limit | The five-device figure is the standard-app limit; paid Meta plans may differ, and this research could not verify what they allow | Do not plan headcount around an unconfirmed higher limit |
If you are still deciding between the free app and a paid inbox, the business app versus personal WhatsApp explainer is the right first step, and WhatsApp customer service covers the response-time habits that sit alongside the tool choice.
Ground Rules That Keep a Shared Number From Turning Into a Mess
Ground rules for a shared number are the written agreements that stop two staff answering the same customer or nobody answering at all. They cost nothing and work on either route.
- Name an owner for every open chat. The app has no assignment feature, so use labels or a simple handover note, and give each staff member a time block rather than shared responsibility.
- Keep a device register. List which device is linked, whose it is and when it was added. The register is the first thing you check when someone leaves.
- Remove access on the day someone leaves. Unlink their device from the main phone and change any shared passwords. This is a practical POPIA section 19 safeguard, not a legal formula.
- Sign messages with first names. Customers see one business name; a name at the end tells them who is helping and gives you a trail.
- Keep customer details outside the chat. Notes and contact data in a CRM or sheet survive a lost phone; see the contact organisation guide and the CRM guide for small businesses.
- Set shared away hours. One away message for the whole team avoids contradicting replies; the away message best practices cover the wording.
Takeaway: process beats the tool
On the app, a written chat-ownership rule and a device register do more to protect customers than adding a fifth device. When those rules start to need software to enforce them, that is the signal to move to a shared inbox on the API.
Why South African Businesses Choose Growth Pulse Media
Growth Pulse Media was founded by Dirk van Greuning, who built and scaled a large South African ecommerce business before starting the agency. The work is executed in-house, with a limited client load so each account gets senior attention. GPM's paid media work runs on Meta Ads, and click-to-WhatsApp advertising is where team inbox pressure often starts, because paid enquiries arrive in bursts (see click-to-WhatsApp ads in South Africa).
The WhatsApp marketing service page outlines how the channel fits into a wider plan. This post is independent guidance on seats and routes. Handling WhatsApp multiple users well starts with the ground rules above, and it does not require an agency.
Who This Is NOT For
This post is the wrong fit for readers who need a build guide, a provider shortlist or an exact quote.
You need screen-by-screen linking steps. Menu names change between versions, and WhatsApp's help centre is the authority for the clicks. This post covers the decision around them.
You want a ranked list of inbox providers with prices. This post does not compare providers or print rates, because Meta's rates and free-message rules changed again on 1 October 2026. Get current quotes from providers directly.
You want several separate numbers on one handset. That is a different question from sharing one number across a team. This post covers one number, many people.
Want a second opinion before you add the next device?
Ask for a free audit of how your team handles WhatsApp enquiries today and where chats are slipping. No obligation.
Book a free auditFrequently Asked Questions
How many people can use one WhatsApp Business number?
The standard WhatsApp Business app supports the primary phone plus up to four linked devices, so five devices in total. WhatsApp says you can link a phone as one of up to four additional devices. With the API and a shared inbox the app limit no longer applies, and the seat count depends on your inbox provider's plan.
Can two employees use the same WhatsApp Business account on different phones?
Yes. A second phone can be linked as one of the up to four additional devices, and WhatsApp says team members can respond to customers from their own phones under the same WhatsApp Business account. Both people see the same chats, so agree who owns each conversation.
Do linked devices stop working if the main phone is switched off?
They can. Meta's documentation says a primary device inactive for approximately 14 days triggers disconnection, and practitioner guides describe linked devices being logged out on the same 14-day basis. Keeping the main phone charged, on backup power during load-shedding, and opened regularly avoids the problem.
What is WhatsApp coexistence?
Coexistence is a Meta feature that connects an existing WhatsApp Business app account to the Cloud API, so one number runs on both. It requires app version 2.24.17 or higher and onboarding through a Solution Partner or Tech Provider. Onboarding unlinks all companion apps, which must then be re-linked. It does not support group chats, and new broadcast lists cannot be created.
Do I need the WhatsApp Business API for a team of three?
Not necessarily, because headcount is not the trigger. Three people who reply in turns, each with a clear chat owner, fit within the app's five-device limit. The API becomes worth considering when several agents answer at once, customers go unanswered, or you need assignment, notes or a CRM link that the app does not offer.
Get your team on one number without dropping customers
Growth Pulse Media is a Johannesburg agency running Meta Ads and Google Ads, working with Shopify and Omnisend. Tell us who answers your WhatsApp enquiries today and we will tell you which route fits. No obligation, and we will get back to you within 24 hours.
Talk to Growth Pulse Media