Queue Ticket

Queue Ticket

Scan a QR code, get a ticket number, and see how many people are ahead of you. No sign-up or phone number needed to run a line at your event.

Stored on a server: only the number and a hash of an anonymous token, for 24 hours. No names or phone numbers.

Create a queue

Queue type

The type sets the letter on each ticket: booths print B-001, consultations C-001, and so on.

I have a ticket code

Paste the 6-character code or the link printed on the poster.

Use without a server

If the server is down, this device alone can still call numbers. Hand out numbers on paper or by voice. Nothing on this screen is saved anywhere.

-Nobody called yet · Numbers handed out up to 0

Stored on a server

This service uses a server. It stores only the ticket number, a hash (scrambled value) of an anonymous token, and times. It does not store names, phone numbers or IP addresses. A queue is deleted 24 hours after the host last acted and a ticket 24 hours after it was taken. Wait estimates are a rough guide. Do not use this for medical, government or other important waits.

For reference only. Do not use it for waits where order matters for health, government or safety. The operator is not responsible for disputes about order.

Frequently asked questions

  • Do I need an account or a phone number to get a ticket?

    No. Scan the QR code and press the get-a-ticket button. The service does not ask for a name or phone number. Only a hash of an anonymous token made by your browser is stored on the server.

  • How do I know when it is my turn?

    While the page is open it checks every 8 seconds, then flashes the screen and vibrates on your turn. There is no sound, and battery saver or a dark screen can block the alert.

  • How accurate is the wait estimate?

    It is a rough guide: the average gap between the host's calls times the number of people ahead of you. It appears only after more than 3 calls and can differ from the real wait.

See all questions

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