Browse guides
Guest list
Guest list is how you add comps without a fake €0 checkout. Each person is a real admission: they take stock, they can hold a numbered seat or standing place, and the door team finds them by name.
They are not customers. There is no buyer account, no Stripe or PayPal charge, and no refund. If someone will not arrive, you release the admission and the inventory comes back.
What you get
- A named party of 1–20 people on a standard ticket
- Optional ticket delivery email (or send the tickets to yourself)
- An internal staff hint, visible only to organizers and scanners
- Door search by guest name, companion name, or delivery email
- Walk-ins at the scanner for GA or standing (one person, checked in immediately)
- Numbered seats picked on the map; standing from a standing area
- Individual release of an unredeemed companion, including standing comps
- Move a numbered guest to another free seat of the same ticket
What you do not get
Guest list is not a second checkout. It does not auto-assign seats, sell group tickets, book whole tables, or let the scanner walk in numbered seats. Wheelchair and companion places stay paired.
Hidden 0€ promo codes are the wrong object. Use guest list.
Let guests sign up themselves
An event’s guest list has three views: Guests lists every party and says whether your team added it or which link it signed up through. Requests holds the signups waiting for you, with the number waiting. Signup links shows your links with their confirmation mode, ticket, companions and places taken.
Open Guest list → Signup links → New signup link on the event. Under Access, choose a standard ticket for general admission or standing, the Places through this link and the Companions per guest, leave Signups open on and decide whether to Review signups. Save, then copy the link. The shop and event must be published; unlisted events are supported.
Guests sign up on one mobile page, without an account or checkout. The page links to your privacy policy, and the privacy policy texts Usetix writes for you cover guest-list signups.
What guests are asked
Name and email address are always asked. Under What guests tell you, set Company, Phone and Companions’ names to Don’t ask, Optional or Required. Companions’ names are only asked when the link allows companions. Switch on Checkout questions to ask the event’s checkout questions that are asked once per order as well; questions asked per attendee are left out. A required question is required at signup unless you let buyers complete it later.
New links ask for the company optionally and nothing else, and links you created before work as they did. What a link doesn’t ask is not stored. When you approve a signup, its company, phone, answers and companions’ names go to the guest’s party, just as if you had entered them yourself, so the door team sees the companions by name.
Several links
Create another link for each ticket type or guest group. An optional internal name such as Press or Partners helps you tell them apart. Each link has its own questions, confirmation mode, companion limit and quota. New links start open; switch off Signups open to create a closed link. Existing closed links stay closed.
If a link reaches the wrong audience, open it and choose Renew link. Confirming immediately invalidates the old URL, including forms already opened by guests. Copy and share the replacement. Existing requests and tickets stay valid, and other links are unaffected. Under Requests, filter by link to review the right group.
Confirm or review
- Review signups on: the guest sees an acknowledgement. Owners/managers receive a notification. Open Requests, check the name, details, answers and party, and click Approve or Decline directly on the row.
- Review signups off: a valid signup creates the complimentary tickets and emails them at once.
Each person receives their own QR ticket, including companions. Pending requests reserve no places. Approval checks both the link quota and actual inventory. Closing the link stops new signups while keeping pending requests available for review. Declining does not send an email.
One signup per guest
A guest signs up once per event, across all of its links, and also when your team already added them with that email address. Signing up again creates nothing new: the page says You’re already signed up, and the guest receives an email with a link to their own signup page (or, when your team added them, their tickets again). The page reveals nothing else about the signup.
On their signup page, guests see whether they are on the list, can have their tickets sent again and can bring someone along, up to the link’s maximum, while the link takes signups. Before approval, the added people simply join the request. After approval, they get their tickets at once on a link without review; otherwise they wait under Requests next to the original signup until you approve or decline them. Approved companions get their own tickets, so tickets already sent never change. They count toward the link’s places.
Cancelled admissions free capacity, but the original signup stays reviewed. Use the existing guest-party edit/resend workflow for changes. Numbered seats continue to use the manual seat picker.
How to add a guest
Open the event, then Guest list. Hit Add guest.
| Field | Notes |
|---|---|
| Guest name | What the door team will search for. Required. |
| Ticket type | A standard ticket. On seated events it must be mapped to seats or standing. |
| Party size | One admission per person, up to 20. On numbered seats, each clicked place is one person. |
| Seats or standing | Click seats on the map, or pick the standing area when the ticket is standing-only. |
| Delivery email | Optional. Guests without an email are door-list only. |
| Staff hint | Optional. Shown to organizers and scanner staff only. |
Save. Inventory is taken immediately. Companions without a name show as “Guest of {name}” at the door.
At the door
Staff search the scanner by the displayed name. The staff hint is on the ticket. Walk-ins are Add walk-in: name, GA or standing ticket, then they are on the list and already checked in.
After you add someone
- Edit the lead name, companion names, delivery email, or staff hint
- Resend tickets when there is a delivery address
- Release one unredeemed admission, or remove the whole party if nobody has checked in
- Move a numbered seat on the same map. Apple Wallet updates if the pass is installed; email goes out only when a delivery address is set
Checked-in admissions stay. You cannot remove a party after someone has arrived; you can still release the people who have not.
AI, MCP, API and CLI
The in-app assistant, MCP, and the Guest list API share this same product. You can list parties, add GA or standing comps, pick numbered seats by their stable keys, update names, cancel, and move a seat.
They also configure signup links and review requests. For example, ask the assistant to open a link with manual approval, 50 places, up to two companions and a required phone number, then show pending requests. The shared manage_guest_list tool provides forms, form, create_form, configure_form, rotate_form, requests, approve_request and reject_request; signup_fields and ask_checkout_questions set what a link asks.
The CLI exposes the signup workflow through usetix events guest-list forms/create/form/configure/rotate/requests/approve/reject. --company, --phone, --companion-names and --ask-checkout-questions set what a link asks. Approval and rejection use the request ID and --yes; --json retains the API response fields. Manual party and seat operations remain available through usetix api.
Never invent seat keys. Ask the places tool (or GET the guest list JSON) first, then pass those keys. The API does not auto-assign seats.
Complimentary guest-list orders are not Stripe refunds. PrepareRefundTool ignores them on purpose.