WhatsApp Queue Management: Tokens, Live Positions and “Your Turn” Alerts
Customers book a token in a chat, get updates as the queue moves, and are told exactly when and where to go. Waiting rooms empty out, and counters stay organised.
- Tokens booked in WhatsApp, no app to install
- Position updates only when they matter
- Staff dashboard, counter screens and reports
Sample implementation · fictional branch · not a client case study
Why queues frustrate everyone involved
A token on a piece of paper tells you your number. It does not tell you when to be back.
Crowded waiting areas
People stand or sit for hours because leaving feels like losing their place.
Customers who cannot step away
They miss lunch, work or a parking limit for fear of being skipped.
Staff answering “how long?”
The same question at the counter, all day, to people who are already frustrated.
No data on waits and no-shows
Nobody knows the real average wait, the busiest hour or how many tokens go unused.
How a WhatsApp token system works, step by step
Each step has two halves: what the customer sees in the chat, and what the system does to make it true.
- 01
Book a token
In the chat
The customer sends “Book token” and picks a branch and service from buttons.
In the system
The system checks opening hours, the service and duplicate bookings, then issues the next token in that branch’s queue.
- 02
Confirm
In the chat
A template confirms the token number, the people ahead and the estimated wait.
In the system
The estimate comes from recent real service times for that counter and service, not a fixed guess.
- 03
The queue moves
In the chat
Position updates arrive at sensible points, such as 5, 3 and 1 ahead, not on every change.
In the system
Each time a counter calls the next token, positions are recalculated and only the customers who cross a threshold are messaged.
- 04
Turn approaching
In the chat
“Your turn is approaching. Please be at the branch in the next 5 minutes.”
In the system
A threshold you set, in people ahead or in minutes, triggers it for exactly one customer at a time.
- 05
Token called
In the chat
“Token A-104: please proceed to Counter 3.”
In the system
The staff member presses “call next” on the counter screen; the message, the display board and the dashboard update together.
- 06
Completed
In the chat
A short thank-you and, if you want it, a one-tap rating.
In the system
The service time is recorded, so tomorrow’s estimates are a little more accurate than today’s.
The software that makes the messages true
WhatsApp is the front door. The queue itself is software: tokens, ordering, counters and real-time state.
Token service
Issues tokens per branch and service, with prefixes, daily resets and rules for priority tokens.
Queue engine
Holds the order of every queue, recalculates positions and keeps state consistent when two counters act at once.
Counter app
A simple screen for staff: call next, recall, skip, transfer to another counter, mark done.
Live dashboard
Waiting counts, average wait and counter status for managers, updated in real time over WebSockets.
Notification worker
Decides who needs which message, and when, then sends it through the WhatsApp Cloud API with retries and tracking.
Database and reports
Every token, call and message stored in PostgreSQL, so waits, no-shows and busy hours can be reported.
The cases a demo never shows
A queue works when it is boring on a bad day. These are the situations we design for before launch.
Designed for
- No-shows: recall, hold for a few minutes, then skip and re-queue
- Priority tokens for elderly visitors, appointments or urgent cases
- Transfers between counters and counters going on break
- A cut-off time for the last token of the day
- Customers who cancel, or try to book twice
- Switching branch after booking
- Language preference on every message
- Customers without WhatsApp: a printed token or kiosk, with the same queue
Anywhere people wait for a counter
- Clinics and hospitals
- Government and public-service counters
- Service centres
- Banks and financial branches
- Salons and spas
- Registration and check-in desks
What a typical build includes
- Token booking and queue messages on WhatsApp
- Token service, queue engine and counter screens
- Live staff and manager dashboards
- Optional display board and printed or kiosk tokens
- Reports on waits, service times and no-shows
What we need from you
- Branches, counters and services
- Opening hours and average service times
- Rules for priority, skips and cut-offs
- Languages your customers use
- Any system the queue must report to
WhatsApp queue management: your questions answered
Do customers need to install anything?
No. They only need WhatsApp, which they already have. They start the chat by scanning a QR code at the entrance, tapping a link or a button on your website, or messaging your number.
How is the estimated wait calculated?
From recent real service times for that counter and service, adjusted for how many counters are open. It improves as the system learns your patterns, and we tell customers it is an estimate.
Can staff override the queue?
Yes. Staff can call a specific token, recall, skip, move a customer to another counter or add a priority token. Every override is logged, and customers affected are messaged correctly.
What if a customer ignores the messages?
The system recalls the token, holds it for the period you choose and then skips it or re-queues it, according to your rule. The customer is told what happened.
Can it run across several branches?
Yes. Each branch has its own queues, counters and staff view, while head office sees all of them in one dashboard.
Is this a ready-made product?
No. It is a custom build, designed around your branches, services and rules, using patterns we have designed before. The conversation on this page is a sample implementation, not a customer case study.
Describe your queue. We will design the messages around it.
Tell us how many branches and counters you have, how people join the queue today and what goes wrong on a busy day.
Keep exploring
WhatsApp is a trademark of Meta Platforms, Inc. Stack Bridge Labs is an independent software company and is not affiliated with, endorsed by or sponsored by WhatsApp or Meta. Conversations, names, numbers and templates shown on this page are fictional examples.