Check-in queues

A queueA named group that tickets are placed in so you can direct people to the right check-in desk, for example General, Priority, or Escalation. A queue is a label and a grouping, not a physical line: you decide which tickets go in it and which desks work from it. A ticket can be moved between queues by a rule or by an operator. is a named group of tickets you use to direct people to the right check-in desk, for example General, Priority, and Escalation. Queues are optional.

Why use queues

Queues let you handle groups of attendees differently:

• Route people to the right desk. Send priority attendees to a fast lane and problems to an escalation desk.
• Show a queue on a desk. A desk can display its queue on its standby screen, so operators see who is coming.
• Trigger printing. A queue can print something automatically when a ticket enters it, such as a merch picklist.
• Split pre-printed badges across desks. If you pre-print badges, queues let you physically separate them between desks so each operator only sorts through their own stack, which keeps lines moving and cuts down on time spent hunting for a badge. Group your badges by queue when you print them. The usual setup is several queues for one attendee type, for example General 1 through General 4, filled by a rule set to split evenly across them with improved sorting turned on.

Create a queue

Registration → Queues → New Queue

Give the queue a title and a short display code, and choose whether it clears a ticket once that person is checked in.

A queue has:

• Title. Its name, used in the admin.
• Display code. A short code (up to four characters) shown on desk displays and badges, such as GEN or VIP. On-site staff read it at a glance, so keep it short: one to three letters works well, and a single letter is often simplest.
• Visible to users. Whether attendees can see which queue they are in.
• Auto-remove on status change. Whether a ticket leaves the queue once the attendee is checked in.

Auto-remove on status change

With this on, a ticket leaves the queue once the attendee is checked in, so the queue reflects who is still waiting. Leave it off for a merch queue, where you want checked-in attendees to stay until their goods are handed over.

Fill queues with rules

A queue rule decides which tickets go into a queue. Because it matches on ticket fields, it is a ticket rule. Each rule has:

• Name and priority. Rules run from the lowest priority number upwards, and the first rule that matches decides the queue.
• Active. Whether the rule is in use.
• Assign automatically. Whether the rule runs on its own when an order is confirmed, so tickets are sorted into queues before the day.
• Queues. One queue means every match goes there. Two or more means matches are split evenly across them, keeping a party together on the same queue.
• Conditions. What the rule matches on, built as a ticket rule.

To sort tickets that already exist (for example after adding a rule mid-sale), use the bulk Assign queues action.

Move an attendee by hand

An operator can move a ticket into another queue from the desk, for example into the merch queue after check-in, or up to the escalation desk when there is a problem. You can also move tickets between queues in the admin before the event, for example to balance stacks of pre-printed badges across desks.

Print automatically for a queue

A queue can print something when a ticket enters it. Each print rule chooses a type and a device:

• Pickup receipt
• Merch picklist, for example to the merch table’s receipt printer.
• Badge

Set a badge rule to assign automatically to pre-print badges in advance, such as printing day-pass badges as each order is confirmed rather than at the desk. See Badge printing.

Show a queue at a desk

A station profile’s display queue shows that queue on the desk’s standby screen, so operators can see who is in it. See Stations and profiles.