Registration & ticketing
Shorter forms. More completed registrations.
Show, require or hide any field based on what the registrant has already answered. Conditional logic runs on every field, every price and every follow-up question, so nobody scrolls past questions that do not apply to them.
The form
Each person sees only the questions that apply to them.
Fields that appear on an answer
Ask the dietary question only of people attending the dinner. Show, require or hide any field on any earlier answer.
Multi-step, save and resume
A registrant who stops at step three resumes at step three, on another device, a day later.
Accessible, from the first release
WCAG 2.2 AA on the public form, built in rather than retrofitted — so the most public thing you own works for every member you have.
Group registration
One payer buys a block of places and the names are filled in later, by whoever knows them.
Invitation-only and access codes
Create ticket types that only appear for people holding a code. For board meetings, press and sponsor allocations.
Waitlists that promote themselves
A cancellation promotes the next person automatically and emails them. Nobody has to watch the queue.
Transfers
Somebody always sends a colleague instead. One action moves the badge, the sessions and the attendance record together — no reprint, no refund-and-rebuy, no phone call to you.
Bulk import
Load a delegation or a sponsor block from a spreadsheet, including the one that arrives three days out.
Sensitive answers stay sensitive
Set permissions field by field. Dietary and accessibility answers stay hidden from staff who can otherwise see the registration.
Pricing the ticket
Early-bird pricing expires on its own.
Ticket types are products in one catalogue, and a price is a row with a window and an audience on it. That is why the rules compose instead of fighting.
Member pricing that reads the cart
Somebody joining as a member in the same checkout gets the member rate on the ticket beside it. One transaction, no phone call to the office.
A real zero is a price
A member rate of nothing is a decision, and the pricing ladder treats it as one. Small detail, and the reason your comped tiers never quietly charge full price at checkout.
Comps, promo codes and discounts
One discount engine across tickets, booths, sponsorships and merchandise. Build a code once and it works everywhere.
Add-ons in the same cart
Workshops, the dinner and merchandise go in the same cart as the ticket. One transaction to reconcile.
Who they are
Register in one step, with no password to create.
They register, and the identity resolves from the email afterwards. Nobody abandons at the last step because they cannot remember a password they set eleven months ago.
Two registrations by the same person resolve to one record, whether they are a year apart or at two different organizers’ events. Nothing to merge by hand later.
And when they come back
There is no password to have forgotten.
Sign-in is a link sent to the address they registered with. Nothing to remember, nothing to reset, nothing to steal.
Your support inbox stops receiving password resets in the week before the event.
And then the badge
Decide what triggers a badge.
Paid, confirmed, approved by a reviewer, or pending an ACH that has not settled — you set the trigger, per ticket type. Nobody walks your door on an unpaid registration unless you decided they could.
Whatever you choose, the credential stays tied to the live roster. Cancel a registration and that badge stops working, with nothing reprinted and nothing to collect back.
What happens at the door →How many questions is your registration form?
And how many does every registrant see whether or not they apply? That gap is usually worth a few points of completion.
hello@fieravents.com