Every configuration step for an on-premise queue system — the ticket buttons, the ticket station, the TV display, the layout, and the Queue Manager at each counter. Real screenshots, in the order you'll actually do them.
None of this takes long, but chasing a missing WiFi password halfway through a counter install is how a one-hour job becomes an afternoon.
The WiFi name and password, or a spare LAN point at each device. Every part of the system talks over your own network — there is nothing to configure on the internet side for an on-premise install.
The names customers will see on the ticket buttons — Registration, Payment, Inquiry, Collection. Decide these first; they set the ticket prefixes and the whole numbering scheme.
The address of the machine running the Queue Manager, plus the port we set at installation. We hand these to you when the system is commissioned — write them down once and every display and counter uses the same pair.
Click any step to open it. The first one is expanded to get you going.
Each service you offer becomes one button on the ticket station. Give it a name, a prefix and a starting number, and the printer produces the right ticket the moment a customer touches it.
Two words at most. A customer standing at a kiosk reads the screen in about two seconds, and a long label is the fastest way to get people queuing at the wrong counter.
Once the buttons are saved, the station runs itself. Staff log in once in the morning and leave it on the service selection screen for the rest of the day.
Their own number and the number currently being served are both printed. That one detail is what stops people asking staff how long the wait is.


The display box drives any TV over HDMI. Give it network access, tell it where the Queue Manager is, restart it, and it stays live from then on — including through a power cut, because it comes straight back up on its own.
Announcements play through the TV's own speakers. With several screens in one hall, leave the voice enabled on one of them only — otherwise the same number is called back at you three times over.




The layout decides how the screen is divided — one huge number, six counters side by side, a video panel with queues down the edge. Click a preview to select it, then restart the display for the change to take effect.
A single huge number reads from the back of a large hall. Six counters at once works when people are seated close. Portrait Tower is for the tall screens in a lift lobby. Full walkthrough on the QDisplay page.
One Queue Manager per counter. Staff log in with their counter number and work from a single screen for the rest of the shift — call the next customer, recall one who didn't hear, insert a walk-in by hand, or push someone to another department.
With several counters running, one Queue Manager acts as the server the ticket stations and displays connect to. The rest connect to it. We set which one during commissioning — it is normally the machine that stays switched on longest.


Not every counter needs a PC. Staff can work the queue from an Android tablet or from a browser on any machine on the network. Both routes need one thing the Windows-only setup can skip: a shared database.
A Windows-only setup can run without a separate database server. The moment a tablet or a browser counter is involved it becomes a requirement. It can share an existing PC, but it has to exist somewhere — see the server page.


Our own team installs it — hardware, network, displays, counters and staff training, on site. We cover the whole of Malaysia and Singapore, with engineers based in Kuala Lumpur, Penang and Johor Bahru.
Send us a photo of the screen you're on. Our support team reads it and tells you exactly what to change — usually within the hour during business days.