WhatsApp team inbox: how multiple agents can share one number, and how to run it

What is a WhatsApp team inbox?

A WhatsApp team inbox is a setup in which a team answers customers from a single business number, with each chat assigned to one person and the history available to colleagues. The customer always writes to the same place. On the inside, several people work without answering the same message twice and without leaving anyone unanswered.

You will also see it called a shared WhatsApp inbox, multi-agent WhatsApp or a WhatsApp multi-user platform, and the idea is almost always the same. It differs from omnichannel, which brings several channels together, and from a chatbot, which automates replies. A company can run a team inbox on WhatsApp alone, with no bot at all. What defines it is people sharing one number in an organized way.

In practice, four things separate a team inbox from several people passing a phone around. Every chat has an owner. The history belongs to the company rather than to someone's device. There is a rule that decides who gets the next chat. And a manager can see who is waiting, for how long and with whom.

You can build those four things in three ways: through the WhatsApp Business app with linked devices, through the official API with a shared inbox, or through tools that imitate WhatsApp Web. The agent's screen can look identical in the last two. What changes is how the number is connected to WhatsApp, and that decides how much risk the company is taking on.

3 ways to get a WhatsApp team inbox: comparison table

The comparison below summarizes what comes from the WhatsApp Help Center, Meta's documentation and the Terms in force, checked on November 2, 2026. Read each line in the same order: app, official API and unofficial tool. The details of each option follow in the next sections.

Connection and limit. App: a primary phone plus up to four devices, or up to ten with Meta Verified or Meta One benefits. Official API: the number is connected to Meta's platform through an official flow, and the number of people depends on the tool you hire. Unofficial: a QR code scan, as if the tool were one more device, with whatever limit the vendor offers.

Organization. App: manual chat assignment, with no queue, automatic distribution or response time report. Official API with an inbox: queues, distribution, deadlines, internal notes, access roles and reports, depending on the platform. Unofficial: it can have similar features, because the screen belongs to the vendor, and that is why comparing by demo is misleading.

Sending rules. App: regular chats and broadcast lists, with no templates. Official API: free text for 24 hours after the customer's message and an approved template outside that window. Unofficial: it may promise sending with no template or approval, outside the rules of Meta's platform.

Cost. App: free for up to four devices, with a subscription above that. Official API: platform and messages, in models that vary between per agent, per contact and per message. Unofficial: a monthly fee per user or per connection, which looks like a saving for as long as the number keeps working.

Risk and who it suits. App: low risk and a low ceiling, good for up to four people with little volume. Official API: rules to follow and monitored quality, for those with a real queue or who rely on the number to sell. Unofficial: a temporary or permanent ban, as the WhatsApp Help Center warns, so we don't recommend it for a number the company can't afford to lose.

Multiple agents on the WhatsApp Business app: the linked device limit

The About linked devices page in the WhatsApp Help Center says an account works on up to four devices at a time, in addition to the primary phone, which is still required to register the account and link new devices. Linked devices work while the phone is offline, but they log out if the primary phone goes unused for more than 14 days.

For more people, there is the multiple agents feature. According to the page of the same name, it raises the limit to up to ten devices, lets you name each one and assign chats, with a filter for chats assigned to you. The path runs through Tools, Subscriptions, Meta Verified or Meta One, Linked devices. Customers can't see which agent replied or who the chat was assigned to.

The exact number of devices depends on the subscription. Meta's announcement of Meta One, published in September 2026, lists more linked devices on WhatsApp under the Advanced plan, along with team access to the account without sharing a password. The same text warns that plans, benefits and availability may vary by region, app and account. Before deciding, open Tools, Subscriptions on your phone and see what your account is offered.

Two traps are easy to miss. If the subscription is canceled or the benefits change, only the last four active devices stay connected, according to the Help Center, and the other agents are left out until that is fixed. And with more than four devices, calls ring only on the primary phone. Anyone planning to grow by adding devices has to account for both.

The app works well for a team of up to four people, with a volume all of them can keep an eye on. The ceiling shows up when you need what the Help Center doesn't promise: a queue, automatic distribution, deadlines, reports and limits on what each person can see. Assignment is manual, and nobody measures how long the customer waited. If you already miss those controls, the problem is no longer the number of devices.

