The new Event Registration Form should allow event options to be selected even if there are not enough registrants entered prior to selection.
because the end user does not necessarily know that they are going to need to create 10 guests BEFORE they are able to select an option for a table of 10, there is the possibility that the process will be frustrating for the end user (especially since there is the ability to add attendees later in the process).
-
Julie Stone
- May 4 2018
- Reviewed: Voting Open
Related ideas
What matters the most is that the user purchases a table, and not that they detail their guests information on the date of purchase. Let us do the work in confirming with the donor who their guests will be. This form puts all the work on the user and that's not something our organization is okay with.
There needs to be a better way for people to buy a table before they know all of the names of the people that will be coming with them to the event. Not sure why this functionality was taken a way and why.
How is this form supposed to support a benefit event where a table is purchased? This seems nearly impossible as designed. There is no way a user is going to fill out 10 individual registrants, unknown guest or otherwise, prior to selecting an option for a table of 10 registrants. This is VERY important to us. This new form is taking away functionality we were previously allow via layering the form with some JS.
Common feedback on this form is that the logic is backwards. Users should be able to select the event(s), then the number of tickets, then fill out the attendee's names (if known) or set to "unnamed guest".
The whole process of this new registration form is counterintuitive - guests shouldn't be forced to put in names before picking their options. We often sell tickets to donors who don't exactly know who all their guests will be at time of purchase. I think many people will find it frustrating to put in the guests names they do have and then not be allowed to buy the number of tickets they want.
There's the possibility of donors registering and when faced with having to fill in guest names, would choose to fill in their own name or names of random friends. CRM doesn't allow multiple registrations for the same person, so the person using their own name would except out of batch and if one or more of the friends were registered as the guest of another person, they would except out.
First of all, this is just backwards to have to enter guests before you event chose an option. Secondly, this will keep folks from signing up and paying early. Some guests never even fill their 10 seats, so this doesn't work for them either. You really should consult your users before releasing something like this.