|
pawmedia
|
May 14, 2020 at 2:16 pm
Is there a reason why the registration UI doesn’t make it clear that the first attendee is also meant to be the primary registrant? I’m referring to the scenario when you are collecting information from each attendee. Hoping I’m just missing something. Thanks!
|
|
Tony
|
May 15, 2020 at 4:46 am
Hi there,
We didn’t add details on the registration page as a ‘primary registrant’ doesn’t apply to everyone using Event Espresso.
Yes, there will always be one and yes, it will always be the ‘first’ attendee currently but that doesn’t necessarily make a difference depending on your use case.
May I ask what you are looking to add to that section?
|
|
pawmedia
|
May 15, 2020 at 7:39 am
Not looking to add anything to the section, but it would be great to make it clear that the information added to the “first attendee” section will be the primary attendee (who will receive primary attendee notifications). I’ve had cases where a family registered for an event where we were collecting information for each attendee in a purchase. Since it wasn’t clear that the first attendee was the primary, some purchasers would start with a random family member in section one and their 14 year old child would get emailed their payment receipt. Am I missing something?
|
|
Tony
|
May 15, 2020 at 9:13 am
I don’t know, but this is the first report we’ve had of users randomly entering details in the registration form meaning a random attendee was then used for the Primary Registrant.
One option to add some details to the primary registrant section without any code is to use an empty question group, set a description on the group and include it within the Primary Registrant question groups on the events.
Like so – https://monosnap.com/file/26XqM6hVEs9cgXtGC41X2fmFPgSWDQ
Reg form – https://monosnap.com/file/PKRmDFw4LCxUGo6ve0yXsGVMECSL5k
Does that work for you?
|
|
pawmedia
|
May 15, 2020 at 9:39 am
To clarify, I’m not saying that EE picked a random group member to be the primary attendee, I’m saying that the purchaser doesn’t get any guidance that they should enter the primary attendee in the first attendee section. It should somehow be clear that whoever gets typed into attendee #1 will get the primary registrant emails.
While I think the UI could be a bit clearer out of the box, your suggested workaround seems to work fine. Thanks!
|
|
Tony
|
May 15, 2020 at 9:55 am
To clarify, I’m not saying that EE picked a random group member to be the primary attendee, I’m saying that the purchaser doesn’t get any guidance that they should enter the primary attendee in the first attendee section.
I understand but again this is the first report we’ve had of users entering data into the registration form in a seemingly random fashion. So most users must be entering the details in a way that, to me makes logical sense, entering the main/primary/first registrant first and then any additional registrants after that.
I know EE doesn’t randomly select a Primary Registrant, it is always the first attendee on the form and that’s intentional.
It should somehow be clear that whoever gets typed into attendee #1 will get the primary registrant emails.
Ok, and when the primary registrant emails aren’t used that message causes more confusion.
Whilst the above likely reads that I’m against adding any kind of message, I’m not, but the point is there is a balance we need to keep to fit the most us cases.
While I think the UI could be a bit clearer out of the box
If you let me know how you prefer this was out of the box I can pass that feedback along, I can’t say that it will be implemented but we do take on any feedback given and discuss what we can do with it internally.
|
|
pawmedia
|
May 15, 2020 at 11:31 am
I guess it would seem to make sense that when questions in the personal information group are enabled for additional registrants, then the “attendee 1” section should be noted as the “primary registrant” or “ticket purchaser” or “attendee 1 – will receive payment receipt”. Something simple to make it a bit more clear that attendee 1 shouldn’t just be a random person from the purchasing group’s list.
This became a bit of an issue for us when we sold ~650 tickets to a high priced event where many of the purchasers were buying tickets as gifts ahead of the holidays. Some of the attendee that were supposed to be surprised on Christmas were instead surprised when they received the payment receipt.
|
|
Tony
|
May 18, 2020 at 6:12 am
I guess it would seem to make sense that when questions in the personal information group are enabled for additional registrants, then the “attendee 1” section should be noted as the “primary registrant” or “ticket purchaser” or “attendee 1
Currently, we can’t automatically change the text to contain purchaser as some users already have EE set up so that Attendee 1 is not the purchaser. They do that using a custom question group on the primary registrant and then pull the answer to those questions into the message system to send the emails wherever they should go.
We may be able to add an option somewhere to change the text when checked but I’ll open a discussion with the rest of the team.
This became a bit of an issue for us when we sold ~650 tickets to a high priced event where many of the purchasers were buying tickets as gifts ahead of the holidays. Some of the attendee that were supposed to be surprised on Christmas were instead surprised when they received the payment receipt.
Thank you for the additional details, I’ll add this to the ticket.
|
