Request a quote
Emergency SectorsCareers About us Blog Get in touch
Bright reception hall with a wooden desk, plants and large windows

A queue management system with ticket and screen: what the IT underneath has to settle

A queue management system looks simple: a kiosk that prints a number, a screen that calls it and a button at the counter. What makes the difference sits underneath. What happens when the internet drops, who changes the paper roll, and where do the phone numbers of people waiting remotely end up? This is the list we go through before a kiosk goes into a reception hall.

6 min read Written by the ITproposal team
Short answer

Choose the form first: a ticket from a kiosk, a virtual queue by SMS or QR code, or appointments. The technology follows from how your visitors arrive.

A queue management system is four kinds of device and a piece of software. Put them on their own network segment and ask what happens when the connection to the cloud drops.

The software belongs to a third party, and the phone numbers of people queuing remotely are personal data. Agree how long they are kept, and who changes the paper roll.

Which queue management system fits your counter

A queue management system decides the order in which visitors are served and shows how long that will take. There are three basic forms, and most organisations combine two of them:

  • A ticket from a kiosk. Visitors pick a service on arrival, get a number and wait in the hall. It suits a service desk, a pharmacy, a council office or a collection point where people walk in without an appointment.
  • A virtual queue. Visitors scan a QR code or leave a mobile number and get a text when their turn is close. They do not have to stay in the hall. It suits long waits or small spaces.
  • Appointments. Visitors check in at the kiosk with a code from their confirmation and are called at the booked time. The queuing system then becomes an extension of a booking calendar.

The deciding question is: how many services and how many counters? One queue for three counters is straightforward. Five services, each with their own staff, two of which also make call-backs, needs rules on who may call which number, and those rules belong on paper before anything is ordered.

The parts: kiosk, printer, screens and counter

A ticket-based queue management system is made of four kinds of device, and each has its own way of failing.

  • The ticket kiosk. A touchscreen in a housing with a built-in printer. The screen runs one app and nothing else; that is kiosk configuration, and it belongs with device management.
  • The ticket printer. A thermal receipt printer with a paper roll. It is the part that stops most often: the roll runs out, the paper jams or the print head gets dirty. Ask whether the kiosk warns that the roll is running low, not only when it is empty.
  • The calling screens. Screens in the waiting area showing the number and the counter, often with a chime. They are ordinary displays with a player or a built-in browser.
  • The counter. A button, a small unit or an application on the staff PC to call the next number, transfer it to a colleague or mark it as a no-show.

For each part, ask whether it is standard hardware or only available from the software vendor. A standard screen you can replace tomorrow; a proprietary unit waits for a delivery.

What the network has to handle

Every part talks to the others through the software, which runs either in the cloud or on a server on site. That decides what happens when something drops out.

  • A separate network segment. Kiosk, screens and counter units belong on their own segment, apart from staff devices and tills, with only the connections the software needs. A kiosk in a public hall is a device anyone can reach.
  • Wired where possible. A kiosk and a calling screen do not move. A network cable is more reliable there than wifi, and Power over Ethernet sometimes saves a socket.
  • Without internet. If the software is cloud-hosted, ask what happens when the connection drops for a quarter of an hour. Does the kiosk still issue tickets, and can counters still call? A hall full of people with no order is worse than a few minutes without statistics.
  • The same clock. Waiting times are calculated from timestamps on different devices. Have them take their time from one source, or the reports will not add up.

How we set up and monitor such a segment is described under managed network.

Virtual queuing: SMS, QR codes and personal data

As soon as a visitor leaves a phone number, you are processing personal data, and UK GDPR applies (or the EU GDPR, if you operate there). That is no reason not to do it, but it is a reason to arrange it in advance.

  • Only what is needed. A number for the message, no name unless it is needed, no free-text reason for the visit.
  • How long it is kept. The number is needed until the message has been sent. Agree with the vendor that it is then deleted or detached from the ticket.
  • A data processing agreement. The software vendor processes that data on your behalf, and that belongs in a written agreement, including where the servers are.
  • Who sends the text. Usually the vendor, through its own service. Ask which sender name the visitor sees and what happens when a message does not arrive.

In healthcare the bar is higher: even a number on a screen can say something about who is waiting. Call people there by number, never by name.

Integrations with bookings, screens and reporting

