Multiple Agents on a Single WhatsApp Number: A UK Business Guide

Having multiple agents on the same WhatsApp number is possible, permitted by Meta, and doesn't require workarounds. What confuses those researching is that there are three paths with very different rules: the WhatsApp Business app with linked devices, coexistence between the app and the API, and the official API with a customer service platform. This guide explains how each truly works, its cost, and when it's not worth it.

TL;DR

• With the official API, the customer service platform creates the agents, not Meta. The API has no user limit; the limit is set by the plan you subscribe to.
• The WhatsApp Business app supports 1 main phone + up to 4 linked devices, with no queuing, no transfers, and no record of who responded to what.
• Coexistence (app + API on the same number) works but caps throughput at 20 messages per second and disables features like broadcast lists.
• Since 1 October 2026, Meta has charged for service messages after the first 1,000 free per number per month. More agents sending fragmented replies = a larger bill.
• For a single agent, the official API is often overkill. From 2 or 3 agents with a queue, it pays for itself in organisation.

I'm Cleverson Gouvêa, founder of Agathas Web. I work with servers, managed hosting, Moodle, and, in recent years, with the official WhatsApp API, which is the foundation of Voyia, our customer service platform. The figures in this text were checked against Meta's official documentation in October 2026; when something comes from a secondary source, I'll state it.

Multiple Agents on a Single WhatsApp Number: What the Official API Truly Allows

The first thing that needs to be clear: the official WhatsApp API (the Cloud API, hosted by Meta itself) doesn't have the concept of an "agent". It understands business numbers, messages, templates, and webhooks. The software that sits between the API and your team handles receiving conversations, distributing them to an individual, and logging who responded.

This is why the question "how many agents does the API support?" has a surprising answer: from Meta's side, there's no user cap. The real limit is determined by your chosen platform's plan and your ability to organise the queue.

What Meta Handles

• The number and account: The business number is registered within a WhatsApp Business Account (WABA) linked to your company's business portfolio.
• Sending rules: The 24-hour customer service window, approved templates, message limits, and number quality.
• Message billing: What is paid and what is free follows the official Meta pricing page.

What the Customer Service Platform Handles

• Individual logins: Each agent logs in with their own username and password, via browser or app.
• Queue and distribution: Who picks up the next conversation, who handles which department.
• Transfers: Passing a customer from sales to finance without them needing to repeat their story.
• History and reports: Who responded, how quickly, and what was said.

This is why two products that "use the official API" can be so different for those operating multiple agents on the same WhatsApp number: the API is the same, but the service layer isn't.

Why the WhatsApp Business App Doesn't Work for a Team

Before moving to the API, many businesses try to manage multiple agents on the same WhatsApp number within the app itself. The limit is quickly reached. According to the official WhatsApp blog, an account can have up to four linked devices in addition to the main phone. In practice, that's a maximum of five screens responding from the same number.

The problem isn't just the number of screens. It's what's missing from them:

• No queuing system. Everyone sees all conversations simultaneously. Two agents might respond to the same customer, or no one responds because each thinks the other has picked it up.
• No message attribution. Messages are sent in the company's name, without a record of which individual sent them. When investigating a complaint, no one knows who promised what.
• The main phone dictates everything. Meta's own documentation states that linked devices are disconnected if the main device is inactive for about 14 days.
• Offboarding staff is manual. If an employee has left and their WhatsApp Web session remains open on their laptop, they continue to see customers until someone remembers to disconnect it.

I detailed this scenario in WhatsApp Business on two phones. For two people working side-by-side, it works. For three or more, with shifts and departments, it becomes chaotic.

Coexistence: App and API on the Same Number, and What You Lose

Since 2025, Meta has allowed coexistence: the same number remains on the WhatsApp Business app on the phone and, at the same time, is connected to the Cloud API. This is the path for those who want to use multiple agents on the same WhatsApp number without abandoning the app the owner uses.

According to Meta's onboarding documentation:

