we have a business scenario where we store an e-mail address on a custom entity. This record is associated to a contact. In a real time journey we have a custom trigger that is listening on the creation of such a record and sends out an email. But we dont want to send out the email to emailaddress1 of the contact but to the email address which is stored on the custom entity.
However, Please note that you cannot use more than one address field at a time, which means that the contact's default mailbox will not receive emails from the journey when you change to a custom mailbox:
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.