Variant Email Templates In Email Assist

@dan_ahrens @lila_meyer any update on this, given @nitisha_rathi has not followed up on the thread in 2+ years?

Now that the latest release allows for admins to control which templates are/are not available for CSMs to send from cockpit, we’d like to enable the feature. However almost all of our templates are variants - for both language and product differences in the messaging. 

Enabling this feature really won’t be helpful at this point, given this limitation. I’d have to duplicate each template with each single variation; with up to 12 per template that’s really not feasible.

Another product manager has taken up this feature area recently, so I’m reaching out to try and get an update here. 

This item is still under discussion by our product team. We’ll share a more specific update as soon as possible.

We definitely need this as we need to create different rules for  every CTA in every language that we support in different time zones

This is becoming more of a necessity for us as well. We love the ability  to send emails from cockpit but in a few current use cases we have to create the email with a 2nd (or more) versions for a program, but also want to make those versions available to send via cockpit. So now, we’re creating a combined email template for 1 send option and duplicating and offering the versions as separate templates for send from cockpit. It makes naming all of these templates a chore and leaves lots of potential for errors if someone grabs the wrong one.

Hello @katie_b , @steve_davis 

As we are planning to support variant selection in email assist i wanted to runt eh solution with you all and see if it solves most of your use cases.
Solution:  Manual approach.

Please see below for the quick overview of how will this option look like.

• User will be provided with a variant selection option when working with email task.
  • Use case 1:
    When user is sending email to 5 recipients and  all recipients of email need same email template variant[ I assume this is most of the use cases which we have today].With new solution user  can choose the email template variant from the drop down.
  • Use case 2:
    when user is  sending email to. 5 recipients, out of which 3 needs english variant and 2 needs spanish variant, in this case user has to send 2 emails one with english variant and another one with spanish.
    With new solution user has user can use adhoc email feature [documentation] where user can send email without having to create a email task. But once the email is sent email task will be automatically added to the respective CTA.
  • Use case 3:
    When user is sending emails to 5 different where all 5 require different variants. With new solution user has to send 5 different emails [adhoc emails] one for each variant.
  • Use case 4:
    For use case 2 & 3, another approach is create multiple email task as per language needed with language mentioned in the subject, user can work on them and choose the required variant as defined the task.
    Fo example: If CTA has 4 tasks, 1 of which is email assist, which requires  2 different languages,  playbook will be updated with an additional email assist for that second language, so CTA suddenly has 5 tasks.

Please let me know which of above mentioned use cases is the most frequently encountered. Feel free to provide your comments on the solution mentioned above.
 

This would be a great feature - our team is needing as well. We want to give levels of touch in an email task, depending on who it will be sent to. Adding the variant will allow the CSM to choose which template version is most applicable to the person they are reaching.

@chethana  Any idea on when this would go live?

Hello @andreammelde 

This is planned for this quarter. Can you provide your comments on the approach i have mentioned above.