|
kraaykraay
|
June 11, 2018 at 9:05 am
Hello, I had reviewed this thread (and his previous forum message) from 2015.
https://eventespresso.com/topic/double-emails-for-single-registrant/
Has there been an update to this?
We have events where we do ask for primary and secondary registrant info – and everything works as it should. We have other event where we just ask for the primary registrant details. In this case the Primary registrant gets both the primary and the regular registrant emails. Which is redundant.
Am I missing a setting that would prevent this?
|
|
Josh
|
June 11, 2018 at 9:10 am
Hi kraaykraay,
There has not been an update to this, but you can deactivate the Primary Registrant context and that will remove the redundancy. The Primary registrant will still get the Registrant email without getting the Primary Registrant email.
|
|
kraaykraay
|
June 12, 2018 at 2:31 pm
But if that is the case how do I ensure the primary registrant gets the ticket link that shows all of the tickets in the one email?
|
|
kraaykraay
|
June 12, 2018 at 4:08 pm
Okay, I have been playing with this and testing a few things. On 3 of the EE related sites I manage they all have regular events where either we don’t care who the additional registrants are or we do. So if we only had one method needed I think I could solve the problem. But this is not the case. Some instances exist where we need additional info from secondary registrants and some we do not.
I also realize we could use custom messages for each instance but I have run across issues with this because if a person buys using multi-event the system falls back on the default messages. So after having issues with this I am not going to rely on that as a viable option.
MY TESTS
Test 1:
- 1 event
- 3 tickets (same type)
- Secondary personal info requested
- Primary details used for all registrants
Results….
– 1 registrant and 1 primary registrant registration approved emails sent (3)
– 1 ticket notice is sent to registrant and includes the primary ticket (only 1)
– 1 ticket notice is sent to primary registrant includes all 3 tickets
Test 2:
- 1 event
- 3 tickets (same type)
- Secondary personal info requested
- Primary details used for 2, addition registrant used for 1
Results….
– 3 registrant and 1 primary registrant registration approved emails sent (4) – one of these has no ticket info due to it being the same as the primary info.
– 3 ticket notices sent to registrants and includes the primary ticket (only 1 for each registrant)
– 1 ticket notice is sent to primary registrant includes all 3 tickets
Test 3:
- 1 event
- 3 tickets (same type)
- Secondary personal info NOT requested, Primary Only
Results….
– 1 registrant and 1 primary registrant registration approved emails sent (3)
– 1 ticket notice is sent to registrant and includes the primary ticket (only 1)
– 1 ticket notice is sent to primary registrant includes all 3 tickets
Thoughts on these options?
1) What is I turned off secondary registrant emails and included a link in the registration approved emails to “all transaction tickets”.
Then I turn off the ticket email for the primary registrant and leave the ticket notice only for secondary registrants?
– or –
2) I turn off ticket notices all-together and add the “all tickets link” to the primary registrant “reg-approved” email and only the “registrant ticket link” in the secondary reg-approved emails.
It still means multiple emails for the primary if we do not need additional registrant personal info. A bit cleaner as each person gets one email. It’s still redundant for emails (but not as much) if the primary also takes the secondary reg sports with their info.
Thoughts?
|
|
Josh
|
June 14, 2018 at 12:35 pm
If it was my site I’d go with option 2. The ticket notice emails are redundant if you’re also using the Registration Approved emails. As you’ve noted, the Registration Approved emails can include the same content as the Ticket Notice email.
|
|
kraaykraay
|
June 15, 2018 at 2:40 pm
Thank you. I will keep checking for a resolution to the additional email for the Primary in cases secondary registrant details are not needed.
I will also implement the ticket code in the reg approved emails and take that ticket out of the equation.
Appreciated as always.
|
