Design, Test, and Send Emails
Interactively design emails from scratch or from a template and send emails from the email content record. You can also preview and test your email before sending it.
Required Editions
| Available in: any Account Engagement Edition with Salesforce Professional, Enterprise, Performance, and Unlimited Editions |
- Considerations for Designing and Sending Emails
Review these considerations before using the enhanced email experience in Account Engagement. - Considerations for Using Handlebars Merge Language Fields in the Enhanced Email Experience
Some Handlebars Merge Language (HML) fields in Salesforce aren’t supported in Account Engagement. To use these field values, map custom fields from Account Engagement to existing Salesforce fields. Keep these scenarios in mind when you use HML fields in the enhanced email experience. - Create Enhanced Emails
Provide basic email information to create an email content record, and then build from scratch or edit existing email content. To make email creation even easier, Account Engagement offers email templates that help you reuse email designs. - Preview and Test Emails
Before sending your email, preview it as a specific prospect, and then test send it to troubleshoot personalization issues. You can send a test email to a test list or to individual email addresses. Test emails don’t include merge field data. - Send Emails
After you design your email content, define a campaign, an audience, tracker domain, sender options, and completion actions. - Reuse Email Content for List Emails
Edit and reuse existing email content to create and send new emails. Resend email content to different recipients and segments as unique list email sends. You can also view related email sends for specific email content. - Use Custom Components in Email
Marketers can use custom components to enhance their email templates and content by bringing in information and assets, such as surveys or event details, from third parties. Partners or developers can create custom components. Admins install custom components from an unmanaged package or via AppExchange. After a component is installed, a user can choose it when they build email content.
Did this article solve your issue?
Let us know so we can improve!
