Complete guide to having multiple people handle the same number without stepping on each other

The real problem of handling a WhatsApp among several people

Handling the same WhatsApp number among several people seems easy until what always happens happens: two operators answer the same query, a message goes unanswered because each one thought the other was answering it, and the customer ends up talking to three different people who repeat the same thing to them. The problem is not the tool: it is that there is no method. This guide organizes the topic from start to finish: what roles are needed, how the work is divided, how to transfer a conversation without losing context, and how to calculate how many people you need based on the volume of messages you receive.

Why handling a WhatsApp with several people fails

Regular WhatsApp was not designed for teams. When several people log in with the same number on their phones, four structural problems appear:

• There is no conversation status: no one knows if the message has already been answered, who answered it, or if it is still pending.
• There is no assignment: two people can be writing the same response at the same time, and the customer receives two messages that overlap.
• There is no shared real-time history: if an operator responds from their phone, the other does not see it until they refresh, and sometimes not even then.
• There is no way to measure: without response time metrics or conversations per operator, you do not know if the team is enough or if support is falling behind.

The technical solution has existed for years: Meta's official WhatsApp API allows multiple agents to access the same shared inbox, where each conversation has a status (new, in progress, resolved) and an owner. But the tool alone is not enough: without clear rules for distribution and transfer, the team still steps on each other. This guide covers both parts.

The three roles every team that handles WhatsApp needs

Before thinking about tools, define who does what. In small teams (two or three people), roles are combined, but the function has to be assigned. These are the three minimum roles:

The most common mistake is not assigning a supervisor. Without someone watching the general inbox, conversations that no one took remain there until the customer complains. The supervisor doesn't have to read everything: they have to see the dashboard and spot what's stuck.

The golden rules to avoid stepping on each other

These rules work with any shared inbox tool (Wando, other software with Meta's official API, or even an Excel if you're just starting out). They are not configuration: they are team agreements.

• One conversation, one owner: the first operator who takes it finishes it. If they need help, they ask for help, but they don't let go of it.
• No one responds to a conversation that already has an assigned owner, unless the supervisor reassigns it.
• Every conversation must go through a status: new, in progress, pending customer, resolved. If you don't know its status, don't touch it.
• Handoffs always include context: you don't send the number, you send a summary of what was discussed and what still needs to be resolved.
• When in doubt, the supervisor decides. If two operators stepped on each other, the supervisor defines who continues, and the other steps back without writing anything else.

How to size the team: the table that tells you how many people you need

The calculation that almost no one does is how many operators are needed to handle the real volume of messages. Without that number, either you have too many people (wasted cost) or too few (customers waiting for hours). The formula is simple:

1. 1Count the incoming messages of a typical day. Not the outgoing ones: the ones your number receives.
2. 2Multiply by 2: each incoming message generates, on average, one reply and sometimes a couple of back-and-forths. That is your total of messages to write per day.
3. 3Estimate how many messages an operator can write per hour. With templates and quick replies, an experienced operator writes between 20 and 30 messages per hour. Without templates, it drops to 10 or 15.
4. 4Divide the total messages per day by the messages per hour. That gives you the man-hours needed.
5. 5Compare against the hours you have: if your team covers 8 hours and the calculation gives 12, you need two people during peak times or automate part of the response.

The table assumes that the whole team works 8 hours straight. If your service is 12 hours, double the numbers. If you have marked peaks (for example, everything arrives in the morning), the average is not enough: size for the peak, not for the day.

How to hand over a conversation without losing context

The handover is the moment where the most information is lost. An operator going to lunch, a specialist receiving a referral, a shift change: in all these cases the conversation changes hands. If the person receiving it does not know what happened before, the customer repeats everything from scratch and the experience falls apart.

• Summarize in one line: what the customer asked, what was answered, what is pending. Example: 'Asked for the Pro plan price, I sent the pricing link, need confirmation on whether they want invoice A or B'.
• Leave the conversation in 'in progress' status with the new responsible person assigned. If there is no responsible person, the supervisor assigns it before the operator leaves.
• If the handover is due to a schedule change, do it 15 minutes before the outgoing person leaves. Not at the last minute: the incoming person needs time to read the context.
• If the customer asks 'Who am I talking to?', respond with the team name, not with proper names. This way the handover does not confuse the customer.

What the tool does and what the team does

A shared inbox with the official WhatsApp API (like the one offered by Wando, or other similar ones) solves the technical part: everyone sees the same messages, each conversation has a status and a responsible person, and the history is saved. But the tool does not define who takes each conversation or when it is handed over: that is decided by the team.

The division of tasks is clear. The tool has to ensure that there are no duplicate messages (because the conversation has an owner), that the history is available to everyone (so that handovers don't depend on anyone's memory), and that the supervisor can see the overall board (to detect what's hanging). The team has to enforce the rules: who takes, who refers, when to hand over, and what information is passed.

Common mistakes and how to avoid them

These are the mistakes that repeat in all teams that start handling WhatsApp among several people. Each one has its solution:

What to do first: the 5-step startup plan

If you're about to go from handling alone to handling among several people, don't try to do everything on the first day. This is the order that works:

1. 1Define the roles: who operates, who supervises, who is the specialist if needed. Even if there are two people, assign the supervisor role.
2. 2Count the messages from one week and do the sizing calculation. If you're short-handed, resolve it before starting.
3. 3Write the rules in a visible document: one conversation one owner, mandatory states, handover with summary.
4. 4Configure the tool: shared inbox, states, labels for query types, auto-replies by schedule.
5. 5Do a trial week with the full team, reviewing each day the cases of overlaps and hangings. Adjust the rules based on what you see.

Questions that remain open

There are two topics that this guide does not cover in depth because they depend on your context, but it is worth keeping them on your radar. The first is measurement: once the team is working, you need to look at first response time and conversations per operator to know if the method holds up. The second is automation: if volume grows, templates and automatic responses for frequently asked questions free up hours without adding people.

With the method in this guide, the sizing and handoff rules, handling a WhatsApp among several people stops being a source of overlaps and angry customers. The rest is fine-tuning.