Registration by email means a spreadsheet you build by hand, one forwarded message at a time. Names are misspelled, meal needs are lost and badges come out wrong. I would rather give every delegate the same questions in one link.
How it works
- The delegate gives a name, email, organisation and job title, so you can print a badge.
- They pick an attendee type and the days they will be there, so you can plan rooms.
- They tick the kinds of session they care about, so you can see which halls will fill.
- They choose a meal and describe any access need, so the venue is ready.
- They say whether they join the dinner and whether sponsors may see their name.
What a delegate's AI would ask
"What name should go on your badge?" Then "Which days will you attend?" Then "Do you have a meal preference?" The AI shows every answer and submits only after a yes. Read more about agent-fillable forms.
Good to know
This form records who plans to come. It does not take fees or issue tickets, so handle those on your own. For smaller breakout sessions, add a workshop registration form. For remote delegates, a webinar registration form works the same way. A pre-conference course fits a training registration form. More ideas are in forms for events.
Questions
How do I get a headcount for each day?
Download the CSV and count the rows that include each day in days_attending. It is a pick-all question, so one delegate can count towards several days.
Will sponsors see attendee details?
Only if you pass them on. The form has a box asking whether the delegate agrees to share a name and organisation with sponsors. Check that column before you export any list.
Can I cap registrations at the room size?
Yes. Set max_responses to your capacity and close_at to the registration deadline. The public form stops taking registrations when either point is reached.