Email Templates

An email template holds the reusable message selected by a program’s email step. The subject and preview text explain the message before it is opened. The sender name, sender address and reply address tell the recipient who is contacting them and where a reply will go. Keep those details with the HTML body, text body and postal address so review covers the whole asset.

Marketing Manager checks the content version before approving it. A clear template code and name help Marketing Operations select the intended asset when building a journey. Similar subjects can hide different versions or senders, so compare the referenced template itself during program QA. Approval records a content decision; the connected sending service provides the result of the later send action.

• Prepare the asset. Record the author and required sender information with the message. Read the subject alongside the body and check the response route. Use representative lead details when previewing the message, including a lead whose contact information is incomplete.
• Request the decision. Submit the Draft through the template approval lifecycle. Marketing Manager reviews the version under review and approves it. The approval retains the deciding user and time, making it possible to identify which asset the manager accepted.
• Use the reference. An email step points to its selected template. Check that the asset is Approved and active before program review. An Archived asset has a different status; inspect existing step references when changing which content the team should use.

Marketing Manager agrees the sender identity, review responsibility and version to use. Marketing Operations checks how that asset fits the journey. Assign editing access deliberately and rehearse submission with the actual accounts that will prepare and approve content. Agree how changed wording returns for review before it reaches another audience.

Set up the email-send service connection and confirm how its result is correlated with the member’s execution history. Test the reply route and the lead identity used for merge data. Decide who investigates an error and what evidence they need before resuming the journey. Keep content review and the sending result distinguishable when discussing a problem with the program owner.

Prepare a webinar follow-up with a clear subject, a known sender address and the intended meeting invitation. Marketing Manager checks the Draft, submits it for review and approves through the lifecycle. Inspect the recorded decision and select that exact template on the email step. Compare the rendered message with the approved body and sender.

Rehearse a lead with an email address and another with no known address. Inspect the execution history and any error before continuing. Then test a suppressed lead and verify that the email action respects the global restriction. For a successful send, follow the connected service’s result back to the same member and template so the operator can explain what was sent.

• Email Templates Pending Approval — Content awaiting the manager’s decision, with sender, author and version.
• Approved Email Templates — Active approved assets with their deciding user and approval time.

Follow template approval and set up the sending connection.