On this page
Start with a clear expectation
A customer may be happy to wait for a haircut or freshly cooked food. What makes waiting harder is not knowing what happens next. Before asking them to scan a QR code, explain what it is for: joining a service queue, or tracking an order they have already placed.
Show the right code in the right place
Use a short instruction beside the QR. For a service queue, try “Scan to join the haircut queue.” For collection, try “Already ordered? Scan and enter your receipt number.” If your venue uses both workflows, put each sign where it belongs and give it a clear heading.
Explain what the ticket can tell them
Walk-in customers may see their queue position or an estimated wait, depending on the queue settings. Collection customers see the status of the receipt number they entered. Avoid giving a precise return time unless your team can support it; a ticket is useful because it can update as the situation changes.
Agree how far customers can go
Tell people whether they can find a nearby table, visit the next shop or simply wait outside. A clinic may need patients to remain within a particular area. Staff should give instructions that fit the venue rather than assuming every customer can leave.
Make alerts a clear choice
Customers use QueueFinder in their browser, without an app-store download. Ask them to turn on alerts from their ticket. If alerts are off, use your normal calling method.
Finish the handover
For walk-in service, staff should record the start and completion of the service. For collection, check the receipt, hand over the order and select Collected. Duplicate order numbers need the same receipt checks you would normally use. Keeping the ticket status current makes the dashboard more useful for the next staff member.
Learn from a shift
After trying the process, ask a few customers whether the sign and ticket were easy to understand. Ask staff whether they could find the right ticket quickly. Review the recorded activity, then change one part of the process at a time. The aim is a clearer wait and a smoother return, not simply more people scanning a code.