UAE queue system
A ticket, a counter, and a screen
Queue management for a UAE client: kiosk tickets, a live board, and counter calls.
9 wks
Kiosk through screen
Redis
Live ticket fan-out
Per service
Separate sequences
Client names, logos, and contracts stay unpublished under NDA. Software screens use sample data, not live records.
Outcome focus
Live board
Kiosk, counters, and a waiting screen
01 — Context
Challenge
People took a paper number that did not match the counter. Staff called numbers the room could not hear, and walk-aways were invisible.
02 — Method
Approach
A kiosk issues the next ticket for a service. Counters call the next ticket. The waiting screen and an optional SMS show the number being served. The venue is not named.
Workflow
Take a ticket
The visitor picks a service. The kiosk prints the next number.
Call next
A counter calls the oldest waiting ticket for that service.
Show it
The screen updates. SMS can repeat the call for that ticket.
Outcomes
- One sequence per service
- The screen and the counter show the same current ticket
- Staff can see who is still waiting
Measurement
Illustrative patterns from this engagement style
Tickets called from the counter app
Illustrative share of served tickets that were called in the system rather than shouted.
- 20 W4
- 38 W5
- 55 W6
- 74 W8
- 86 W9
Checkpoint values
Same series as bars — useful for scanning week-to-week movement.
How people knew their turn
Illustrative.
Before
- Asked staff45%
- Paper guess40%
- Screen15%
After we rebalance
- Asked staff12%
- Paper guess8%
- Screen80%
Charts are illustrative patterns for how we sequence and measure work in this category. They are not audited financial results or guarantees.
Visuals
Project gallery
Forms and listings are sample interfaces. They are not screenshots of a client's live data.
Need a similar outcome?
Book a free audit. We will tell you whether a campaign rebuild, a product build, or a creative system is the honest next step.
Book a free audit