A team inbox on the official API: what a shared inbox solves

The official API is Meta's connection for businesses, explained in our guide to the official WhatsApp Business API. It has no concept of an agent. Messages flow in and out through a system, and with no app in the path there is no primary phone or device slot. The number of people who can reply depends only on the platform you choose.

The shared inbox is the part the team actually uses. It receives the number's chats, applies queue and distribution rules, shows the deadline for each one, keeps internal notes and opens the customer record alongside, which a WhatsApp CRM extends with a pipeline and sales history. This set of features varies a lot from vendor to vendor, so it is worth comparing item by item.

The rules come with it. WhatsApp's messaging policy, updated on September 23, 2026, allows automation within the 24-hour window as long as there is a path to a human. Outside the window, only an approved template works. And since October 1, 2026, according to Meta's pricing page, each number has an allowance of 1,000 delivered service messages per month, and the ones after that are charged.

A 2026 change alters the conversation about who owns what. In Meta's new account model, which started on September 23, 2026 and was due to reach all businesses by mid-October, the old account splits into a WhatsApp account, holding the numbers, and a Messaging account, holding templates and billing. The documentation says the WhatsApp account is always owned by the client or direct developer, and that partners get access through sharing.

Tools that imitate WhatsApp Web: ban risk and what the Terms say

The third path works like this: you scan a QR code on the vendor's screen, and its system starts operating your number as if it were one more linked device. The appeal is obvious. It goes live in minutes, accepts a regular number and requires no verification or templates. In a demo, the screen looks just like an official platform.

WhatsApp's wording is direct. The Help Center's page on linked devices says WhatsApp Web and linked devices only work through official applications, and that linking your account to an unofficial app or website, now or in the past, may result in a temporary or permanent ban. The part about the past matters, because switching tools today doesn't erase the risk from the old connection.

The Terms for the WhatsApp Business app, effective September 23, 2026, point the same way. Item g of the restrictions forbids developing or using applications that interact with the app's services without prior written consent. The security section says the company is responsible for all activity on its account. In practice, whoever hires the tool bears the consequences, even if another company wrote the software.

A ban can't be solved by the vendor either. The Help Center's page on Business app bans says only WhatsApp can ban or unban an account, and that third-party services can't remove a ban. If the app shows no review option, the decision is final. For an operation that runs on one number, that means every queue stops. Our guide on a banned WhatsApp account covers what to do next.

This debate is on the first page of search results. On November 2, 2026, we read the pages of eight vendors ranking well on Google in Brazil for the local term. Three state outright that they use the official API. Three mention a QR code, one of them offering QR code or API as a choice. Two don't say how they connect. In one case, the blog defends the official API while the home page says to scan the QR code. A page proves nothing alone, but it shows you have to ask.

A note on vocabulary helps here. Some industry articles say these tools are illegal. WhatsApp's documents talk about terms violations and bans, and that is where the risk should be measured: losing the number, having no access to history and backups while the ban lasts and, on a paid account, losing the Meta Verified subscription, as the Help Center explains.

How to tell if a tool uses the official API: 5 questions for vendors

How is my number connected? The answer you want is Embedded Signup, Meta's registration flow opened on the partner's site, with an authorization screen. Don't assume every QR code is a problem. For coexistence, Meta's Embedded Signup documentation also shows a QR code, scanned from inside the Business app, and the connection then appears under Settings, Account, Business Platform. The bad sign is a QR code scanned under Linked devices, which turns the tool into one more device.

Does the number appear in my Meta account? Ask to see it together. In WhatsApp Manager, under Account tools, Phone numbers, Meta's documentation says each number shows a status, and it must be connected to send and receive through the API. After the account migration, Meta Business Suite has separate tabs for WhatsApp accounts and Messaging accounts. If the number isn't anywhere in your account, be suspicious.

How do I reach a customer after 24 hours? On the official API, the answer is always an approved template, and the vendor should show you where templates are created and which category each one has. If the answer is that you can send any text at any time with no approval, that rule isn't being applied, and the likely reason is that the connection doesn't go through the API.

