Use Contact's Email 1 and Email 2 field in Communication Triggers
As a business who generates a lot of reminder emails from Administrate, it would be useful if they could go to home and work emails in the Contact, utilising both Email 1 and Email 2 fields.
-
Many people provide both work and personal email addresses. We don't always know which one they use most often or will get the best response. Exposing email 2 in addition to email 1 would be a big help. We would like the option of sending to both emails using the same trigger.
Thanks
Brad
-
This is a very sensible addition. We are currently using the email 2 for the 'bookers' email as sometimes we don't have a personal address and we need at least some way to communicate since the warning for duplicates emails exists, and more importantly there still isn't a way to book a named delegate on with a booking contact, its still either/or and not both which it really should be.
-
Oh crikey Julie - being new to using this system and now starting to add our IHT events to the system, I hadn't realised if you added a Booker Contact you can't add named delegates....
How do you get around that with your communication triggers when using 'Booking Contact' to send key event details/request to the booker vs. notifying the instructors who's attending?
Thanks,
Lindsey
-
FAO Product Team: this was also recently raised in another Idea, of which has since been closed and the customers been asked to partake in this particular Idea (with more votes).
-
We're looking into this one now. We've noticed that 2 separate issues were intertwined here.
1) There is a request to use the primary email field as a merge field.
This is pretty straight forward, and we're looking into adding that now.
2) Being able to send communication triggers to an alternate email on a contact, or to several emails on a contact.
This will take a bit more design and thought, but we're looking at it to see what we can do.
-
I like to think it is a Email1 and/or Email 2. I agree it is a 'nice to have' as I'm currently sending emails with a workaround. I think it is mentioned before but we actually come across it quite often as we deal with a reseller/end user or another 2nd party who wants either to forward the emails themselves or at least want to know about it.
Please sign in to leave a comment.
Comments
12 comments