Why one Business number breaks for teams
Most shops, clinics, and agencies start WhatsApp the obvious way: one phone, one Business account, one person who “has the number.” That works until the person who holds the phone is in a meeting, on leave, or asleep. Messages sit. A second login — if you even have one — creates a second history. Nobody can tell who already answered. The customer gets two replies, or none.
The number itself is not the problem. Customers already saved it. Changing it to add a teammate is how you lose the thread. The problem is that a personal device is not a team queue: there is no owner on the chat, no note the next shift can see, and no record you can search after the handset is wiped or left in a drawer.
Official multi-device limits are not a shared workspace
WhatsApp Business can link extra devices to the same account. That is useful. It is not the same job as a shared inbox. Meta’s multi-agent FAQ — About multi-agent, verified 20 August 2026 — documents the current device caps:
- Without the paid multi-agent benefit: connect up to four devices to the account.
- With multi-agent (a Meta Verified or Meta One subscription): connect up to ten devices. The exact cap follows the benefits on that subscription.
- If the primary phone is unused for more than 14 days, linked devices disconnect. New devices still have to be linked from the primary phone.
- You can name a linked device and, with multi-agent, assign chats to an agent on that account. Customers do not see which agent or device sent a message.
- Tablets are not supported. Several other companion features stay limited.
Those limits describe devices signed into one WhatsApp account. They do not describe workspace permissions, a history that survives a lost phone, or a way to stop two people typing the same answer. Assignment on a linked device is still assignment inside WhatsApp’s app. Meta does not give you a shared workspace. A team inbox is assignment inside a queue you already use for Instagram, email, and chat.
Source: WhatsApp Help Center — About multi-agent. Device numbers above were checked live on 20 August 2026. Confirm the live FAQ before you treat a cap as permanent.
Companion app and Meta Verified vs Cloud API and a shared inbox
Meta publishes two WhatsApp products for businesses. They solve different jobs.
WhatsApp Business app — companions and multi-agent
The WhatsApp Business app is Meta’s own app for small businesses. You run it on a primary phone and can link companion devices. Meta Verified / Meta One multi-agent raises that device cap and lets you assign chats inside that app. You can see which linked device sent a message. The customer cannot. The primary phone still matters: unused for more than 14 days, companions drop.
Stay on the app if one person still owns the number and a second device is only backup. That is official, and it is enough for a lot of shops. It is still one WhatsApp account on extra screens. It is not notes, collision detection, workspace permissions, or a history you can search after the phone is gone.
WhatsApp Business Platform — APIs, then software
The WhatsApp Business Platform is Meta’s API product for businesses. Shared inbox software typically connects a Business number through that kind of programmatic path so agents log into a workspace instead of linking another phone. Meta still operates WhatsApp. Meta still bills delivered template and marketing messages. The software vendor does not become WhatsApp.
InboxBay is in that second group: a shared WhatsApp workspace that connects to the Business account you already have. We do not replace WhatsApp Business. We do not claim to be a WhatsApp Business Solution Provider. We sit on a Chatwoot MIT core with an InboxBay overlay. Agents sign in at demo.inboxbay.work.
Do not treat “Cloud API” as a magic unlimited-agent switch. The API is Meta’s interface. How many people can work the queue, whether they collide, and whether notes survive a lost phone — those are properties of the software you put on top, not a number Meta prints as a team size.
What a shared inbox changes
A shared inbox puts the Business number’s chats in one list several people can see. Incoming WhatsApp lands next to the other channels you have connected. The customer still writes the same number. You do not publish a new chat identity just to add a teammate.
That is the model on InboxBay’s WhatsApp team inbox: connect the account, invite the people who actually answer, and work the queue in a browser.
Assign an owner, or the pile stays ownerless
“Anyone can take it” is how chats sit for three hours. Assignment makes follow-up someone’s job. Unassigned work stays visible instead of hiding in a pocket notification. Round-robin can spread new conversations so the first person online is not the only person working.
Assignment is not the same as a WhatsApp device name. A device name tells you which handset sent a message. An inbox owner tells you who is responsible for the next reply, including when that person is on a laptop they never linked to WhatsApp.
Collision and duplicate replies
Two people opening the same unread chat is the usual failure. Both draft a confirmation. Both send. The customer now has two slightly different answers and no idea which one stands. Collision detection exists so you can see when a teammate is already viewing or typing. Status — open, pending, resolved — keeps the same thread from being “done” in one head and “still waiting” in another.
Linked devices do not solve this. They multiply the places the same unread badge can appear. A shared inbox does not make two replies impossible; it makes the second person visible before they hit send.
Permissions and who can see what
A phone PIN is a blunt permission: you have the device, or you do not. A workspace can give an agent the queue without giving them billing, channel setup, or every brand inbox. That matters when a contractor covers weekends, or when an agency runs more than one client number.
InboxBay is a team workspace today. Custom logo, name, colors, and a branded client portal are still coming soon — we do not sell those as live. The permission you get now is the practical one: agents sign in to the workspace, not to a shared phone PIN.
History that is not in someone’s pocket
The promise that matters is reconstruction. When a customer says “you already confirmed Tuesday,” the next agent should find that message without unlocking last month’s phone. Search, notes, and labels live on the conversation. Do not plan on a full history import from every provider the day you connect; once the Business account is linked, new chats land in the inbox. Ask before you assume the archive moves.
When a team inbox makes sense — and when the phone is enough
A team inbox is the right next step when most of these are true:
- More than one person already answers the same Business number.
- Shifts, leave, or after-hours coverage matter more than a single owner’s phone.
- You need a note the customer never sees — VIP, billed, waiting on a third party.
- WhatsApp is not the only channel, and the same customer writes Instagram or email next.
- You are tired of screenshots in a staff chat as the handover protocol.
Stay on the phone — or on official companion devices — if one person still owns every chat and will keep doing so. Official multi-agent is the cheaper next step if you only need a second screen on the same WhatsApp account and you accept the device cap and the 14-day primary-phone rule. Do not buy software to decorate a process you do not have.
How InboxBay runs this workflow
The working sequence is short:
- Keep WhatsApp Business. InboxBay connects to it. It does not replace the account, the number, or Meta’s rules.
- Invite the team. Agents sign in to the workspace (login is at demo.inboxbay.work/app/login today), not to a shared phone PIN.
- Assign or round-robin. Give each thread an owner, or let automations spread new conversations so they do not sit unowned.
- Reply with context. Use saved replies for the daily questions. Leave a note when something is billed, VIP, or waiting.
Routing, tags, and saved replies are live. Suggested replies and any autonomous answering are coming soon — a person still sends every reply. Meta bills WhatsApp per delivered template or marketing message; conversation-based pricing was deprecated as of 1 July 2025. InboxBay does not collect or mark up those fees. InboxBay list prices are Starter AED 499, Growth AED 999, and Business AED 1,999 per workspace per month, with a 7-day trial and checkout on Ziina. Plans are not per agent. Meta WhatsApp fees stay extra.
If you want the product page, start at the WhatsApp shared inbox for teams. If you want the broader queue — assignment and notes on every connected channel — read the shared inbox page, or the WhatsApp shared inbox guide.