Multiple Agents on One WhatsApp Number: How It Works

Using multiple agents on the same WhatsApp number is possible, permitted by Meta, and doesn't require a workaround. What often confuses people is that there are three distinct approaches with very different rules: the WhatsApp Business app with linked devices, coexistence between the app and API, and the official API with a customer engagement platform. This guide explains how each truly works, its costs, and when it might not be the best option.

TL;DR

• With the official API, agents are created by the customer engagement platform, not Meta. The API has no user limit; the limit is determined by your chosen plan.
• The WhatsApp Business app supports 1 primary phone + up to 4 linked devices, without queues, transfers, or tracking 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 October 1, 2026, Meta charges for service messages after the first 1,000 free per number per month. More agents sending fragmented responses means a larger bill.
• For a single agent, the official API is usually overkill. For 2 or 3 agents with a queue, it often pays for itself through improved organization.

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 engagement platform. The figures in this text were verified against Meta's official documentation in October 2026; I'll indicate when information comes from a secondary source.

Multiple Agents on One 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) does not have the concept of an "agent". It understands business numbers, messages, templates, and webhooks. The software that sits between the API and your team is responsible for receiving conversations, distributing them to an individual, and logging who responded.

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

What Meta Manages

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

What the Customer Engagement Platform Manages

• Individual logins: Each agent logs in with their own username and password, whether in the browser or app.
• Queues and distribution: Determining who takes the next conversation and who handles which department.
• Transfers: Moving a client from sales to finance without them having to repeat their story.
• History and reports: Tracking 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 customer service layer is not.

Why the WhatsApp Business App Isn't Enough 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 primary 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:

• No queues. Everyone sees all conversations simultaneously. Two agents might respond to the same client, or no one responds because each assumes the other has it.
• No sender attribution. Messages are sent in the company's name, without a record of who sent them. When investigating a complaint, no one knows who promised what.
• The primary phone controls everything. Meta's own documentation states that linked devices are disconnected if the primary device remains inactive for about 14 days.
• Employee offboarding is manual. If an employee leaves and their WhatsApp Web session is still open on their laptop, they continue to see client messages until someone remembers to disconnect it.

I detailed this scenario in WhatsApp Business on Two Phones. For two people working side-by-side, it can work. For three or more, especially with shifts and departments, it quickly 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 a phone and is simultaneously connected to the Cloud API. This is the path for those who want to use multiple agents on the same WhatsApp number without giving up the app the owner uses.

According to Meta's onboarding documentation:

• Contacts are synchronized, and conversations from the last 6 months (180 days) can be imported;
• Group conversations are not synchronized;
• 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 sharing 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 abandon the app, and message blasts are moderate. In that case, 20 messages per second is more than enough.

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 such cases, a complete migration to the API causes fewer headaches.

How Conversations Reach the Right Agent

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

1. The client sends a message to the company's number.
2. Meta delivers this message via webhook to the platform.
3. The platform determines 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 through 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 open queue (the next available agent takes it), and by account assignment (the client always returns to the same salesperson). For small teams, a departmental queue is usually sufficient.

Transfers

Transferring means passing the entire conversation, including its history, to another person or queue. The client 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 client's last message, the company has 24 hours to respond freely. Beyond that, only an approved template can be used. Stalled queues over the weekend are the most common reason for "the message won't send" on Monday.

Cost of 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's monthly 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 October 1, 2026, service messages (free responses 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 subject to charges. I detailed these changes in WhatsApp Service Messages: Billing Has Begun.

Item	Who Charges	What Increases the Cost
Platform Monthly Fee	Software Provider	Number of users, features (AI, reports, BI)
Service Messages	Meta	Volume of responses above 1,000 per number per month
Marketing Templates	Meta	Campaigns and blasts outside the window
Utility and Authentication Templates	Meta	Order notifications, billing, verification codes
Markup on Messages	Some Providers	Margin added to Meta's fee, per message

The Hidden Effect of More Agents Responding

Now that every response counts, your team's communication 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 over an entire month.

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

Technical Limits That Emerge as Your Team Grows

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

• 80 messages per second per number, by default, combining incoming and outgoing.
• 1,000 per second with automatic upgrade, for portfolios with unlimited messaging tiers, reaching 100,000 unique recipients in 24 hours and with yellow quality or better.
• If the limit is exceeded, the API returns error 130429 until traffic decreases.

And there's the limit on business-initiated messages. According to Meta's messaging 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. Responses within the window do not count. A detail that catches many people off guard: 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 typically an issue: five people responding to clients won't come close to 80 messages per second.

Comparison: The Three Ways to Have Multiple Agents on One 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 dashboard	Yes
Queue and Transfer	No	Yes, in dashboard	Yes
Sending Throughput	N/A	20 msg/s	80 msg/s (up to 1,000)
Broadcast Lists	Yes	Deactivated	Campaigns with templates
Imported History	Already in app	Last 6 months	Starts from scratch if number is new
Message Cost	Free in app	Charged 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 API vs. Unofficial WhatsApp API: the unofficial API also promises "multi-agent support," but with the risk of number banishment.

When Using the WhatsApp API for Multiple Agents Isn't Worth It

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

• Only one person is handling 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 template-based messaging.
• Volume is very low. Ten conversations a day don't justify a monthly fee, setup costs, and training.
• The operation relies on groups. In coexistence, group conversations are not synchronized 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 around.

And there's the opposite case: departments that need different identities (e.g., a clinic with appointment scheduling and a lab) are sometimes better off with separate numbers, each with its own display name. Multiple agents on the same WhatsApp number work well when the client sees 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 of this will find out the next day.
• Not creating templates before flipping the switch. Without an approved template, the team cannot resume conversations stalled for more than 24 hours.
• Shared logins. Buying 3 users and having 6 people share 2 logins defeats the main advantage: knowing who responded.
• Not deactivating former employees. With individual logins, deactivating a user is one click. Do it on the same day of termination, for security and CCPA compliance.
• Bot responding in fragmented messages. With service messages now being charged, a chatbot that breaks a response into multiple messages increases the bill without improving customer service.

How Agathas Web Solves This

The Voyia is the customer engagement 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 tracking. In practice, here's what you receive:

• Real-time multi-agent inbox, with team-based queues, agent-to-agent transfers, and quick replies.
• iOS and Android app, allowing your team to serve customers away from their computers with push notifications.
• No-code chatbot for departmental triage before reaching a human agent.
• AI integration using your chosen model (Claude, GPT, Gemini, DeepSeek) with your own key, available in Professional and Business plans.
• Reports on response times and agent performance.
• Meta's fees passed on without markup, billed in US dollars, with transparent invoicing.

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) supports up to 5 users with a BI dashboard. Starter and Professional plans have a setup and configuration fee, which you can inquire about with our team before subscribing. There are no long-term contracts.

How to subscribe: you choose your plan, we connect your number to the official API (including evaluating whether coexistence or a complete migration is the best path for your case), and your team configures queues, templates, and workflows using the dashboard tutorials and documentation, with English-speaking support. See 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 handles up to five screens with no control; coexistence keeps the owner's phone active and limits throughput; the official API with a platform provides individual logins, queues, transfers, and reporting. With service messages being charged since October 2026, organizing your team has also become a cost-saving measure.

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