What is a queue management system, and how does a token system work?
A queue management system is software, sometimes with hardware, that turns a physical line into an ordered list of numbered tokens. Visitors take a token, wait wherever is comfortable, and are called to a specific counter when it is their turn.
The flow has five steps. First, issue: the visitor picks a service and receives a token number, from a kiosk, a QR code, WhatsApp or the reception desk. Second, waiting: a TV display shows the numbers being served and, often, the next few in line. Third, calling: a staff member presses "next" on their device, and the system chooses the right token for that counter, shows it on the TV and announces it aloud. Fourth, service: the staff member marks the token served, skipped or transferred. Fifth, reporting: every timestamp is stored, so you can see how long people waited and how long each service took.
The benefits are practical rather than glamorous. Fewer arguments about who came first. Staff who are not interrupted every two minutes with "how long?". A calmer waiting area, because people can sit, step out or keep an eye on their phone. And, for the owner or branch manager, real numbers about peak hours and slow counters instead of guesses.
- Clinics and diagnostic centres: doctor-wise queues, sample collection, report counters
- Banks and financial offices: cash, accounts, loans and enquiries at separate counters
- Service centres: vehicle, mobile phone and appliance intake and delivery
- Government and corporate offices: document submission, certificates, HR and admin desks
Hardware or software-only: which queue management system setup do you need?
If most visitors carry smartphones and you already have a TV in the waiting area, a software-only queue management system is enough: QR or WhatsApp tokens, a display page on the TV and a counter app on staff phones. Add a kiosk and printer only when many visitors cannot or will not use their own phones.
The hardware question is really about who your visitors are. At a city dental or skin clinic, almost everyone scans a QR code happily. At a bank branch in a small town, at a government office, or at a hospital OPD with many elderly patients, a printed slip from a kiosk or the reception desk is kinder and faster. Many places use both: QR for those who prefer it, and a tablet kiosk with a small thermal printer for everyone else.
Whatever you choose, the hardware should be ordinary and replaceable. Any smart TV with a browser, or a plain TV with an Android TV box, can run the display. A mid-range Android tablet in a floor stand can be the kiosk. A USB or Bluetooth thermal receipt printer prints the slips. Staff can call tokens from their own phone, a small tablet or the counter PC. We do not sell or install hardware; you buy it from any shop, which keeps its cost visible and its warranty with you.
Proprietary keypads and dedicated token displays still have a place where wiring and simplicity matter more than data, but they rarely connect to WhatsApp, apps or reports.
Token issue by kiosk: touch screen, printer and walk-ins
A kiosk gives every walk-in a token without staff involvement: the visitor taps a service, optionally enters a mobile number, and receives a printed slip with token number, service, time and approximate wait.
We design kiosk screens for people who have never seen one before. Big buttons with icons, Hindi and English labels side by side (or another local language you provide), no more than two taps to a token, and a timeout that returns to the home screen if someone walks away. The mobile number step is optional but useful: with it, the visitor also gets a WhatsApp or SMS alert when their turn approaches.
The kiosk runs as a locked-down app or full-screen browser page on an Android tablet, so staff cannot accidentally close it and visitors cannot wander into settings. If the internet drops, the kiosk keeps issuing tokens from a local sequence and syncs when the connection returns, so the queue never stops because of the router. Printers are the most common point of failure, so the screen shows the token number large enough to photograph if the printer runs out of paper.
For a clinic, the kiosk can ask "new patient or follow-up?"; for a service centre, "drop-off, pick-up or enquiry?". Each answer sends the token to a different queue.
QR code tokens: joining the queue from the visitor's own phone
QR tokens let a visitor scan a code on a standee or the door, pick a service on a simple web page, and get a token on their phone with a live position in the queue. There is no app to install and no hardware to buy beyond a printed QR code.
The token page updates itself: "You are token B-17. 4 people ahead of you. Counter 2 is serving B-13." When the visitor's number is called, the page changes colour, vibrates where the phone allows and shows the counter to go to. Visitors who close the page can reopen it from a link sent by WhatsApp or SMS if they gave a number.
A QR queue can also start before the visitor arrives. Put the same link on your Google Business Profile or website, and people can join the queue from home, arriving just in time. That works well for service centres and clinics with predictable service times; for banks and government offices, you may prefer to allow remote joining only within a set distance or time window, so tokens are not hoarded.
The main risk with QR tokens is fake or duplicate entries. Simple rules handle most of it: one active token per mobile number per service, an OTP where abuse is likely, and automatic expiry for tokens that are called and skipped more than once.
How do WhatsApp tokens work in a queue system?
A visitor sends a message such as "Hi" or "token" to your business WhatsApp number, picks a service from a short menu, and receives a token number and live position in the chat. Later messages tell them when their turn is near and which counter to go to.
This runs on the official WhatsApp Business Platform, with your own business account and number, never on unofficial tools that risk the number being blocked. Meta's pricing documentation says it moved to per-message pricing on 1 July 2025, that service conversations have been free since 1 November 2024, and that utility templates delivered within an open customer service window are free. Because a WhatsApp token starts with the visitor messaging you, most of the queue conversation usually falls inside that window, which keeps messaging costs low. Alerts sent after the window closes use paid templates at Meta's rates.
WhatsApp tokens suit places where people already message the business: clinics, salons, service centres, coaching offices. They are less suited to high-volume counters where hundreds of people arrive in one hour, where a kiosk and QR code spread the load better. For a deeper look at WhatsApp flows, see our WhatsApp chatbot page.
What the chat can show
Token number, service chosen, people ahead, estimated wait, the counter when called, and a cancel option so abandoned tokens do not slow the queue.
Languages
Menus and messages in English, Hindi or another language you supply and approve. Template messages are submitted to Meta for approval in each language used.
TV display with Hindi and English voice calling
The display is a full-screen web page on a TV that shows now-serving tokens per counter, the next few in line and optional notices, and plays a voice announcement for each call, such as "Token number B-17, counter number 2" in Hindi and then English.
The display page runs on any smart TV browser or an Android TV box, connects to the queue in real time and updates within a second or two of a staff member pressing "next". Layout is designed for reading from across a room: high contrast, large numerals, the latest call highlighted and a short chime before each announcement. The lower part of the screen can rotate your own notices, service timings or health messages.
Voice needs more care than people expect. Text-to-speech engines built into browsers and TVs vary by device, and not every device has a good Hindi voice installed. For consistent results the build can use short recorded clips instead: "token number", each digit or number, "counter number", and each counter name, recorded once in Hindi and English (by a person you choose or generated once with a quality speech service) and stitched together at call time. The announcement then sounds the same on every TV and never mispronounces a counter name.
Large waiting halls may need two or more displays, each showing different services. A doctor's cabin can have its own small screen showing just that doctor's queue.
Multi-counter routing: services, counters, priorities and transfers
Routing decides which token a counter gets when its staff press "next". In a good queue management system it follows simple, visible rules: which services each counter handles, which tokens have priority, and what happens when a token moves between counters.
Each service gets its own letter series (A for cash, B for accounts, C for loans, for example) and each counter is mapped to one or more services. A counter handling two services can take them in strict arrival order or give one service preference. Priority tokens for senior citizens, persons with disabilities or pregnant women can be issued at the kiosk or by staff and inserted according to a rule you set, rather than jumping to the front unpredictably.
Transfers need the most thought. A visitor served at the enquiry counter who then needs the loans desk should not start again at the back. The counter app lets staff transfer a token with a note, and the token enters the new queue at a position you decide, often at the front or after a fixed number of tokens.
Staff can also pause a counter for a break, recall a token that did not come forward, or mark it as a no-show after a set number of calls. Every action is logged with the time and the staff member, which is what makes the analytics trustworthy.
“Your turn” alerts that empty the waiting room
"Your turn" alerts tell a visitor, by WhatsApp or SMS, when they are a few tokens away, so they can wait in their car, a nearby café or at home instead of in a crowded room. It turns waiting time back into the visitor's own time.
The trigger is configurable: when the visitor is three tokens away, or when their estimated wait drops below ten minutes, or both. A second message goes out when the token is called, naming the counter. If the visitor does not arrive within a set time, the token is skipped and can be recalled by staff when the person turns up.
For clinics, alerts can also carry instructions: "please bring your previous reports" or "fasting sample: please do not eat before your turn". For service centres, a message can say "your vehicle is ready at delivery counter 3". The content is your choice, written in the languages your visitors read.
Estimated wait times are calculated from recent service times at the counters serving that queue, not from a fixed guess. They improve as data builds up, and the system avoids promising precision it does not have by showing ranges rather than exact minutes when the queue is volatile.
What wait-time numbers should a queue manager watch?
Watch four numbers: average wait time, average service time, no-show rate and tokens per hour, each broken down by service, counter and time of day. Together they tell you when to add staff, which counters are slow and whether visitors are giving up.
Wait time runs from token issue to call; service time runs from call to completion. A long wait with short service times means too few counters open at peak hours. A normal wait with long service times at one counter points to training, missing documents or a complex service that deserves its own queue. No-shows rising in the afternoon may mean people are leaving because they cannot see how long they have left.
Reports can be daily summaries on the manager's phone, weekly heat maps of tokens by hour and weekday, and monthly comparisons between branches. For banks and multi-branch service networks, a head-office view compares branches on the same measures. Exports go to Excel or your own dashboard.
Keep the numbers honest. If staff mark tokens served in bulk at the end of the day, service times become meaningless, so the counter app is designed to make the right action the easiest one.
Queue management system for clinics, labs and hospital OPDs
In healthcare, a queue management system usually runs one queue per doctor plus shared queues for registration, billing, sample collection and reports. Tokens can be issued at reception or the kiosk and linked to the patient's appointment if you have one.
Doctor-wise queues solve the most common complaint in multi-doctor clinics: patients for a busy doctor mixing with patients for a quiet one. Each doctor's cabin or chamber can show its own queue on a small screen, and the doctor or assistant calls the next patient from a tablet. Appointments and walk-ins are merged by rule, for example alternating, so neither group feels cheated.
Diagnostic centres and labs benefit from queues per stage: registration, billing, sample collection, radiology, report delivery. A patient moves through each with the same token, and the system shows where the bottleneck is. If your clinic already has software, the queue can take patient names and doctor assignments from it; our clinic management software and pathology lab software pages cover those systems. Dental practices with chair-based diaries are covered separately under dental clinic software.
Queue management system for banks, service centres and offices
Banks, service centres and offices use a queue management system mainly for routing: getting each visitor to the right counter the first time and moving them between counters without losing their place.
Bank branches and financial offices typically separate cash, account services, loans and enquiries, with priority tokens for senior citizens. Branch managers care about peak-hour staffing and the share of visitors who leave without being served. Head offices want a comparison across branches. If a bank's IT policy requires on-premise hosting or specific security reviews, that has to be clarified before quoting, because it changes how the system is deployed.
Vehicle, mobile phone and appliance service centres split intake, estimate approval, delivery and billing. "Your turn" alerts shine here, because customers can leave and come back when their device or vehicle is ready. Government and corporate offices, such as certificate counters, document submission desks or HR helpdesks, often need printed tokens, Hindi and a regional language, and strict first-come order with visible rules. For offices tracking who enters the building rather than who is waiting for service, a visitor management system is the better fit; for internal support queues, see helpdesk ticketing.
How much does a queue management system cost in India?
A custom queue management system from BtechWaleTech starts at ₹60,000 (about US$900) for the software. Hardware is separate and bought by you, and a software-only setup on your existing TV and staff phones keeps that part close to zero.
Think of the total in three parts. Software: the one-time build, which depends on token channels, voice languages, routing complexity, integrations and reports. Hardware: whatever you choose to buy, such as a smart TV or Android TV box per display, a tablet and floor stand for each kiosk, a thermal printer per kiosk, and tablets for counters if staff will not use phones or PCs. Running costs: cloud hosting, WhatsApp template messages at Meta's rates and SMS if you use it, all billed by those providers directly.
Ready-made token displays and subscription apps are real alternatives, with quotes that vary widely by features, counters and branches. A standalone display is simplest when you need nothing beyond numbers on a screen. A subscription app is quick if its routing and alerts fit. An owned system makes sense when you want your own channels, languages, reports and data, or have enough branches that per-counter fees add up. After two free months, maintenance from ₹8,000/mo is optional.
How long does it take to set up a custom token system?
A first version usually takes 6 to 12 weeks to build, and physical setup on site takes an afternoon once your hardware has arrived, because the displays and kiosks are simply devices opening your system.
A common sequence: week one to agree services, counters, routing rules, languages and channels, and to list hardware for you to buy. Weeks two to four for the core queue, counter app and TV display, tested with dummy tokens. Weeks four to six for kiosk and QR token issue, voice clips and printing. Weeks six to nine for WhatsApp tokens and "your turn" alerts, which also depend on Meta approving your message templates. Weeks eight to twelve for analytics, multi-branch settings and any integration with clinic or billing software.
Before go-live, run the system in parallel for a few days: tokens issued, calls made, but staff still watching the physical line. That catches confusing kiosk labels and routing mistakes before visitors depend on them. Setup of TVs and kiosks is done by you or your local IT person following our written steps and a video call, since we do not visit sites.
Who owns the queue software, and how is visitor data handled?
You own the code, the hosting account, the WhatsApp Business account and all the queue data. At handover you receive admin access, deployment notes and a list of every paid service with who bills it, and you can move to another developer whenever you like.
A queue system collects less personal data than most software, but mobile numbers and sometimes names are still personal data under the Digital Personal Data Protection Act, 2023, whose Rules MeitY notified on 14 November 2025 with obligations phased in. The system supports your obligations by asking only for what is needed (a mobile number only if the visitor wants alerts), showing a short notice at the kiosk and on the QR page, deleting numbers after a period you set while keeping anonymous timing data for reports, and restricting who can see visitor details. Your lawyer should review the notice wording; compliance remains your responsibility.
Displays should never show full names or phone numbers. Token numbers and counter names are enough, and in clinics, the display must not reveal which doctor or department a named patient is visiting. Accessibility deserves the same care: large type on displays, audio announcements for people who cannot see the screen, visual calls for people who cannot hear, and priority rules for those who cannot wait long. Our general terms set out ownership and payment conditions.
Worked example: a two-wheeler service centre in Lucknow (hypothetical)
Say a two-wheeler service centre in Lucknow sees heavy crowds from 9 to 11 am, when customers drop off bikes for service, and again from 5 to 7 pm, when they collect them. It has three service advisors for intake, one estimate desk and two delivery and billing counters. Customers crowd the intake desk in the morning and ring the centre repeatedly in the evening asking if their bike is ready.
A sensible setup: QR code standees at the gate and a tablet kiosk with a thermal printer for customers who prefer paper. Services: A for drop-off, B for pick-up, C for enquiries. Three advisors take A tokens, one desk takes C, two counters take B. The existing TV in the lounge runs the display with Hindi and English announcements from recorded clips. When a job card is closed in the workshop, a WhatsApp message tells the customer the bike is ready and gives them a B token for pick-up, so they arrive when their bike is waiting rather than when they finish work.
In reports, the manager watches morning wait times at intake and evening service times at delivery, and moves one advisor to delivery after 4 pm if the numbers justify it. This is a hypothetical illustration to show how the pieces fit, not a client project; your setup would come from a short call about your peak hours and counters.
Queue management system across India
Queues look different in every city. Pilgrim and tourist towns such as Tirupati, Agra and Shimla have service counters that face sudden surges. Commercial cities like Rajkot, Jalandhar and Salem have busy service centres and bank branches serving traders. Medical hubs in Jabalpur, Gwalior and Cuttack draw patients from surrounding districts who need printed tokens and clear voice calls in the local language.
The build and support are remote everywhere, with the same prices and process. What changes is the language of the voice clips and kiosk labels, the mix of QR and printed tokens, and how many visitors arrive with smartphones in hand.
Queue management system checklist before you ask for a quote
Share these details with your enquiry. A short video of your waiting area at peak time is often more useful than a long description.
- Type of place: clinic, lab, bank, service centre, office, other
- Services visitors come for, and which counters handle each
- Number of counters, and whether some handle more than one service
- Busiest hours and roughly how many visitors arrive per hour then
- How visitors should get tokens: kiosk, QR, WhatsApp, reception, or a mix
- Languages for voice calls, kiosk screens and messages
- Priority rules for seniors, persons with disabilities or appointments
- TVs, tablets, printers and PCs you already have
- Any software the queue must connect with, such as clinic or billing
- Number of branches now and planned
If visitors find you through Google, a clear website with timings and a "join the queue" link helps; business websites start at ₹10,000.