A queuing system rarely stands alone. The integrations are where it earns its keep, and where it breaks after an update.

  • The booking calendar. With appointments, the kiosk needs to know who is expected. Ask which calendars the software supports and who maintains the link when either side changes.
  • The screens in the hall. Calling numbers and information about your organisation on the same screen is attractive. The queuing system and the digital signage platform then have to share one screen, and that is a question for both vendors. What the screens themselves involve is covered under digital signage screens and players.
  • Reporting. Waiting and serving times per service, per hour and per counter. Ask whether you can export that data, because it is the reason for having the system.
  • More than one language. In a hall where visitors speak several languages, ask whether they can choose the language on the kiosk and whether the audio follows.

After go-live: paper, faults and who gets the call

On handover day everything works. What goes wrong afterwards usually goes wrong quietly: an empty paper roll does not send an error to your inbox, and a frozen screen simply keeps showing the last number.

  • Paper and print head. Agree who changes the roll, where the spares are kept and how often the print head is cleaned. That is work for someone on site, every week.
  • Monitoring. Have the software or the management platform report any kiosk or screen that has not checked in for a while. A broken kiosk is rarely reported; visitors just queue at the counter.
  • Updates outside opening hours. Software and devices get updates. Agree a fixed window for them, and test a major update at one site first.
  • A fallback. A stack of numbered cards in a drawer sounds old-fashioned and keeps a morning going. Agree when the counter switches to it and who decides.

And agree who gets the call: the software vendor, the party managing the devices, or both. When something fails at the counter, nobody wants to work out first whose problem it is.

What to ask the queue management system vendor

A demo shows you what the calling screen looks like. What matters in day-to-day running, you ask before you sign:

  • Does the software run in the cloud or on your own server, and what still works without internet?
  • Which devices are supported: standard screens and printers, or only the vendor’s own?
  • How is the licence counted: per site, per counter, per kiosk or per screen? That decides what an extra counter costs later.
  • Sign-in with multi-factor authentication, permissions per site and a log of who changed what.
  • How long are phone numbers and ticket data kept, and can you set that yourself?
  • Do you get your data and settings back if you move to another system?
  • Can someone in a wheelchair or with a visual impairment use the kiosk? Whether accessibility legislation applies to your kiosk is something to have checked.

Where our work stops

What we do. We supply the kiosk, the ticket printer, the calling screens and the counter equipment, install and connect them, put them on their own network segment and bring them into management and monitoring, so a kiosk that stops becomes an alert. On site, our own local engineers do that, in every country.

What we do not do. The queue management software belongs to a third party, just as with digital signage: how it works, the SMS service and the data in it sit with that vendor and with you. We do not write rules on who gets priority and we do not decide how you staff your counters. If there is a card terminal at the counter, it comes from your payment provider; we do not process payments. And we are not an accessibility auditor.

Frequently asked

Questions we get about this

The five that come up most often.

What is a queue management system?

A queue management system decides the order in which visitors are served at a counter. Usually the visitor takes a number at a kiosk and a screen calls that number when a counter is free. There are also forms where the visitor waits remotely and gets a text message, or checks in with an appointment code.

What are the components of a queuing system?

A ticket kiosk with a touchscreen, a thermal printer for the tickets, one or more calling screens in the waiting area, and a button or application at each counter to call the next number. Underneath runs the software, in the cloud or on a server on site, and a network that connects it all.

Does a queue management system work without internet?

That depends on the software. Some systems keep issuing and calling tickets on site when the connection to the cloud drops; others stop completely. Ask before you choose, and agree a fallback for the counter.

Can you ask for phone numbers for a virtual queue?

Yes, but they are personal data and data protection law applies. Ask only for what is needed, agree that the number is deleted once the message has been sent, and set out the processing in a data processing agreement with the software vendor.

Do you also supply the queue management software?

No. The software belongs to a third party, and that vendor is responsible for how it works, the SMS service and the data in it. We supply, install and manage the kiosk, the printer, the screens, the counter equipment and the network underneath. A card terminal comes from your payment provider; we do not process payments.

Related services

Further reading

What a queue management system connects to.

Start at the counter, then the kiosk

Tell us how many sites, counters and services there are and which software you have in mind. We will tell you what kiosks, screens, printers and network it needs; the software stays with its vendor.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call