Automatic distribution of conversations on WhatsApp: how it works

A automatic distribution of conversations on WhatsApp defines, without manual dispute, which attendant takes over each new conversation. There are two models: the round-robin, which rotates conversations in a fixed order between the team, and the catch-who-can, in which the queue is open and whoever clicks first responds. WhatsApp does not have this feature natively — it comes via extension, like Zapext's round-robin on the Plus plan, or via the official API. This guide shows you when to use each model and the fairness rules that make rotation really work.

The problem that distribution solves: ownerless conversation

WhatsApp multi-device connects up to 4 devices to the same number^[1] — which puts the entire team in the same inbox. But it connects people, it doesn't divide work: everyone sees all the conversations and none of them are responsible. The result appears in two opposing symptoms. Either two attendants respond to the same customer at the same time, or no one responds because each one thought the other was going. And the vacuum is expensive: leads responded to in the first hour are 7 times more likely to qualify than those who wait longer^[2]. Automatic distribution exists to eliminate exactly that gap between "the message arrived" and "someone is responsible for it."

What is round-robin?

Round-robin is the distribution in a circular relay: the first new conversation goes to attendant A, the second to B, the third to C — and the fourth goes back to A. The name comes from tournaments in which everyone plays against everyone else and from the scheduling of tasks in computing: each participant receives a turn in sequence, and when the list ends, it starts again from the beginning. In customer service, this means that every conversation starts with a defined owner, without anyone needing to decide anything.

Three practical caster effects:

• Volume justice. At the end of the day, each attendant received almost the same number of conversations — the division no longer depends on who shouts first.
• End of cherry-picking. Nobody chooses only the easy conversations (the customer who "just wants the price") and lets the difficult ones get old in the queue.
• Comparable basis for measurement. If everyone receives similar volume, the difference in results between attendants becomes management information, not noise.

The alternative model: catch-all (open queue)

In the open queue model, the new conversation is visible to the entire team and whoever is free brings it to themselves. It's the spontaneous model for any small team — and it has real merits: it doesn't require configuration, it absorbs spikes well (those who are free take more) and it allows the most experienced attendant to take on the most delicate case on their own initiative.

Costs appear with growth. First, the cherry-picking: laborious conversations are left waiting while quick ones disappear from the queue. Second, the invisible unequal burden: the quickest click agent accumulates the good customers, and no one notices until the commission is crooked. Third, the old vacuum: "those who can" are sometimes nobody, and the customer is left without an answer precisely in the model that promised agility.

Rodízio vs pega-que-pode: direct comparison

Criterion	Round-robin	Grab-who-can (open queue)
How the conversation gains ownership	Automatic, in relay	Manual, on the initiative of those who pull
Justice in charge	High — volume divided by default	Low — depends on team discipline
Vacuum risk	Low — every conversation has an owner upon entering	High — no one pulling is always possible
Risk of cherry-picking	None	Loud
Volume spikes	Distributes equally, even if someone is overloaded	Absorbs well — whoever is free takes more
Best case scenario	Team with similar functions and constant volume	Duo that talks to each other all the time, irregular volume

When to use each model

Adopt rotation when:

• the team has a similar function — everyone handles the same type of conversation;
• there is already a recurring conflict regarding "who responds" or complaints about unequal load;
• you want to measure performance per attendant on a fair basis of comparison;
• the volume of conversations is reasonably constant throughout the working day.

Stay on the safe side when:

• the team is a duo that works side by side and communicates all the time;
• availability varies greatly — the attendant also takes care of the cash register, production or delivery;
• each person takes care of a different matter (financial, support, sales). In this case, whoever organizes it is etiquette in the sorting + transfer to the person responsible — drawing a bill to the seller only generates a transfer.

How round-robin works at Zapext

At Zapext, round-robin is part of the Plus plan (R$59/month, up to 4 users on the same number, no cost per message). The basis is the official multi-device itself: each attendant connects WhatsApp Web to their computer, and the extension adds the team layer on top — without migrating numbers and without passing conversations through a third-party server, as the data is stored locally and encrypted. The flow in everyday life:

1. Customer calls on the company number and the conversation enters the new queue.
2. The rotation assigns the conversation with the next attendant in turn, in turns — the owner is visible to the entire team, and the “I thought it was up to you” ends.
3. Has the authority changed? Service transfer passes the conversation to the right colleague with the context together, without the customer repeating the story.
4. The manager monitors all in the shared CRM Kanban, with stage and source tags — each conversation is a card in the funnel.

The complete configuration step by step — from connecting users to dividing the queue — is in the guide multiservice on WhatsApp.

Rules of justice: what rotation cannot solve alone

Round-robin deals volume, no effort. Without four process rules agreed with the team, the best configured rotation still produces injustice:

1. Rotation only between those who are available

Anyone who goes out for lunch, a visit or a meeting lets you know and leaves that time. If the relay continues to count on the absentee, his conversations grow old in the queue — and the customer pays the bill. Signaled availability is a prerequisite, not a detail.

2. Equality of volume is not equality of effort

Ten 2-minute conversations don't weigh as much as ten one-hour negotiations. The rotation balances the input; real balance appears in service metrics reviewed per week: response time, closed conversations and open load per attendant. If someone is always drowning in the same volume as their colleagues, the problem is the type of conversation, not the quantity.

3. Transfer is a ticket, not a return

Transferring a conversation is about taking it to the right colleague with context — not returning it to the queue for the rotation to draw again. Conversation that returns to the queue restarts the customer's wait from scratch. Rule of thumb: transfer always has a named recipient and reason.

4. Public Rules, Weekly Review

The distribution rule needs to be written and visible to the team: who enters the rotation, how to signal absence, what is a valid reason for transfer. In the weekly metrics review, one of the items is precisely "is the distribution fair?" — and the answer may change as the team grows. The complete ritual is in the method of how to organize service on WhatsApp.

When automatic distribution is not the answer

Honesty before subscribing: if you serve alone, there's nothing to distribute — the free WhatsApp Business with tags will do the trick, and the rotation would be a paid feature that doesn't stand still. A well-matched duo, with low volume, also lives well in manual catch-up. At the other extreme, operations with 5 or more simultaneous agents, formal SLA or routing by skill and department do better with the official WhatsApp Business API and a platform with advanced queues — Zapext serves up to 4 users on Plus and does not replace this infrastructure. The complete overview of the three ways of operating as a team is in multiple agents on the same WhatsApp.

For the team of 2 to 4 people stumbling across the same inbox, the sequence is simple: define the model (rotation for similar functions, open queue for matched pairs), combine the four fairness rules and activate distribution. The guide to multiservice on WhatsApp shows the complete configuration — and Plus has a 7-day guarantee to test the rotation with real conversations from your team.

Sources

1. [1] About multi-device beta — WhatsApp Help Center — WhatsApp (2024). accessed 2026-05-19.
2. [2] The Short Life of Online Sales Leads — Harvard Business Review (2011-03). accessed 2026-05-19.