The moment is always the same: the company hires a second salesperson and discovers that WhatsApp was not designed for two people. From there, there are four possible paths — three of them create a new problem to solve the old one. It's worth understanding all four before choosing.
In this article
- Method 1: the company phone on the desk
- Method 2: linked devices
- Method 3: one number per salesperson
- Method 4: shared inbox
- The four side by side
- How conversations are distributed
- The five rules that make the team coexist
- How many agents do you really need
- Migration in 7 days, without losing customers
- Frequently asked questions
Method 1: the company phone on the desk
This is the oldest and still the most common solution. One device stays at reception or on the sales desk, and whoever is free answers.
It works while volume is low and people are in the same room. It breaks down for three reasons: only one person can type at a time, no one can work outside the office, and there is no record of who attended whom. When the customer complains about something agreed upon, there is no way to know who they spoke to. This method causes the most embarrassment of having to ask the customer what the company promised.
Method 2: linked devices
WhatsApp allows linking other devices and computers to the same number. Many people discover this and think they have solved multi-agent support. It solves half the problem — the easy half.
What improves: more than one person can access at the same time, each from their own computer. What remains broken, and what matters:
- Everyone sees everything. There is no division of accounts. Salesperson A opens the conversation that salesperson B is handling and replies over it.
- There is no "owner" of the conversation. Two responses to the same customer with different information is routine.
- There are no internal notes. Everything written is visible to the customer.
- There is no measurement. No reports on how many conversations each handled, response times, or sales conversions.
- The number remains tied to one phone. If the main device runs out of battery or is reset, the operation stops.
It is an acceptable temporary fix for two people who talk all the time. With three or more, the rework costs more than the solution.
Method 3: one number per salesperson
This seems like the obvious solution and is the most expensive in the long run. Each salesperson has their own SIM card, their own WhatsApp Business, their own client list.
In the short term, it works well: no one interferes with anyone, each takes care of their own clients. Problems appear in chronological order:
- The customer doesn’t know whom to write to. They saved the number of the salesperson who attended them in January, who no longer works there.
- The company has no consolidated view. To know how the month went, you have to ask each salesperson — and no one reports against themselves.
- Marketing becomes impossible to measure. If the ad directs to three different numbers, there is no way to know what generated what.
- The client list is not the company’s. This is the real cost. When the salesperson leaves, they take the SIM card or simply take the contacts, and within two weeks they are selling to the same base — at a competitor or on their own. This has happened to too many companies to be treated as a hypothetical risk.
Quick test: if your best salesperson resigned today, how many customers could you continue serving tomorrow without relying on their goodwill? If the answer is "few," the problem is not the salesperson — it’s the architecture.
Method 4: shared inbox
This is the model used by customer service systems and WhatsApp CRMs. One number — the one the company already advertises — connected to a dashboard. Each agent logs in with their own credentials and sees only what is assigned to them.
What changes concretely:
- Assignment. Each conversation has an owner. Those who are not owners do not respond by mistake, and the system signals when someone is already typing there.
- Transfer. The salesperson goes on vacation and passes the client list in two clicks, with the entire history.
- Internal notes. "Customer already asked for a discount twice, do not exceed 10%" is recorded in the conversation and never seen by the customer.
- Company history. It leaves someone’s phone and becomes a business asset.
- Measurement. First response time, conversations per agent, conversion per salesperson — numbers, not opinions.
- Permissions. Salesperson sees their own client list; manager sees everything; data export is restricted to those you designate.
And it’s worth debunking a myth: you don’t need to change your number or migrate to the official Meta API to have this. Connection via QR Code already delivers multi-agent support while keeping the number you have been advertising for years. The official API solves another problem — high volume of company-initiated messages and verification — not the issue of having a team attending together.
Continue reading for free
Fill out once and unlock this and all other blog articles. We don’t charge anything — we just want to know who we are writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
The four side by side
| Phone on the desk | Linked devices | One number per salesperson | Shared inbox | |
|---|---|---|---|---|
| Answer at the same time | No | Yes | Yes | Yes |
| Account division | No | No | Yes | Yes |
| Only one number advertised | Yes | Yes | No | Yes |
| History stays with the company | Partial | Partial | No | Yes |
| Internal notes | No | No | No | Yes |
| Report per salesperson | No | No | Manual | Yes |
| Works outside the office | No | Yes | Yes | Yes |
| Cost | Zero | Zero | SIM cards and devices | Monthly fee |
How conversations are distributed
Having everyone on the same dashboard alone doesn’t solve it: someone needs to decide who attends whom. There are three logics, and the choice changes team behavior.
Rotation. New conversations are distributed in order, one per agent. It’s the fairest and easiest to explain to the team. Note: it ignores if the salesperson already has ten open conversations.
Queue. Conversations stay in a common pool and whoever is free picks the next one. It makes better use of capacity and reduces wait times but requires a mature team — otherwise everyone picks only what seems easy.
Manual or by rule. Someone triages and forwards, or a rule decides by origin: those from a product ad go to that product’s specialist, existing customers go directly to their account salesperson. It’s the most efficient and requires the most design.
One caution that applies to all three: a customer who has already spoken to the company should return to the person who attended them. Starting over with someone else is the fastest way to annoy someone who was almost buying.
The five rules that make the team coexist
The tool alone doesn’t organize the team. These five combinations solve almost all friction that appears in the first weeks:
- Only the owner of the conversation responds. If help is needed, use internal notes and call the responsible person — don’t write to the customer.
- Maximum first response time. Set a number and make it visible. Fifteen minutes during business hours is a good start. What isn’t measured isn’t fulfilled.
- Conversations without customer response for X days return to the queue or become a follow-up task. Nothing can be left idle by forgetfulness.
- Every conversation has a funnel stage. Without this, the dashboard becomes just a list of messages again.
- Important agreements go to internal notes, not memory. Agreed discount, promised deadline, customer restrictions.
How many agents do you really need
Before hiring more people, it’s worth checking if the problem is capacity or organization. The calculation is straightforward — use your own numbers instead of the example:
Example — capacity of one agent
In the example, 45 ÷ 28 = 1.6 — that is, two agents with room to spare. If your company already has four people attending this same volume and there are still customers without response, the bottleneck is not people: it’s process.
Migration in 7 days, without losing customers
The biggest fear of those who postpone this change is going offline in the middle of the month. A short roadmap to avoid this:
Day 1 — Choose the number. Use the one the company already advertises, the one on Google My Business, the website, and ads. Don’t debut a new number: you lose all the history of those who already have you saved.
Day 2 — Design the funnel before connecting. Write the real stages of your process on a sheet. Five or six are enough. A tool configured with another company’s funnel is never used.
Day 3 — Connect and run with only one person. A single agent, a whole day. This is when automatic message adjustments, schedule, and missing stages appear.
Day 4 — Bring in the rest of the team. One hour of training solves it. Agree on the five rules from the previous topic on the same day, in writing.
Day 5 — Register the active client list. Don’t try to import five years of contacts. Bring those currently negotiating and those who bought in the last six months. The rest will come naturally as they contact you again.
Days 6 and 7 — Turn off the old shortcuts. As long as the phone on the desk remains on, half the team will keep using it. Cut the old path, or the migration never ends.
If you use multiple numbers today: don’t turn off the old ones all at once. Keep them for 60 to 90 days with an automatic message pointing to the company’s official number, and notify the active base there. After that, retire them.
Frequently asked questions
Is it possible to have multiple agents on the same WhatsApp number?
Yes, but the common app was not made for this: linked devices show everything to everyone, without conversation division or control of who responds to what. For team support, a shared inbox with login per agent is needed.
Should each salesperson have their own number?
It is not recommended. The customer doesn’t know which number to write to, the company can’t measure anything consolidated, and when the salesperson leaves, their client list goes with them.
How to prevent two agents from responding to the same customer?
With assignment: each conversation has a responsible person and the system shows when someone else is already typing there. Without this, duplicate responses are a matter of time.
Do I need the official Meta API to have multi-agent support?
No. Connection via QR Code already allows multiple agents on the same number, keeping the number the company already advertises and without Meta message costs. The official API makes sense for high volumes of company-initiated messages or when official verification is sought.
Can agents work from their phones?
Yes. The shared inbox works in the browser, so each person accesses from a computer or their own phone — without the number being installed on their device.
Put the entire team on the number you already use
Connection via QR Code or the official Meta API, with conversation division, funnel, and report per salesperson on the same dashboard.