• Contacts are synchronised, and conversations from the last 6 months (180 days) can be imported;
• Group conversations are not synchronised;
• Numbers in coexistence have a fixed throughput of 20 messages per second, compared to 80 for an API-only number;
• Disappearing messages, view once, and real-time location are disabled in individual conversations;
• Broadcast lists are deactivated: you cannot create new ones, and existing ones become read-only.

When Coexistence Makes Sense

When the number has years of history, the owner doesn't want to give up the app, and outbound messages are moderate. In such cases, 20 messages per second is ample.

When It Doesn't

When the operation relies on broadcast lists, there are large campaigns planned, or no one will be opening the phone app. In these situations, a complete migration to the API causes less hassle.

How Conversations Reach the Right Agent

With multiple agents on the same number using the official API and a customer service platform on top, the conversation flow is as follows:

1. The customer sends a message to the company's number.
2. Meta delivers this message via webhook to the platform.
3. The platform decides the destination: a triage chatbot, a departmental queue, or a specific agent.
4. The agent responds via the dashboard or app, using their own login.
5. The response is sent via the API, from the same number, and is logged with the sender's name.

Distribution

The most common methods are by department (the bot menu asks "sales, support, or finance?"), by free queue (the next available agent picks it up), and by client portfolio (the customer always returns to the same salesperson). For small teams, a departmental queue is usually sufficient.

Transfers

Transferring means passing the entire conversation, including history, to another person or queue. The customer remains on the same number and doesn't need to repeat anything.

The 24-Hour Window Applies to the Entire Team

Meta's rule is per conversation, not per agent: after the customer's last message, the company has 24 hours to respond freely. Beyond that, only an approved template can be used. Queues stalled over the weekend are the most common reason for "the message isn't sending" on Monday.

How Much Does It Cost to Have Multiple Agents on One WhatsApp Number?

Having multiple agents on the same number doesn't change Meta's fees. The cost has two distinct parts: the platform subscription fee (which defines how many users you can have) and the messages billed by Meta (which depend on volume, not the number of agents).

On Meta's side, the rule changed this month. Since 1 October 2026, service messages (free replies within the 24-hour window) have been charged after an allowance of 1,000 per number per month, as per Twilio's notice on pricing changes. Utility templates sent within the window are also now charged. I detailed these costs in WhatsApp service messages: billing has begun.

Item	Who bills	What increases the cost
Platform subscription	Software provider	Number of users, features (AI, reports, BI)
Service messages	Meta	Volume of replies above 1,000 per number per month
Marketing templates	Meta	Campaigns and outbound messages outside the window
Utility and authentication templates	Meta	Order notifications, billing reminders, verification codes
Markup on messages	Some providers	Margin added to Meta's fee, per message

The Hidden Effect of More People Responding

Now that each reply counts, the team's style impacts the bill. Someone who writes 'Hi', 'how are you?', 'I'll check', and 'one moment' in four separate bubbles uses four messages where one would suffice. Multiply that by five people and an entire month.

Also, ask if the provider passes on Meta's fee at the official rate or adds a margin per message. With high volume, the margin can outweigh the monthly subscription.

Technical Limits That Emerge as Your Team Grows

Having multiple agents on the same number rarely hits a technical limit. Campaigns, however, can. The official figures, according to Meta's throughput documentation:

• 80 messages per second per number, by default, combining inbound and outbound.
• 1,000 per second with automatic upgrade, for portfolios with an unlimited limit, that reach 100,000 unique recipients in 24 hours and maintain yellow quality or better.
• If the limit is exceeded, the API returns error 130429 until traffic drops.

And there's the limit on company-initiated messages. According to Meta's limits page, new portfolios start with 250 unique recipients in 24 hours outside the customer service window, potentially increasing to 2,000, 10,000, 100,000, and unlimited. Replies within the window do not count. A detail that catches many people out: the limit is for the portfolio, not the number. If you have two numbers, they share the same quota.

In day-to-day customer service, none of this is an issue: five people responding to customers won't come close to 80 messages per second.

Comparison: The Three Ways to Have Multiple Agents on a Single WhatsApp Number

