Kiosk or front desk
Customers serve themselves on a tablet or front-desk PC, or staff register walk-ins at the desk with the same three steps and can set a priority class.
End to end
1 · Getting a number
On a tablet or front-desk PC, or with staff at the desk. No app, no account.
The customer types their name. A mobile number is optional and, if given, is checked for format. It is only used to look the ticket up later.
Every active service of the branch appears as a large card with its prefix letter, name and description. Inactive services are hidden.
“Get and print my ticket” creates the number. A double tap never creates two tickets, and the page resets itself for the next customer after a set time.
Customers serve themselves on a tablet or front-desk PC, or staff register walk-ins at the desk with the same three steps and can set a priority class.
The ticket shows the queue number in large type, the service, the branch, the date and time, and the estimated wait, and asks the customer to watch the display.
Where printing is on, the browser print dialog opens with a compact ticket for standard receipt printers. Otherwise customers simply note their number.
The public status page looks a ticket up by queue number or mobile number, without signing in, and shows its status, position and estimated wait.
If the company turns it on, customers can leave an email address to be told when their turn is near and when they are called.
If nothing matches, the status page says so kindly, and it never shows another customer’s name or number. Repeated lookups are limited.
2 · Ticket lifecycle
A ticket starts as Waiting, is Called to a counter and Served until Completed. Every other path is a deliberate action by staff, saved with who and when.
| Status | Meaning | Set by | In reports |
|---|---|---|---|
| Waiting | Registered and in the queue. | Set by: Registration, Resume, Transfer | In reports: Registered |
| Called | A counter has called the number and the customer is expected. | Set by: Call next, Recall | In reports: Registered |
| Serving | The customer is at the counter and service has started. | Set by: Start service | In reports: Registered |
| Completed | Service finished. | Set by: Complete | In reports: Served |
| Skipped | The customer did not respond to the call. Can still be recalled. | Set by: Skip | In reports: Skipped |
| No show | The customer did not appear after the allowed recalls or skip window. | Set by: No show, or automatically | In reports: Skipped |
| Parked | Held by staff so the counter can serve someone else. | Set by: Park | In reports: Registered |
| Cancelled | Ended before service started, by staff or at the customer’s request. | Set by: Cancel | In reports: Cancelled |
| Closed (end of day) | Left open at the end of a day and closed by staff. | Set by: Close previous-day tickets | In reports: Closed, not served |
3 · Counter actions
Ten actions cover every situation at a counter. Each one is a single click and is saved with the staff member, counter, ticket and time.
4 · Calling order
Staff never choose by hand. Call next follows the same rules at every counter, so the order is fair and explainable.
A counter calls from the waiting tickets of the services assigned to it: one service, several or all of them.
Higher-priority classes go first; within the same class, the earliest registration time wins, across all of the counter’s services.
Priority never starves everyone else: for example, after every 3 priority calls, 1 standard ticket is called.
A counter serves one customer at a time, so Call next is disabled while a ticket is in service.
Every active counter for a service is offered its tickets, and the first to call takes it. Two counters can never call the same ticket.
A counter on a break is excluded from routing and shown as Paused on the display.
5 · Estimated wait
Take the tickets ahead in the service, multiply by that service’s average service time, and share the work between the counters serving it. Round up to whole minutes.
6 tickets ahead times 4 minutes average service time, divided by 2 active counters, equals about 12 minutes.
6 · The live display
A full-screen page for any TV, opened once with the branch’s display link. Its five zones update on their own.
The latest call in very large type with its counter, “A025, Counter 3”. Before the first call it says “Waiting for the next call”.
The next tickets to be called, with their counter where it is already known (5 by default).
One card per active service: the latest ticket called, its counter and how many are waiting.
Each call or recall is highlighted and announced: “A025, please proceed to Counter 3”. Volume and mute are settings.
Uploaded videos play in a loop and pause for every call; announcement messages scroll along the bottom.
It refreshes every 5 seconds by default. If the connection drops it keeps the last known state with a small “reconnecting” notice, and recovers on its own.
7 · Numbering
Tomorrow every service starts again from 001.
Get started
Click through a real HANA QMS workspace as an admin, a branch manager or a staff member, no sign-up needed. Or tell us about your branches and we will set up a walkthrough.