|
Thomas
|
September 5, 2015 at 9:48 am
Hi,
I am using EE 3.1.36.6.P
and we need to send confirmation emails to
o) the participant -> OK
o) the event mgmt -> OK
o) the hotel -> ?? how can this be done”
Is it possible to define additional confirmation emails for the hotel the participant is registering for?
I just found this post from 2012, but I am not sure if there are now more features now available after 3 years…:
https://eventespresso.com/topic/send-email-to-a-3rd-party-after-registration-in-addition-to-confirmation-email/
Thanks, Thomas
|
|
Tony
|
September 7, 2015 at 6:37 am
Hi Thomas,
That functionality is not available within EE3.
We completely re-designed how Event Espresso sends emails within EE4 giving you the ability to edit all of the emails within the admin and also edit where those emails are sent so this is possible with EE4.
However would the Hotel confirmation contain different information than the information sent to either the Event Admin or the Registrant? If so it would require some custom development to include another message type which would be sent to the Hotel on registration.
|
|
Thomas
|
September 7, 2015 at 10:49 am
Hi Tony,
Great to hear that this is feasible in EE4.
An update to EE4 prior to the big event coming up is not (yet) an option, so we have to take what EE3 can do.
Basically, the info sent to the event admin or the registrant would also be fine for the hotel. But how can I define such a third email being sent out?
I only know the two confirmations so far (admin and registrant).
Thanks, Thomas
|
|
Tony
|
September 8, 2015 at 9:14 am
In 3.1.36.X you can tell Event Espresso to send a copy of the event admin email to another email address using the ‘Alternate Email Address’
In 3.1.37+ that field was renamed to ‘CC Email Address’ because it actually sends a copy of the email, it does not replace the original.
http://take.ms/77liv
Add an email address there an an addition admin email will be sent to that address.
Will that work?
|
|
Tony
|
September 8, 2015 at 9:16 am
Just to note, WP introduced some security fixes within 4.2+ which causes problems with longer event and pricing names.
We included fixes for these within 3.1.37 so I would recommend updating to the latest version of EE3.
|
