Document screening first
Validate at the door, not at the counter. A wasted two-hour visit becomes a two-minute redirect.
Government transaction centres
A citizen who needs three counters should not join three queues. Screen the documents at the door, carry the token across departments, and export the service-level evidence instead of reconstructing it.
How it gets configured
Configured for a hall where one transaction can require several desks in a fixed order.
Services on the kiosk
A short screening step at the door catches a missing document before it costs someone two hours.
Token prefixes
Each department keeps its own series while sharing one board and one citizen journey.
Counters & roles
A token transfers between desks with its history attached, so a three-stop transaction stays one visit.
Integrations
Timestamps at issue, call and close make the compliance report a query rather than a project.
When the room fills — a typical week
Service halls load heaviest at the start of the week and after public holidays. Publishing the quiet windows shifts demand on its own.
Key use cases
Public offices rarely have one line. The problem was never the queue — it was the sequence.
Validate at the door, not at the counter. A wasted two-hour visit becomes a two-minute redirect.
Each keeps its own prefix and counters, on one shared board and one citizen journey.
Declared at intake, bounded by a ratio, and logged — so the reason a token jumped is recoverable months later.
The cashier queue receives the token directly instead of sending the citizen back to the start.
Percentage served within target, by department, exported for the quarterly report.
Every call timestamped and attributable, with role-based access over the console.
Transparency
When the order is on the wall, nobody has to police it. Complaints about being skipped fall away, because the record shows exactly what was called and when.
Tell us how many desks and departments you run, and we will show you the board.
Deployment usually runs two to six weeks