frequentix
Help centre

How frequentix works, for the people running the event.

Orientation guides for every part of the platform — the organiser console, your public storefront, and the Scanner and Box Office apps at the door. Enough to know what to expect; the console itself guides each step.

Help menu

Registration questions

Registration questions turn a checkout into a registration: dietary requirements, company and job title, session choices, consent boxes — asked at exactly the right moment, and required before payment.

Building the questions

The event’s Registration area: wizard steps with their questions, and a preview of what buyers will see.
Registration — arrange library questions into the steps buyers walk through.
  • Questions live in a shared library (Audience → Registration questions), so “Dietary requirements” is written once and reused across events.
  • Each event arranges questions into steps — pages of the wizard the buyer walks through.
  • A question applies per order (billing contact, heard-about-us) or per ticket (each attendee’s name-badge details), and can target specific ticket types — the VIP dinner question only appears when a VIP ticket is in the basket.
  • Conditional questions appear based on earlier answers — “Which allergy?” only after “Yes”.
  • A live preview in the console shows the wizard exactly as buyers will see it.

What buyers experience

After choosing tickets, the buyer walks the steps you built. Only questions relevant to their basket appear, and every required question must be answered before payment unlocks — an incomplete registration can’t become a sale.

Where answers end up

Answers attach to the order and to each ticket, visible in the console on the order record, in exports, and on badges where mapped. Per-ticket answers follow the ticket — reassigning it to a new attendee is the moment to collect theirs.