Custom guest fields let you ask for information that is not covered by name and email alone. Use them for guest workflows where the extra data helps your team make decisions or run the event.
Keep custom fields focused. Every extra question adds friction.
Use custom fields for practical needs
Common guest fields include:
- Company or role.
- Dietary requirements.
- Accessibility needs.
- Session preference.
- Department or team.
- Plus-one information.
Only ask for information your team will review or use.
Match fields to the workflow
Different workflows need different questions. A VIP invite may only need dietary information. Open registration with approval may need company, role or motivation. A partner list may need an internal reference.
Do not reuse the same long form for every guest type.
Keep sensitive data under control
If a field collects sensitive or operationally important information, decide who can access it and how long it is needed. Avoid collecting sensitive data just because it might be useful later.
For public registration flows, make the question clear enough that guests understand why it is being asked.
Review responses before the event
Custom fields are only useful if someone checks the answers. Assign an owner before event day, especially for food, accessibility, approval or seating information.