What happens if the phone is switched off? On an API-only connection, nothing, because there is no phone in the path. On coexistence, the documentation lists a disconnection when the primary device is inactive for about 14 days, and the vendor should be able to tell you that. If the answer is to keep the phone plugged in or scan the QR code again when the session drops, you now know how the tool works.

Who owns what, and how do I leave? Ask whether the vendor is a Solution Partner or a Tech Provider, the categories Meta names for offering this registration. Ask whose name the account and number are under. In the new model, Meta says migrating a number from one Solution Partner to another isn't supported, and that the client shares its WhatsApp account with the new partner. Also ask for a history export and the contract clause on bans.

A vague answer to any of these five is information too. Anyone operating on the official API can answer plainly, because this registration is their daily work. Keep the answers in writing, by email or in the proposal, and check them at connection time. To compare companies with a source for each data point, our guide to WhatsApp API platforms puts the main ones side by side.

How to run the operation: queues, team routing and distribution

Start with queues, and start with few. A queue is justified when one group of people resolves things another group can't. If two queues have the same people, they are one queue. For a distributor, for example, three may be enough: sales, orders and finance. Too many queues scatter people, leave chats sitting in a box with no one free and create needless transfers.

Routing decides which queue a chat goes to. The most used options are a short button menu, an AI agent that understands the request, rules by tag, area code or priority, and the inbound number, when the company has more than one. The agent must identify itself as AI at first contact and hand over to a person when the customer asks. A chat with no clear destination goes to a general queue with a named owner.

Inside the queue, distribution picks the person. Round-robin is the default for interchangeable agents. Lowest load suits long chats that tie someone up for longer. Skill-based makes sense for technical subjects or languages. Last agent works in consultative sales, where the customer already knows someone. Pulling from the queue works in very small teams and tends to reward whoever picks the easy chats.

To work out how many people you need at peak, use simple math: chats per hour at peak, times minutes of actual work per chat, divided by 60, divided by your target occupancy. In an example with 30 chats per hour, 6 minutes of work and 75% occupancy, the result is 4 people. These numbers are only an illustration. Measure your own for two weeks before building the schedule.

Finally, hours and coverage. Each queue needs published hours, someone responsible outside them and a rule for lunch, vacations and absences. Whoever leaves the rotation stops getting new chats and keeps the ones already theirs. Outside hours, the away message says when someone will reply, and the chat enters the next shift's queue. Our page on customer service for support teams shows this design in use.

Deadlines, internal notes and handoffs with context in a team inbox

Three clocks are enough: first reply, each following reply and case resolution. A starting point of ours, not a market figure, is five minutes for the first reply during business hours, fifteen for the following ones and one business day to resolve a simple case. Adjust to what your operation delivers. Count time only while the ball is with the company, and treat a customer's messages in a row as a single one.

One deadline nobody sets rules all the others, the 24-hour window. A chat left idle from one day to the next loses free text, and picking it up again requires a template. So create an internal alert well before that, for example at 20 hours with no reply, and keep follow-up templates ready for cases that depend on another department.

The internal note is what saves you from asking again. The customer doesn't see it, and one format works well: what the customer wants, what has been checked, what is missing and what was promised, with a time. A sample handoff note: “Order 4821. Customer wants to change the address. Confirmed it hasn't left the warehouse. Waiting on logistics. Promised a reply by 2 p.m.”

For the customer, the handoff has to say who it goes to, that they won't repeat anything and when they will hear back. A sample: “I'm passing your case to Maria in logistics. She has the full history, so you don't need to explain it again. You'll have an answer by 2 p.m.” Don't ask for documents, passwords or codes in the chat. WhatsApp's policy forbids asking for full payment card, financial account and ID document numbers.

In some markets this is already law. Brazil's Decree 13,135/2026, published on October 13, 2026 and in force 20 days later, covers federally regulated suppliers, under each regulator's criteria, and digital financial services supervised by the Central Bank. It bans asking consumers to repeat a request (art. 6), caps electronic channels at five service levels (art. 13) and requires the system to give agents access to the customer's history (art. 18).

