WhatsApp multi-agent: several agents, one single number

What multi-agent really means

Multi-agent means more than one person answering on the same number, at the same time, each with their own access. If any part of that sentence is not true on your team, you do not have multi-agent — you have shift-swapping with a nicer name.

The typical scene: the company phone sits in a drawer and whoever needs it goes and grabs it. Or WhatsApp Web is open on one person's machine and the rest of the team asks for screenshots. By the end of the day nobody knows who answered what, the customer gets two different answers, and the only person who knows that lead's history is whoever was holding the device.

What you can do for free

Before selling anything: WhatsApp already solves part of this on its own, and it is worth using. The app lets you link additional devices to the same number — the main phone plus a few devices and browsers connected at once. If your team is two or three people and volume is low, that may be enough for a good while.

The 4 points where it breaks

1. There is no "who". Every reply comes from the same account. You cannot tell who answered, who took too long, who promised the discount nobody approved.
2. There are no permissions. Whoever logs in to answer a quote can also delete chats, export contacts and read the history of a customer that is not theirs.
3. Someone leaves, the history leaves. When a rep quits, what they agreed with each customer lived in their head and in a conversation only they were following.
4. The number is a regular one. A normal WhatsApp account runs under personal-account rules: no visible quality rating, no warning before a restriction, and nobody to escalate to when something breaks. That is your company's entire number resting on that.

The fix: the number registered with Meta

The four problems above share the same root: the number is a regular account, and a regular account has exactly one owner. The way out is to change the number's regime — register it with Meta through the Official API. And the Official API never arrives on its own: it always arrives through a platform. Ours is the Pragmaz platform.

• Each agent with their own login. You invite by email, they sign in with their own account, and every reply has an author.
• Permissions per agent. Who can run broadcasts, who can place calls, who only answers what comes in — you define it, and it is not the same for everyone.
• Shared history. The conversation belongs to the company, not the rep. Whoever takes over later opens the chat and reads everything that was agreed.
• A number with a visible quality rating and a warning before restrictions, with the new-conversation cap rising by Meta's published rule.
• With Coexistence, the app stays on your phone. The same number rings there and answers in the panel — you neither change numbers nor lose history.

How to set this up for your team

1. Connect the number — signup happens inside Meta's own popup, and the account is born in your Meta Business, not ours.
2. Invite the team — each agent gets an email invite and signs in with their own login.
3. Define who can do what — broadcast, calls, exports: permissions are per person, not per account.
4. Leave the rest switched on — Kanban CRM, chatbot and AI already live in the same panel, on the same number.