Queues look different everywhere. Here's how Qrua fits each one.
Every business sets Qrua up a little differently depending on how its line actually works. These are the setups we see most.
Create it now, claim it later. One queue is free for as long as you want it.
Prefer an account first? Start Free
Single queue, single counter
The simplest setup: one queue, one counter, one or a few staff working it directly.
Example: a small barbershop with one chair runs a single queue. Walk-ins scan the QR code, wait their turn, and the one barber calls the next name when free.
Single queue, multiple staff, dynamic counter allocation
Several staff pull from one shared queue, so whoever's free next serves whoever's waited longest - and each sets their own counter label as they sit down.
Example: a bank with six teller windows but only three tellers on a slow afternoon runs one shared queue. Each teller sets their own counter label when they sit down, and customers are always called to whichever counter is actually staffed.
Multiple queues, multiple counters
A business runs several independent queues side by side, each with its own name, settings and staff - for genuinely separate lines that shouldn't mix.
Example: a large clinic runs "General Consultation," "X-Ray" and "Pharmacy Pickup" as three separate queues, each staffed and managed on its own.
Multi-queue workflow, single customer journey
Queues are chained together so a customer automatically moves from one queue into the next as part of one multi-step process, without a new token or a new scan - a workflow can chain as many queues together as the process needs, not just two.
Example: a government office runs a document-check queue, then a payment queue, then a collection queue. A visitor served at document-check is automatically placed into the payment queue, and once paid, into the collection queue - moving through all three steps without being told where to go or scanning anything new.
One counter, multiple services
One staff member handles more than one service queue from a single screen, switching between them as needed, instead of needing a separate login or device per service.
Example: a single front-desk staff member at a small clinic manages both the "General Checkup" queue and the "Walk-in Prescriptions" queue from the same tablet, switching between them throughout the day.
One QR code, many services, fewer queues
A business publishes one QR code listing every service it offers; customers pick the right one and are routed straight into the matching queue. A service isn't limited to a queue of its own either - several services can be assigned to the same queue.
Example: a bank branch has two queues but four services - Deposits, Withdrawals, Loan Enquiries, and Account Opening - all listed on the same shared QR code, with two services routed into each of the two queues.
Gated / pre-processing queue
A customer gets a token right away but only joins the actual waiting list once staff confirm a required pre-step is done - payment, a deposit, a document check, an intake form, or anything else the business needs first.
Example: a food counter gives every customer a token the moment they order, but that customer only joins the live serving queue once payment is confirmed at the till - so the live queue only ever shows people who've already paid and are genuinely waiting to be served.