How a WhatsApp queue management system works

A paper token tells people their number. It does not tell them when to come back. A WhatsApp queue system turns the token into a conversation: the customer books in a chat, hears as the queue moves, and is told exactly when and where to go. Here is how one works, from both sides of the counter.

What the customer experiences

1. They scan a QR code or tap a link and send “Book token”.
2. They pick a branch and a service from buttons.
3. They receive their token number, how many people are ahead and an estimated wait.
4. As the queue moves they receive a short update at sensible points.
5. When their turn is near, they are told to come to the branch.
6. When they are called, they receive “Please proceed to Counter 3”.
7. Afterwards they may get a thank-you and a one-tap rating.

Nothing to install, and they are free to sit in the car or run an errand in between.

What the system does

• Token service. Issues the next token for that branch and service, after checking opening hours and duplicates.
• Queue engine. Keeps the order of each queue and recalculates positions whenever anything changes.
• Counter app. Staff call next, recall, skip, transfer or complete.
• Live dashboard. Managers see waiting counts, average wait and counter status in real time.
• Notification worker. Decides who needs which message and when, and sends it through the WhatsApp Cloud API.
• Database and reports. Every token, call and message is stored for analysis.

Notify at the right moments, not at every one

The obvious design is to message every customer each time the queue moves. It is also the worst: a person ten places back would receive dozens of messages. A better rule is to notify at thresholds, such as when five, three and one people remain ahead, or when the estimated wait drops below a set number of minutes. That keeps messages meaningful, and keeps your WhatsApp quality rating healthy.

Estimating the wait

A fixed “five minutes per person” is wrong the day a complicated case arrives. A better estimate uses recent real service times for that counter and service, adjusted for how many counters are open. Present it as an estimate, and let it improve as the system gathers data.

How the 24-hour window affects the design

Because the customer starts the chat, a customer service window opens at that moment, and most visits end well inside 24 hours. Inside the window, updates can be free-form. We still send the critical alerts, such as “your turn is approaching” and “please proceed to Counter 3”, as approved templates, so they are delivered even in a long wait that outlasts the window. Templates are explained here.

The edge cases that decide whether it works

• No-shows: recall, hold for a few minutes, then skip or re-queue
• Priority tokens for elderly visitors, appointments or urgent cases
• Transfers between counters, and counters going on break
• A cut-off for the last token of the day
• Customers who cancel or book twice
• Customers who do not use WhatsApp, who still need a printed token or kiosk, in the same queue

Is WhatsApp the right channel?

For most branches and service counters in places where WhatsApp is the default way people message, yes. Where it is not, the same queue engine can send SMS or show a display board, and the WhatsApp layer becomes optional. The software behind the queue matters more than the channel in front of it.

See the WhatsApp queue management page for a sample conversation and the architecture, or discuss your own queue with us.