Currently, users are forced to select between either a contact property or a manually entered email address for an internal email recipient. E.g. - A scoring workflow sends a score notification message. It should be sent to an owning user (stored as a contact property), and to a shared mailbox, entered manually. One would reference the property, and the other be the manually entered address. "Send to: {{ contact.product_owner_email }},{{ contact.master_owner_email }},ScoreAlerts@WidgetCo.com" Why: In many cases, a user that should receive this kind of internal alert may be out of office, or otherwise unable to follow up on the internal email. There may also be instances where the property has no value on a given contact. Rather than have those internal emails fall into a "black hole", it would be beneficial to add a manual address to ensure the internal email is handled properly. Value: Timely responses to internal emails and ensuring the emails receive proper follow-up is difficult to give a value to. It will vary depending on how critical the internal email is. A score notification from a high-priority lead will have a different value than a weekly summary. While this idea applies to internal emails sent inside of workflows, the ideal resolution would be to allow contact properties to be used alongside manually entered email addresses wherever an address may be selected.
... Mehr anzeigen