Nobody crowds a counter when they know their turn.
Token issue, counter calling, displays people can read from the back of the hall, and — the part administrators actually want — a measured record of how long everyone waited.
Two problems, not one
Crowding at a counter is the visible problem, and a token system fixes it. The invisible problem is that nobody knows how long people wait, which counter is slow, or whether the extra staff member on Tuesdays made any difference. Administrators are managing a service with no measurement at all.
QueSys handles both. The queue becomes orderly, and the waiting becomes a number.
What it includes
- Token issue at entry, by service category where there is more than one.
- Counter calling from keypad callers, kiosks, handheld units or tablets.
- Software controls: hold, reassign, online tokens and reports.
- Displays — main hall LED, per-counter indicators, readable from the back of the room.
- Voice announcement in the languages the people in that hall actually speak.
- Reporting: average and maximum wait, service time by counter and by operator, load by hour and by day.
Where it is running
Aadhaar enrolment centres and healthcare networks, serving thousands of people a day across multiple centres on one platform. The deployment was recognised with an Innovation of the Year award. Read the deployment.
For hospitals and diagnostic centres
The same measurement extends to the whole patient path, not just the counter: registration, sample collection, imaging, consultation and report delivery. Once the waiting at each stage is measured, the bottleneck is usually not where the staff believe it is. We would be glad to walk you through what that looks like.
Common questions
How many counters can one system handle?
From a two-counter clinic to a large multi-category service hall. The architecture is the same; the display and token configuration changes.
Can it announce in more than one language?
Yes, and it should. Announcements are configured for the languages used at that location.
Can we get the wait-time reports without the displays?
Technically yes, but we would question it. The measurement is most useful alongside the thing that makes the queue orderly in the first place.