It also guarantees real-time human service from 8 a.m. to 8 p.m. every day on electronic channels (art. 12), accepts AI for triage if that human option exists (art. 3) and requires keeping message content for at least 90 days (art. 19). Spain's Ley 10/2025 covers basic services and large companies, and bots there must offer a human at any time (art. 8.2). If neither applies to you, use them as a yardstick for queues and handoffs.

A shared WhatsApp inbox for small teams: the minimum that works

With two to five people, the common mistake is copying the operation of a large contact center. One queue, simple round-robin and five saved replies solve most of the problem. Name one person responsible each day, who checks what has no owner and redistributes it. Use only the tags someone will actually use to decide something, such as urgent, waiting on customer and sale.

The routine can be short too. Open the day with the list of unowned chats, close it with nothing about to expire in the window and review, once a week, the chats that went past their deadline. Fifteen minutes a week with that list teach more than a report nobody reads. If the owner also answers, agree that a chat assigned to a colleague gets no reply from the owner without a note.

Three signs show the app has become too small. Two people answer the same customer with different information. Someone has to stay with the primary phone for the team to work. Or you can't say how many customers went unanswered yesterday. In those cases the next step is worth it, even with few people, and the cost math further on shows which model charges a small team less.

What changes when a number moves to the API, and coexistence with the app

There are two ways to move a number already on the app. In a full migration, Meta's page on migrating a number says that, once you delete the app account and register the number on the Cloud API, the existing history is lost and the number can't return to the app until it is deregistered from the API. The whole team then works through the platform, and the phone leaves the operation.

The second is coexistence with the app, in which the same number stays on the app and the API. The documentation allows syncing contacts and up to 180 days of individual chats, once only, in the 24 hours after connecting, and the business can decline to share its history. Groups don't come along. For a customer base built on the phone, this path preserves the most.

Here lies a trap for anyone using multiple agents. Connecting unlinks all linked devices, and the coexistence documentation talks about up to four of them afterwards, excluding WhatsApp for Windows and WearOS. Messages sent from an unsupported device don't reach the platform. If the team uses ten devices, plan to move people to the shared inbox before connecting, not after.

Other things have to be rebuilt. The app's greeting, away messages, quick replies and labels don't exist on the API, so the equivalent rules must be set up in the platform. Broadcast lists become read-only. Disappearing messages, view once and live location are turned off in individual chats. And the number's throughput is fixed at 20 messages per second, which only matters for large campaigns.

Lastly, agree on who replies where. According to the same documentation, a message sent from the app doesn't open or extend the Cloud API window and stays free of charge, while one sent through the API follows the API's rules and prices. One possible split is the owner on the phone for long-standing customers and the team in the shared inbox. Without that agreement, the customer gets two replies from two places.

What a WhatsApp team inbox costs: per agent or per message

Vendors use four logics, often combined. Per user: respond.io charges by monthly active contacts and includes a set number of users per plan, with paid extras, and Brazil's Zenvia also charges for users beyond the plan. Per active agent and conversation: Blip counts unique daily conversations and agents who handled at least one chat in the month. Per daily contact: Octadesk lists unlimited users and an allowance of daily contacts, with its helpdesk sold per user. Official pages read on November 2, 2026.

The fourth logic is per message. At CCX Messages, the monthly fee follows the month's message tier, each message has a published price and agents don't pay. None of these models is cheap or expensive by nature. Each one grows with a different variable, and what matters is which one grows in your company. Our comparison of WhatsApp CRMs with no per-seat fee shows who charges what.

Before asking for a quote, gather four numbers. P: everyone who needs to log in, including supervisors, finance, salespeople who answer occasionally and vacation cover. A: how many of them answer in a normal month. C: unique contacts with a chat per day. M: messages the company sends per month, split into service, utility and marketing. Almost everything a salesperson will quote comes from these four letters.

The math looks like this. Per agent: the plan, plus P or A above the allowance times the extra user price, plus messages if they are separate. Per contact or conversation: the plan, plus C above the allowance times the overage, plus anything billed outside it. Per message: the tier's monthly fee, plus M times the price of each category. Add setup, mandatory consulting, AI and extra numbers, which change the result.

