Queue Ticket

How to use Queue Ticket

From creating a queue to the poster, calling people and wrapping up, plus how the wait estimate is worked out.

How it works

1. Create a queue
Pick booth, consultation, talk order, tasting, photo spot or flea market and create it. You get a 6-character code and a QR poster right away. Only the host should hold the host link.
2. Put up the poster
Print the poster or save it as a PDF and put it at the entrance. Visitors scan the QR code and land on the get-a-ticket screen. A number is taken only when they press the button, so link previews or accidental opens never use up numbers.
3. Call people
The host presses call next, and each visitor sees how many people are ahead, refreshed every 8 seconds. When it is your turn the screen flashes and the phone vibrates. Both can be turned off.
4. Wrap up
Press close queue when you finish. Every record is deleted 2 hours later. If you forget, they are deleted 24 hours after the last host action.

Ticket letters by type

TypeExampleGood for
BoothB-014club experience booths, lines in front of event booths
ConsultationC-003career or study advice, consulting desks
Talk orderT-007class presentations, lightning talks, demo order
TastingS-021tasting events, free samples
Photo spotP-012photo booths, commemorative photo lines
Flea marketF-045lines at popular stalls

How the wait estimate works

The service averages the gaps between the host calls, using only gaps from 5 seconds to 30 minutes. Presses closer than 5 seconds count as accidental double taps and gaps over 30 minutes count as breaks, so both are left out.

Once three gaps are collected, it shows (people ahead + 1) times the average gap, rounded up to whole minutes. Before that it only says the estimate is being calculated. While the host has paused the line, the estimate is hidden.

Real waits vary from person to person, so the estimate can be wrong. Treat the number as a rough guide only.

Good to know

  • One queue hands out up to 200 tickets, and one person can hold one ticket per queue.
  • An anonymous token stays in the browser storage of the device that took the ticket. After closing and reopening the tab you come back to the same number. If you clear browser data, the ticket cannot be found again.
  • Battery saver or a dark screen can stop the vibration and flashing from reaching you. There is no sound alert.
  • If many people share one Wi-Fi network, request limits can kick in. Try mobile data in that case.
  • A skipped number can get a new ticket and join the end of the line. Someone who was already called cannot take another ticket in the same queue.
  • If the server does not answer, the last checked screen stays visible, and the host can keep calling numbers with the no-server counter.

Ways to use it

Not sure how many tickets to prepare or how many queues to create? Start from a suggested setup for a similar event.

See all use cases