header

Email Templates in Email Assist Vs Journey Orchestrator

  • 18 December 2019
  • 7 replies
  • 197 views

Userlevel 7
Badge +1

SFDC edition: Creating a running list of Email Assist email templates vs. JO templates.

  1. Email Assist: You can't specify the sender in the email assist. Email will be triggered with the name of person who triggered it.The use case would be mostly about sending from a generic email address (eg. customersuccess@abc.com) JO: You can.
  2. Email Assist: You can only add tokens that are in fields of CTA/Account/CustomerInfo/User objects in the email assist (you can't add opportunity fields right or any other object field in the email as tokens) JO: You can. 
  3. Email Assist: You can add cc to the email but it can't be a field (csowner, opp owner, account owner); JO: You can

 

However, I found out that there is a workaround for #2 to add associated fields in Email assist : Say you want to add a field from the opportunity object to an Email Assist

  • Step 1: Add a formula filed on the CTA object & using advanced formula you can populate it with any field on the opportunity object (eg Subscription ARR in below screenshot)

7 replies

Userlevel 7
Badge +1

Number 1 is a significant shortcoming for our use of Email Assist. 

Userlevel 5
Badge +1

We’d love to see the ability send email assists ‘from’ another user as well. Main use case - we have a survey sent ‘from’ the Team Manager, but would like a CSM to be able to trigger it on their behalf.

Userlevel 7
Badge

Thanks for sharing your learnings, @meenal_shukla ! 

 

Userlevel 7
Badge +1

@aditya_marla 

Userlevel 5

@katie_b  @meenal_shukla  @john_apple  for #2 is already planned and in progress. We will be releasing it soon.

Any intent to implement #1 to email assist? 

Userlevel 5

Hello @amy_perrin 

#1 ability to send email from another email address, work in progress, will update you about the availability date.

Reply