Registration forms

Registration forms collect information beyond name and email. Use them when you need data to run the event, not to ask every possible question.

When you need a form

Examples of useful fields:

• Company or school
• Job title / role
• Dietary preference
• T-shirt size
• How they heard about the event
• Accessibility needs

Avoid long forms for free meetups unless you truly use the answers.

Form types

Depending on your workspace, you may create forms for:

• Registration / checkout: attached to tickets
• Speakers, sponsors, volunteers: intake outside the main ticket flow
• Feedback: after the event

This page focuses on registration forms guests complete when claiming a ticket.

Fields

Add field types such as text, email, select, checkbox, and others your workspace supports.

Conditions

Some forms support conditional visibility: show a question only when a previous answer matches. Use this to keep the form short (for example, ask “school name” only if they selected “Student”).

Notifications

Configure who gets an email when someone submits:

• The guest (confirmation)
• Organizers
• Custom addresses (operations inbox)

Test notifications with your own registration before launch.

AI help

Ask the assistant to draft a form from a short brief, then edit labels:

Copy

Draft a workshop registration form with company, role, and dietary fields. Keep dietary optional.

Attach the form to a ticket

Creating a form is not enough. Attach it to the ticket(s) that should collect those answers. Otherwise guests may register with name/email only.

1. Create the form

   Add fields and mark required ones carefully.

2. Attach to ticket(s)

   Link the form from the ticket settings.

3. Test checkout

   Register as a guest and confirm fields appear and save on the attendee record.