Branch by ticket type
Ask the ticket or attendance type as a multiple choice question and route each option to its own section. Speakers, sponsors, and general attendees get three different forms behind one link.
An event registration form turns interest into a headcount. It collects who is coming, which parts of the event they are attending, and everything the venue and catering need to know, in one pass, before the day.
Not a stock template. Build it in a few minutes from a blank form, or describe it and let AI draft the questions on a paid plan.
Registration forms get long fast, because every ticket type has its own follow-up questions. Branching is what keeps them short: a day-pass attendee never sees the accommodation questions, and a speaker sees a section nobody else does.
A starting point, not a rulebook: every question below is a real Questionful question type, and all of them are editable once the form is in your account.
| Question | Question type |
|---|---|
| Full name | Short answer |
| Email address Turn on the emailed copy so it doubles as a confirmation | Short answer |
| Company and job title | Short answer |
| Which ticket type do you need? The branching question | Multiple choice |
| Which sessions will you attend? | Checkboxes |
| Which day are you joining? | Dropdown |
| Dietary requirements With an "other" option for the long tail | Checkboxes |
| Do you need accessibility support? | Paragraph |
| How did you hear about the event? | Dropdown |
Ask the ticket or attendance type as a multiple choice question and route each option to its own section. Speakers, sponsors, and general attendees get three different forms behind one link.
Turn on "email a copy to the respondent" and write the confirmation message on the form. The registrant leaves with a record of what they signed up for.
Enable editing after submit and link the registration to a follow-up form, so a change of session choice does not become an inbox thread.
Export the registration list to CSV for the venue, and push each new signup to Zapier or Make so it also lands in your CRM or a spreadsheet.
Yes, if you enable the emailed copy on the form. The respondent receives their answers along with the confirmation message you have written, so the form itself is the receipt.
Not today. Questionful does not take payments. The usual pattern is to register for free and send a payment link from your invoicing or ticketing tool, triggered by the webhook the form fires.
Yes. Turn on "allow editing after submit" and the confirmation link lets them go back and change a session choice or a dietary note.
There is no automatic quota yet. You close the form manually when you reach capacity. The usual approach is to watch the response count and close it a little early.
Public link, embed on your site, email to a list, or export standalone HTML.
FeatureRoute each answer choice to its own section, so people only see what applies.
FeatureEvery response POSTed as JSON to any endpoint, signed if you want it.
TemplatePost-event ratings, session scores, and open comments.
TemplateConfirm who is coming, plus guest counts and dietary notes.
TemplateLet people tick the slots that work and read the winner off the chart.
Use caseTake registrations for workshops, webinars, and meetups: with the details you need, collected once and exportable.
Unlimited forms and 100 responses a month, free. Paid plans from €19.
No credit card required.
Choose which cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.
Required for core features such as security, load balancing and remembering this cookie choice. These set no tracking cookies.
Google Analytics, used to understand traffic and improve the site. Loaded only if you allow it.