What is queue management kiosk software?
Queue management kiosk software turns a crowd at a counter into an ordered, visible sequence. A customer walks up to a token kiosk, chooses the service they need, and receives a numbered token on paper or by SMS. From that point the software owns the wait: it holds the customer's place, routes them to whichever counter handles that service, shows the current state of every queue on display boards and, when their number is called, announces it on screen and by voice. Behind the counters, staff work from a caller application that advances the queue, transfers a customer to another desk or parks them while a document is fetched. Everything that happens is timestamped, which is where the wait-time, throughput and no-show reporting comes from.
AtashiTech supplies the software layer: the token kiosk application, the display-board and counter applications, and the local queue service that ties them together on the branch network. It sits alongside our other kiosk and self-service solutions, and it runs on kiosk and display hardware you source; we do not manufacture the units.
A queue you cannot see is a queue you cannot manage
Branches and service centres rarely lack staff for the average hour. They lack any way of matching staff to the hour that actually arrives.
The old way
Customers stand in a line that is really three lines: people who need a two-minute task, people who need twenty minutes, and people who are in the wrong line altogether. A guard hands out paper slips from a pad, or nobody does and the order is enforced by memory and argument. A counter opens or closes and the whole line shuffles. Someone steps out to take a call and loses their place. The manager's only view of the situation is the length of the line through the glass.
The cost of this is not only the customer's patience. Staff spend part of every transaction managing the line rather than serving it. Priority customers, the elderly, or a customer with an appointment cannot be honoured without an argument. At the end of the month there is no record of how long people waited, how many gave up, or which service consumed the counters, so the next month is staffed the same way as the last one.
The AtashiTech way
Queue management kiosk software separates arrival from service. A customer chooses the service on the touch screen, takes a printed or SMS token, and sits down. Display boards show the numbers being served and the estimated wait for each queue, so nobody stands guard over their place. Counter staff press a button to call the next customer for the services their desk handles, and can transfer or park a customer without a conversation across the hall. Priority rules, appointments and multi-service visits are policy in the software, applied consistently regardless of who is on the desk.
Because the queue service runs on the branch's own network as a Windows service, the kiosk, the displays and the counters keep working if the wide-area link fails. Analytics upload later; the queue itself never depends on a server elsewhere.
How it works
Four moving parts, one local queue service. The customer only ever sees the first and the third.
Choose a service
The kiosk shows the services offered at that branch in the local languages, grouped so a first-time visitor can find theirs. A customer with an appointment scans the QR from their confirmation and is placed according to the booked slot; a walk-in optionally enters a mobile number to receive updates.
Receive a token
A thermal token prints with the number, the service, the time and the current queue position, or the same details arrive by SMS or WhatsApp for customers who would rather wait outside. Priority categories such as senior citizens or differently abled customers are flagged at this step.
Wait with visibility
Display boards in the waiting area list the tokens now being served, the counters serving them and an estimated wait per queue. When a token is called, the board highlights it, a chime plays and a voice announcement names the number and counter in the configured languages.
Serve, transfer, close
At the desk, staff use the counter application to call the next token, recall a no-show, transfer the customer to another service queue or park them while paperwork is completed. Closing the ticket writes the service time to the record that feeds the analytics.
Core features
The package covers the customer side, the staff side and the manager side of a queue. Each is a separate application talking to one local service.
Multi-service, multi-counter routing
Services map to counters many-to-many. A desk can serve three services; a service can be served by any of five desks. Rules decide which waiting customer is called next.
Printed, SMS and WhatsApp tokens
Tokens print on a thermal printer at the kiosk, and can be sent to the customer's phone so they can leave the hall and return when their turn approaches.
Live display boards
Large-format screens show now-serving tokens, counter numbers and estimated waits, with audio announcements in the languages the branch chooses. Boards can also carry promotional content between calls.
Priority queuing
Senior citizens, VIP account holders, expectant mothers or any category you define are placed ahead under rules you set, without staff having to justify the decision to the rest of the hall.
Appointment slots
Customers book a time online or through your app and check in at the kiosk with a QR code. The queue honours the slot while keeping walk-ins moving in between.
Counter and staff dashboard
Each desk sees its own queue and the totals for the hall. A supervisor view shows which counters are open, who is idle, and where a queue is building, and can reassign services on the spot.
Wait, throughput and no-show analytics
Every token carries its issue, call, start and close times, so reports on average and peak wait, service time by counter and no-show rates by hour come from data rather than impression.
CRM and core-system integration
The token can carry the customer's identity from your CRM so the counter application opens their record when they are called, and service events can be written back for follow-up.
Hardware and integrations
A queue system is spread across the hall: a kiosk at the entrance, screens on the wall, a small application on every counter PC or tablet. All of it speaks to one queue service on the branch LAN.
Components and connections
Unlike a single-box kiosk, a queue system has several endpoints. The table shows each one, what it runs on and how it reaches the queue service, so a branch IT team can see what the installation touches.
| Component | Role | Runs on | Connection |
|---|---|---|---|
| Token kiosk | Service selection, token issue, appointment check-in | Windows kiosk PC with touch screen and thermal printer | LAN to the queue service; printer on USB or serial |
| Display boards | Now-serving, waits, announcements, promotions | Android display application on a commercial screen, or an HDMI player | LAN, real-time push from the queue service |
| Counter application | Call, recall, transfer, park, close | Windows desktop or Android tablet at each counter | LAN, one login per desk |
| Queue service | Holds every queue and applies routing rules | Windows service on a branch PC or server | Local database; syncs analytics to the central platform |
| Messaging | SMS and WhatsApp tokens and call-ups | Cloud gateway such as Twilio or MSG91 | HTTPS from the queue service; queued when offline |
| CRM and core systems | Customer lookup, service events | Your CRM, banking or ERP platform | REST APIs; scoped per customer |
The display-board application is a product of our Android TV and signage app practice, and the counter and kiosk applications come from kiosk application development; the CRM and core-system connectors are built per engagement by the integration team. Where a branch already runs an appointment system or a CRM with a customer-visit module, we connect to it rather than replace it.
Where queue management kiosk software is used
Any place where more people arrive than can be served at once, and where the order of service matters, is a candidate.
Banks and NBFC branches
Cash, account services, loans and grievances each take a different time and a different desk. Routing by service, honouring appointments made in the mobile app and placing senior citizens ahead are the rules branches ask for first; the counter application opening the customer's record from the token comes next.
Government service centres
Passport, transport, municipal and citizen-service offices process high volumes with fixed windows. A token kiosk with multilingual screens and voice announcements, and a display that shows which window is serving which number, replaces the guard-with-a-pad system that most offices still run.
Hospital outpatient departments
OPD registration, consultation, billing and pharmacy are separate queues that the same patient passes through. Our patient registration and screening kiosk issues the first token as part of intake, and the queue service carries the patient through the remaining counters without a fresh token at each one.
Telecom and utility customer care
Retail stores and utility offices mix quick payments with long service requests. Payments are better moved off the queue entirely onto a bill payment and collection kiosk; what remains is routed by service type so a SIM replacement does not wait behind a tariff dispute.
Retail service counters
Returns, alterations, click-and-collect and jewellery counters all queue. Stores that already run our retail self-checkout kiosk often add a token queue at the service desk so the two kinds of waiting are kept apart.
Corporate reception and shared services
Large campuses run internal help desks, ID card counters and HR windows that employees queue for. Where visitors are involved, the visitor management kiosk handles entry and the queue service handles the wait inside.
Deployment, offline operation, AMC and remote management
A queue system is judged on the first busy morning after go-live. This section covers how we get it there and keep it there.
Deployment
The branch installation is the queue service, the kiosk application, the display application on each screen and the counter application on each desk. Services, counters, routing rules, priority categories, languages and ticket layouts are configured for the branch, and a multi-branch customer keeps a master configuration with per-branch differences. We normally run the new system in parallel with the existing paper slips for the first sessions, then remove the pad.
Offline operation
The queue lives on the branch LAN. If the internet connection to head office drops, tokens are still issued, boards still update and counters still call, because none of that leaves the building. SMS and WhatsApp messages queue until the link returns, and the customer-facing screen says so, so staff are not asked why the text did not arrive. Analytics sync afterwards; nothing is lost because a record was written locally first.
Annual maintenance contract
Queue management kiosk software is used every working hour, which means the maintenance arrangement matters as much as the build. An AMC through our consulting and AMC support service covers updates, printer and display driver changes, rule adjustments as the branch's services change, and a support channel for the branch manager. Terms are agreed per customer.
Remote management
Head office wants to know that every branch's kiosk is printing, every board is showing the right content and every queue service is up, without phoning the branch. The centralized kiosk management platform monitors each component, raises an alert when a printer is out of paper or a display has gone dark, and pushes new services, languages or promotional content to all branches at once. Longer notes on running branch estates are on the blog.
Bring order to the hall
Describe the branch: how many counters, which services, whether customers book appointments, and how many locations you eventually want on one dashboard. We will propose the routing rules, list the hardware the software needs, and quote the work. Reach us through the contact page; there is no fixed price because branch layouts differ.