WhatsApp service queue: how to set up step by step

To assemble a WhatsApp service queue, you need three pieces: status tags (New, In Service, Waiting for Customer, Completed), the rule that every conversation is assigned a status and owner as soon as it arrives, and a clear order of service — by arrival, with priority exceptions written in. Mirror statuses into Kanban columns to see the entire queue at once and measure first response time every week. This guide shows you how to put it all together, with and without tools.

Inbox is not a queue

WhatsApp conversation list sorted by last message received — not for those who have been waiting the longest. The customer who called at 9am and was not answered goes down the list as new messages arrive, until it disappears from the screen. Who sends a "??" climbs to the top. Result: those who insist are served, those who wait politely are forgotten — the opposite of what a queue should do.

Real queue has two properties that the inbox does not: order by waiting time (whoever arrived first appears first) and visible status (take a look and see what has already been answered, what is in progress and what has finished). This post delves into a specific step of the service organization method in 7 steps: how to build exactly this queue.

The statuses that form the queue

The backbone is three statuses — New → In Service → Completed — another quarter that avoids the most common distortion:

Status	What does it mean	When you enter	When it comes out
New	Customer called and no one answered yet	Every new conversation, without exception	In the first human response
In Service	Active conversation, with defined owner	When answered	When it resolves or when the ball passes to the customer
Waiting for Customer	You answered; the next action is his	After sending a quote, question or proposal	When the customer responds (returns to In Service) or after follow-up with no response
Finished	Demand resolved and conversation closed	Upon completion of the service	If the customer returns, it becomes New again

The status Waiting for Customer exists so the In Service column doesn't become a deposit: without it, conversations in which the ball is in the customer's court mix with those that are stopped because of you — and you lose the ability to see your own delay. Resist creating ten statuses right away; the complete taxonomy of tags (origin, product, priority) is in the guide stickers on WhatsApp Business, but the queue works with these four.

How to assemble the queue without tools (free)

You can operate this queue just with what WhatsApp Business offers:

1. Create the four status tags in the WhatsApp Business app (Business Tools → Tags).
2. Adopt the screening rule: every incoming conversation gets the New label before anything else — even if you're not going to respond right now. It is the act of "removing the password".
3. Scan at fixed times (e.g. every hour): filter by the New tag and respond from the oldest conversation to the newest — never from the most recent backwards.
4. Update status when leaving the conversation. Did you respond? In Service. Did you send a proposal? Waiting for Customer. Did you solve it? Finished. Etiquetteless conversation at the end of the day is the only serious infraction of the system.

Honesty: for those who work alone, with a few dozen conversations a day, this manual setup does the trick — and it costs nothing. The limits appear with volume and team: the label filter does not order by waiting time (you need to scroll and judge by eye), there is no conversation owner, and the discipline of labeling is 100% manual — on a busy day, it is the first thing the team abandons.

How to set up the queue with Kanban

The Kanban board is the same queue, now visible in full: each column is a status, each card is a customer, and moving the column card updates the status — a gesture instead of menu tags. The practical difference is in the overall view: instead of filtering tag by tag, you look and see eight cards accumulated in New (growing queue), three stuck in In Service since yesterday (your delay) and twelve in Waiting for Customer (follow-up time).

No CRM Kanban by Zapext, the table runs within WhatsApp Web itself: the conversation becomes a card, dragging between columns changes the stage, and the data is stored locally and encrypted on your computer — without a parallel system for typing twice. For the queue, this changes the cost of discipline: keeping the status updated stops being an extra task and becomes the natural way of working.

Priority rules: who is served first

The default rule for any queue is order of arrival — and it should apply in 90% of cases. But every business has legitimate exceptions, and the difference between a professional line and a mess is that the exceptions are written before, not decided in the heat of the moment:

• Priority 1 — ongoing conversation that came back: customer Waiting Customer who responded goes ahead to new conversation. Warm service is worth more than new service — letting a negotiation cool down to “clear the queue” costs sales.
• Priority 2 — urgency defined by the business: list in writing what is urgent in your context (paid order with delivery problem, customer at the counter waiting, deadline of the day). What is not on the list is not urgent.
• Priority 3 — active campaign lead: whoever arrives from an ad that is running now cools down in hours; mark with origin label and serve within the first hour.
• Everything else: first come, first served, no exceptions. "Who shouts the loudest" is not a criterion — a customer who sends ten messages in a row does not get ahead of someone who has been waiting in silence for the longest time.

Queue with team: single owner, rotation and transfer

WhatsApp allows you to connect up to 4 devices to the same number^[1], so the entire team can see the same queue in the browser. What the native feature doesn't solve is the classic shared queue problem: two attendants catch the same conversation, or each thinks the other caught it — and no one catches it. Three rules close this loophole:

• Sole owner: card in In Service has a visible person in charge. Conversation without owner returns to Novo.
• Automatic round-robin: new conversations are distributed in turns, instead of everyone "fishing" for the easy ones and leaving the difficult ones to age in the queue.
• Transfer with context: changed jurisdiction, the conversation goes to the right colleague with the history together — the customer does not go back to the end of the line or start the story over again.

At Zapext, round-robin and service transfer are part of the Plus plan (R$59/month, up to 4 users, no cost per message). The complete setup for team operation — from connecting users to distribution — is in the multiservice on WhatsApp.

What to measure: first response time and two more numbers

1. First Response Time (TPR): from the moment the conversation goes New until the first human response. It is the metric that validates the entire queue: leads responded within an hour are 7 times more likely to qualify than those who wait longer^[2]. Target reference: less than 5 minutes within working hours.
2. Queue reset at the end of the day: how many conversations sleep in Novo. The goal is zero — if there is a queue every day for the same shift, the problem is people allocation, not effort.
3. Age of cards by column: conversation stopped for more than 2 days in In Service is your delay; there are more than 3 in Awaiting Customer is forgotten follow-up. The accumulation points to the bottleneck of the week without a report.

Half an hour of weekly review is enough. The eight complete service metrics, with goals by stage, are in the guide service metrics on WhatsApp.

Errors that dismantle the queue in a week

• Too Much Status: more than five or six columns and no one knows where to move the card — the queue dies of ambiguity.
• Move without responding: dragging to In Service without sending a message only makes up the metric; the customer continues to wait.
• Informal priority: without written rules, everything becomes "urgent" and the order of arrival ceases to exist.
• Finished that does not finish: ending a conversation without resolving it generates reopening — and reopening enters as New, artificially inflating the queue.
• Do not measure: queue without measured first response time regresses to inbox in one month.

When this setup is not enough

If you answer alone and receive few conversations per day, WhatsApp Business's free native tags will do the trick — go back to the Kanban version when the volume gets louder. At the other extreme, operations with 5 or more simultaneous agents, formal SLA or transactional chatbot at scale do better with platforms based on the official WhatsApp API: they cost more and charge per conversation, but scale beyond what an extension on WhatsApp Web proposes to do — and in this scenario Zapext is not the right choice.

For the SME between these two extremes, the queue with status tags and Kanban is the pattern that solves the problem: Zapext sets up the columns, rotation and transfer on your current WhatsApp Web, starting at R$29/month, with a 7-day guarantee — 3,000+ companies operate like this. Start today by creating the four statuses and measuring your first response time; If the team has grown, the next step is to multi-service on the same number.

Sources

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