You can use Versions in Email templates. That’s what I’m doing right now where I have the same content that needs to be sent out but two pieces of text vary depending on package purchased.

The ability to clone Versions helps, but it is essentially multiple copies of the same template.

More detail here:

 https://support.gainsight.com/Gainsight_NXT/Journey_Orchestrator_and_Email_Templates/Email_Templates/Create_and_Send_Multi-Version_Emails

I do versioning too ^ but you can also insert values created via case expressions in your query builder depending on what you’re looking to achieve.

I do this often because we have different Sender names/emails based on the account. So I create my case expressions in my query, then map it to the Sender fields in the mapping, and then I map the token in the template. Sometimes I don’t want to create another version if the content is the same but the only thing I’m changing out is sender information.

If you’re using query builder, create a case expression for the value you want to tokenize in your email template, and then map it (either as a standard field or custom field), and then you can insert it as a token in your email step.

Thanks @sarahmiracle , thats an interesting approach. Do you think it would work the same if trying to use the query builder to dynamic insert specific text in the body of the email itself (as opposed to the sender info)?

If you’re looking to do dynamic text, I’d suggest @darkknight ‘s approach instead, of creating email template versions. For example, I do this based on usage for a monthly newsletter we send our digital touch customers. If a customer has poor usage, we’ll target different resources in the newsletter than for a customer with high usage. This allows me to send customized copy to a customer based on a set of criteria I’m configuring in the “send email” step.