Criterion	App + linked devices	Coexistence (app + API)	Official API with platform
Screens/users	Up to 5 (1 + 4)	Platform-dependent	Platform-dependent
Individual login	No	Yes, in the dashboard	Yes
Queue and transfers	No	Yes, in the dashboard	Yes
Sending throughput	Not applicable	20 msg/s	80 msg/s (up to 1,000)
Broadcast lists	Yes	Deactivated	Campaigns with templates
Imported history	Already in the app	Last 6 months	Starts from scratch if the number is new
Message cost	Free in the app	Billed for those sent via API	Meta's fees

If you're still deciding between the app and the API, it's worth reading the comparison Official vs. Unofficial WhatsApp API: the unofficial API also promises "multi-agent support," but with the risk of number ban.

When It's Not Worth Using the API for Multiple Agents on a Single WhatsApp Number

Not every business needs this. I advise against it when:

• Only one person handles messages. The WhatsApp Business app is free and sufficient. The API starts to make sense when a second or third person joins, or when you need to send templated messages.
• Volume is very low. Ten conversations a day don't justify a monthly fee, setup cost, and training.
• The operation relies on groups. In coexistence, group conversations are not synchronised with the platform. If your customer service happens in client groups, the inbox won't replace that.
• No one will manage the queue. A platform with five users and no distribution rules just moves the mess elsewhere.

And there's the opposite case: departments that require different identities (e.g., a clinic with appointment booking and a laboratory) sometimes work better with separate numbers, each with its own display name. Multiple agents on the same WhatsApp number work well when the customer perceives the company as a single entity.

Common Implementation Pitfalls

• Migrating the number without notifying the owner. In a complete migration, the number leaves the phone app. Those unaware discover this the next day.
• Not creating templates before switching over. Without an approved template, the team cannot resume conversations that have been idle for more than 24 hours.
• Shared login. Buying 3 user licences and having 6 people share 2 logins defeats the main advantage: knowing who responded.
• Not deactivating ex-employees. With individual logins, deactivating a user is a single click. Do this on the same day as their departure, for security and UK GDPR / Data Protection Act 2018 compliance.
• Bot responding in multiple bubbles. With service message billing, a chatbot that breaks a single response into multiple messages increases the bill without improving customer service.

How Agathas Web Solves This

Voyia is the customer service platform Agathas Web built on Meta's official Cloud API, specifically designed to enable multiple agents on the same WhatsApp number with queues, transfers, and individual history. In practice, what you receive:

• Multi-agent inbox in real-time, with team-based queues, transfers between agents, and quick replies.
• iOS and Android app, for the team to serve customers away from their computer with push notifications.
• No-code chatbot for departmental triage before reaching a human.
• AI integration using your chosen model (Claude, GPT, Gemini, DeepSeek) with your own key, on Professional and Business plans.
• Reports on response times and agent performance.
• Meta's fees passed on without markup, in pounds sterling, with a VAT invoice.

Plans are per WhatsApp number: the Starter (£149/month) is for 1 agent and does not include multi-agent support; the Professional (£349/month) allows up to 3 users with queues and transfers; the Business (£749/month) goes up to 5 users with a BI dashboard. Starter and Professional plans have an installation and setup fee, which you can check with the team before subscribing. There is no long-term commitment.

How to subscribe: you choose the plan, we connect your number to the official API (including assessing whether coexistence or full migration is the best path for your case), and your team configures queues, templates, and workflows using the dashboard tutorials and documentation, with support in English. See the details and compare plans on the Voyia page.

Conclusion

Having multiple agents on the same WhatsApp number is a matter of the customer service layer, not a trick. The app supports up to five screens without any control; coexistence keeps the owner's phone and limits throughput; the official API with a platform provides individual logins, queues, transfers, and reports. With service message billing in effect since October 2026, organising your team has also become a cost-saving measure.

If your company already has two or more people vying for the same phone, the next step is simple: compare Voyia's plans or speak to our team to understand which number format best suits your operation.