Long, visible lines
Permit and payment windows draw crowds at opening time, and visitors cannot tell how long they will wait.
For government offices & city halls
Clear, fair queues for every citizen
Give every visitor a number they can follow on a large display and by voice, serve priority citizens first by law, and keep a record of every action at every window.
Typical challenges
What gets in the way today
Priority by law
Senior citizens, PWD and pregnant visitors must be served first, consistently, at every window.
Limited daily capacity
Some services can only handle a set number of visitors per day, and turning people away late is frustrating.
Accountability
Every action at a public window should be traceable to a person and a time.
A day in the life
From opening to close
How a typical day runs with HANA QMS. Times are examples.
Before opening
Staff close any tickets left open from yesterday, so today starts from the first number.
Opening rush
Visitors take Permits, Payments or Civil registry tickets; priority citizens are registered at the desk.
Daily limit reached
Permits reaches its daily limit. Registration for Permits closes and the kiosk says so clearly.
Window change
Window 6 serves All services and calls the longest-waiting ticket across them.
Announcements
The display scrolls opening hours and requirements between calls.
Accountability
Queue activity shows every call, skip and transfer with staff member, window and time.
How HANA QMS helps
Built for how your front desk works
Every point below is a standard part of the product, configured by your own admins.
Big numbers and voice calls
The display shows Now serving in very large type and announces “A025, please proceed to Counter 3” with a chime and voice.
Priority lanes
Priority classes are called first within each service, in registration order, with a fairness rule to keep everyone moving.
Daily ticket limits
Set a daily limit per service; registration for that service closes when the limit is reached.
Accessible public pages
Registration, ticket and status pages work with a keyboard and screen readers and never rely on colour alone.
A complete activity history
Queue activity records every ticket event with time, staff member and counter, and entries cannot be edited.
Recommended setup
A starting point you can change any time
A suggested first configuration. Your admins adjust services, counters and rules themselves as you learn what works.
- Routing
- Counter-based routing: each window serves its own service, with one or two windows set to All services for overflow.
- Priority lanes
- Senior citizen, PWD and Pregnant above Standard. Staff choose the class at internal registration.
- Displays
- A large display in the main hall, and separate displays limited to a counter group where windows are in different rooms.
Example services
- PPermitsP001
- YPaymentsY001
- RCivil registryR001
Example counters
- Window 1–2 · Permits
- Window 3–4 · Payments
- Window 5 · Civil registry
- Window 6 · All services
Features that matter most
Where to look first
Common questions
Asked by teams like yours
- Can we cap how many visitors a service takes per day?
- Yes. Set a daily ticket limit per service; registration for it closes when the limit is reached.
- Are the public pages accessible?
- Registration, ticket and status pages are built to WCAG 2.1 AA: keyboard and screen-reader friendly, with readable contrast.
- Can windows in different rooms have their own screens?
- Yes. Open several displays and limit each to a group of services or counters.
Get started
Give every customer a calm wait.
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.