In response to feedback from partners, our improved registration workflow streamlines the registration process and makes registering for events faster and easier than ever.
The basics:
- Registration is now combined into one single, dynamic step.
- The term “Guest” has been replaced with “Attendee” and attendees are now added with the click of one button
- Note: This update only impacts the user-facing registration process; there are no changes to how events are built, the information collected during registration, or event reporting/API.
See the updated registration flow in action:
View our walkthrough of the updated registration experience.
Updated registration flow:
- The first step of the event registration process is called 'Your Information'. On this step, the registrant will begin by completing the fields added to the “Registrant Form”.
- Next, the registrant (the person filling out the registration form) will indicate if they plan to attend the event or if they are registering on behalf of someone else.
- If the registrant is attending the event, they will be counted as one attendee and will be prompted to complete the fields added to the "Registrant Form" AND “Attendee Form” (shown as one)
- Example of if registrant is attending below -
- Example of if registrant is attending below -
- If the registrant is registering on behalf of someone else, they will not be counted as an attendee and will be prompted to complete only the fields added to the “Registrant Form” and then the 'Attendee fields' for each attendee they add.
- An example of if the registrant is NOT attending below -
- An example of if the registrant is NOT attending below -
- If the registrant is attending the event, they will be counted as one attendee and will be prompted to complete the fields added to the "Registrant Form" AND “Attendee Form” (shown as one)
- If the event allows multiple guests per registration, registrants can keep adding attendees until the maximum number is reached.
- Finally, the registrant will select a ticket for each attendee.
If tickets are restricted by a registrant’s affiliation, the registrant must first select an affiliation before choosing a ticket type. The available tickets will then be displayed based on the affiliation selected.
If tickets are restricted by each attendee’s affiliation, the registrant must select an affiliation for every attendee before choosing a ticket type. The available tickets for each attendee will be displayed according to the affiliation selected.
Frequently asked questions:
Q: Are all events on the new registration flow?
A: Yes
Q: Will this update change or break any of the custom registration fields added to my event?
A: No, this update will not impact the fields on the registrant or guest forms; only the way in which they are displayed.
Q: What impact will the improved registration flow have on custom reporting or the events / event registrations API?
A: There are no changes to custom reporting or the events APIs as part of this registration flow update.
Comments
0 comments
Article is closed for comments.