🎟️ Ticketing & registration
Ticket types and pricing windows, promo codes, add-ons, custom questions, comps, caps and refunds.
Ticketing lives on the event hub. Ticket types themselves are created when the event is created (or cloned); everything that hangs off them — pricing windows, promo codes, add-ons, registration questions — is built through the ✨ Setup assistant on the same page.
✨ The setup assistant
Describe what you want in plain English, press Draft it, read the summary, and press Apply (or Discard). The placeholder shows the register it understands:
The draft is itemised before you apply it — each promo code with its discount, uses and expiry; each price schedule with its ticket type, price and start date; each add-on with its price; each form field with its kind, options and whether it's required. Read that list properly: it's your only review step.
💰 Pricing windows
A ticket type has one current price plus any number of scheduled changes. The price a buyer sees is whichever schedule is active at that moment, so early-bird-to-standard happens on its own at the time you set — no switch to flip on the day, and no risk of forgetting.
Describe it to the assistant the way you'd say it out loud — "in-person goes to $299 on July 1".
🏷️ Promo codes
| Discount | A percentage off, or a fixed amount off. |
|---|---|
| Scope | All tickets, or only named ticket types. |
| Max redemptions | A hard cap on total uses. |
| Expiry | A date after which it stops working. |
Buyers type the code into the Promo code box on the ticket card. An invalid, expired or exhausted code is rejected with an error rather than silently ignored, so people know to ask.
🎁 Add-ons
Optional paid extras — a workshop, a banquet seat, a t-shirt — shown as tick-boxes with prices under the buy form. Each add-on has a name, description and price, and the quantity follows the order. They land as separate lines on the receipt.
📋 Registration questions
Custom fields on the buy form, in four kinds: text, textarea, select (with a list of options) and checkbox. Each can be required, and each can be limited to specific ticket types — so "which workshop track?" only shows to in-person buyers.
Answers come out in the registrations CSV under 📊 Reports.
🔢 Caps, sold-out and the waitlist
A ticket type with a quantity cap shows its progress on the hub — · 84/100 sold — counting minted tickets plus live pending checkouts, so you can't oversell during a rush. Buyers see Only 16 left under 20 remaining, then Sold out with a Join waitlist form.
The hub shows the waitlist state per ticket type — Waitlist: 12 waiting · 3 invited · 1 converted — with a number box and a Release spots button.
- A refund or a cap increase frees up capacity.
- Enter how many spots to release and press Release spots.
- That many people are emailed an invitation, oldest first, and move to invited.
- When one of them buys, they move to converted. Invitations aren't reservations — releasing 5 spots to 5 people may convert 2, so watch and release more.
✉️ Invite-only tickets and comps
A ticket type set to invite_only is hidden from the public list. Its invite link is printed right under it on the hub — …/your-event?invite=… — and is the only way to see and buy that ticket. Copy it and email it to the people it's for. Anyone arriving through it sees the ticket outlined in the event color and labelled · invite.
Use it for member rates, press passes, speaker comps and exhibitor allocations. Combine a 100%-off promo code with an invite-only type and the result is a comp ticket you can hand out by link.
✋ The approve-then-pay queue
A ticket type can be marked approval-required — for student rates, member rates, press. The buyer submits a request and is charged nothing; the order sits as awaiting_approval in the Orders list on the hub with two buttons:
| ✓ Approve | For a paid ticket, opens a checkout session and emails the buyer "You're approved — complete your registration" with a payment link that expires in 24 hours. For a $0 order, mints the ticket immediately and sends it. |
|---|---|
| ✕ Decline | Cancels the order and emails the buyer a short note saying it wasn't approved, inviting them to reply if that's a mistake. |
🧾 Orders
The hub lists the 25 most recent orders with amount, any discount and the promo code used, the date, the status, and a link to the receipt. That's deliberately a working view, not an archive — for the full picture use the registrations CSV in 📊 Reports.
↩️ Refunds and what they cascade
Paid orders (except comps, which have nothing to refund) carry a Refund button. Pressing it refunds through the original payment provider. The rest happens when the provider's webhook lands, usually within seconds:
- The order becomes refunded.
- Every ticket on the order is revoked, and its QR key version is bumped — so any code already emailed or screenshotted stops scanning at the door.
- The tickets disappear from the holder's tickets page, and they lose ticket-gated video access.
- The freed capacity counts against the cap again, so you can release waitlist spots.