> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tixfix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Registration form and custom questions

> Choose what information attendees provide and which answers show up at check-in

The registration form is what an attendee fills in at checkout. TixFix collects the basics automatically, and you add whatever else you need on top — meal choices, t-shirt sizes, accessibility requirements.

You configure it in the **Registration Information** block on the second step of the event wizard.

***

## Personal information

Three fields are built in and always present:

| Field | Label shown     | Status   |
| ----- | --------------- | -------- |
| Name  | `Full Name`     | Required |
| Email | `Email Address` | Required |
| Phone | `Phone Number`  | Optional |

The email address is where the ticket is delivered, so it is always required. If an attendee mistypes it, you can resend to a corrected address later — see [Resend a ticket](/attendees/resend-a-ticket).

***

## Custom questions

Custom questions are grouped under **Additional Information** and are scoped to the ticket categories you choose. A question applied to `VIP` only is asked only of VIP buyers.

<Steps>
  <Step title="Open the Registration Information block">
    It sits below the ticket category table on the **Almost There!** step.
  </Step>

  <Step title="Click Add Custom Form">
    A new question opens for editing.
  </Step>

  <Step title="Choose which ticket categories it applies to">
    The `Applied to:` control scopes the question. Pick one or more of your ticket categories.
  </Step>

  <Step title="Write the question">
    Phrase it as the attendee will read it, for example `What food type would you want?`
  </Step>

  <Step title="Choose the field type and options">
    For a dropdown, list the options the attendee can pick from — for example `Chicken`, `Veg`, `Fish`.
  </Step>

  <Step title="Mark it required if you need an answer">
    A required question blocks checkout until it is answered.
  </Step>

  <Step title="Turn on Shown when scanning if door staff need the answer">
    See the section below for what this does.
  </Step>
</Steps>

Each saved question displays a summary line — the field type, whether it is required, and whether it shows when scanning — followed by its options.

***

## Shown when scanning

A custom question marked **shown when scanning** surfaces the attendee's answer to your door staff at the moment they check that person in.

This is what makes meal choices and similar logistics work in practice: the person on the door scans a ticket and immediately sees `Veg` without looking anything up.

<Tip>
  Use it for anything a staff member acts on at the door — meal choice, drink package, session track, accessibility needs. Leave it off for information you only need afterwards.
</Tip>

See [Questions at check-in](/scanning/scan-questions) for what your scanners see.

***

## Collecting answers afterwards

Custom question answers are part of the attendee record and come through in the attendee export. See [Export attendees](/attendees/export-attendees).

***

## Keep the form short

Every extra required field is a chance for someone to abandon checkout. A practical rule: if you will not act on the answer, do not ask for it.