What a Joinlah queue actually is
A queue gives people a ticket number (like “A012”) and a place to wait that isn't a physical line: they can be anywhere on the venue floor and get notified when they're close to being called. It works for a registration desk with more people than counters, a food stall at a festival, or a single vendor booth with its own line. Turn it on from your event's edit page under modules, then set up individual queues from your event → Queues.
Create a queue
- 1
Name it and give it a prefix
The prefix is the letter in front of every ticket number for that queue: “A” for one counter, “B” for another, so two queues running side by side never hand out the same number.
- 2
Set the grace period
When someone's called and they don't show up, the grace period is how long they have before they're automatically skipped and the next person is called instead. A few minutes is typical for a busy booth.
- 3
Set how far ahead to notify
Attendees who opt into push notifications get an “almost your turn” alert once they're within this many tickets of being called, so they can head back toward the queue instead of watching a screen the whole time.
- 4
Share the join link or QR code
Each queue has its own public join page. Post the QR code at the booth, or share the link directly: attendees already registered for the event can join with one tap; walk-ins without an RSVP can join too and opt into push notifications right there, no account needed.
Running the queue
Open Queue operator on the phone that's actually managing the line. It's built for one-handed use at a booth: a big “call next” button, a way to mark the current ticket as being served, skip a no-show, and mark a ticket complete once you're done with that person.
Tip
For a public-facing screen (a tablet or TV showing “now serving A012” above the booth), use the queue display page instead of the operator view. It updates live as tickets are called, with no interaction needed once it's set up.
Vendor booths and staff who don't have an account
If a vendor is running their own booth (see the vendor application flow), their queue lives under their own vendor dashboard, separate from your main event queues. For helpers who shouldn't need a full login just to run a booth for an afternoon, generate a staff link. It operates one specific queue, can be revoked at any time, and needs nothing more than the link itself to use.
- Restrict a queue to specific team members: assign collaborators to a queue from the collaborators page, and only those people can operate it, useful when different staff run different booths.
- Reset a queue: clears every waiting ticket, for reusing the same queue across separate sessions of a multi-day event.
Before you start
Queue join and status pages update live over a persistent connection. If a participant's status seems stuck, the page also quietly re-checks every few seconds on its own, so a manual refresh is rarely needed, but never hurts.