Run the math in three scenarios: a normal month, a peak month such as Black Friday, and a month with a team 50% larger. If you have many people who answer little, the per-person model weighs heavily. If you have few people and high volume, it may come out better, and it is worth admitting that in the spreadsheet. Divide the total by resolved chats, and you have a figure you can compare across proposals.

Two cost traps. The first is the allowance of 1,000 service messages per number, in force since October 2026, because a chat with a lot of back-and-forth can now weigh on the bill. Check whether the proposal accounts for it. The second is a shared login to save on licenses. It wrecks your audit trail, blurs who wrote what and makes it harder to remove access from someone who leaves, the subject of the next section.

Security and permissions in a team inbox: who sees what, and when an employee leaves

When ten people open the same WhatsApp, the question stops being technical. In the EU, GDPR limits data to what is necessary (art. 5) and requires security appropriate to the risk (art. 32). In California, the CCPA requires reasonable security practices, and Brazil's LGPD has similar rules. WhatsApp's app terms add that the business answers for all activity on its account and must prevent unauthorized use. Everyone needs a personal login, and access should follow the job.

A simple permission design uses five roles. An agent sees their own queue and the chats assigned to them. A supervisor sees their team's queues, redistributes chats and reads notes. Finance or another support area enters only the chats transferred to it. An administrator manages users, numbers and integrations without needing to answer. Read-only serves auditing and anyone who just follows reports. Exporting contacts or history stays with very few people.

Some rules apply in any tool. Turn on two-step verification for everyone. Don't answer from a personal phone on a personal account. Keep a record of who exported, invited or changed a role. Don't paste sensitive data into an internal note. And keep at least two of the company's own administrators on the Meta portfolio, so access doesn't depend on one person or on the vendor.

An employee's exit has to fit on a checklist, done the same day. Suspend the user on the platform, which should end the session. Redistribute open chats. Review saved replies, recent exports and API keys they created. Remove their access to the Meta portfolio. On the app, disconnect their device under Linked devices and collect the company phone. The history stays with the company.

Compare what each path offers here. On the app, the multiple agents page describes chat assignment, not per-chat permissions. On unofficial tools, your number's session runs on a third party's server, outside what the Terms allow without written consent. At CCX Messages there are nine access roles, with two-step verification that can apply to everyone, an audit trail and data hosted in São Paulo, with the exceptions declared in the Trust Center.

Step by step: how to roll out a WhatsApp team inbox in 30 days

Days 1 to 7, diagnosis and decision. Measure the baseline: chats per day, time to first reply, unanswered chats and people involved. List the numbers in use and how each one is connected. If there is a QR code tool, make leaving it a priority. Ask two or three vendors the five questions, run the cost math and choose between full migration and coexistence.

Days 8 to 14, connection and structure. Organize the Meta portfolio, with two of the company's administrators, and connect the number through the official flow. On coexistence, remember the 24 hours to sync and keep the app open during the process, as Meta recommends. Create users, roles, queues and hours. Build the saved replies and submit the follow-up templates for approval.

Days 15 to 21, pilot. Start with one queue and two or three people, and leave the others as they are. Train on real chats: assigning, writing a note, transferring, using a template and asking for help. Write down what confuses people, adjust the distribution rules and test what happens outside hours, at lunch and when someone leaves the rotation. Only then write the manual, on one page.

Days 22 to 28, the switch. Bring in all queues and the whole team, and tell anyone working from the phone when it stops being the official channel. In the first days, the supervisor opens the day with the list of unowned chats and deadlines at risk. Hold a ten-minute daily meeting, only about what got stuck. Make sure no chat gets trapped between the old system and the new one.

Days 29 and 30, review. Compare with the baseline: time to first reply, unanswered chats and transfers per chat. Cut what is left over, because a queue or tag nobody uses only gets in the way. If you want to try this design on a platform, the CCX Messages inbox puts WhatsApp and Instagram in the same queue, with round-robin, deadlines on screen and the CCX Messages AI, which answers from the knowledge base and hands over to a person with context.