Salesforce Email Templates: Setup Guide
Quick Summary:
Email templates let you send consistent, personalized emails using merge fields to pull in live record data — usable both for manual sends and triggered automatically from Flow or workflow automation.
What Is an Email Template?
An email template is a reusable message format with merge fields that automatically populate with data from the record being emailed — a contact's name, an account's details, a custom field value. Templates ensure consistent messaging while still feeling personalized to the recipient.
How to Create One
Go to Setup → Email Templates (Lightning) and click New Template.
Choose a template type — Lightning (recommended, drag-and-drop) or Classic (Text, HTML, or Visualforce).
Build the content, inserting merge fields wherever dynamic data should populate.
Save to an appropriately-shared folder so the right team can access it.
Test by sending to yourself or a test record before rolling out for team use.
A Real-World Example
A customer success team wants every new customer to receive a consistent welcome email, personalized with their name, account manager, and onboarding call link — sent automatically the moment their Account status changes to "Active." A single email template, triggered by a Flow email alert, replaces what used to require someone remembering to send it manually for every new account.
🚫 Common Mistake
Referencing the wrong object's merge fields for the context the template will actually be sent from. A Contact merge field won't populate correctly if the template gets triggered from a Lead-based automation — the object context has to match.
💡 Pro Tip
Build a small library of well-tested, properly-shared templates rather than letting every team member create their own ad hoc versions — consistency in outbound communication is genuinely worth the upfront organization.
Frequently Asked Questions
What\'s the difference between Classic and Lightning email templates?
Lightning email templates use a modern drag-and-drop builder with more design flexibility; Classic templates (Text, HTML, Visualforce) are the older format, still supported but not actively enhanced.
Can email templates include dynamic data from the record?
Yes, via merge fields, which pull live data (contact name, account details, custom fields) directly into the template when the email is sent.
Can email templates be used within Flow or Process automation?
Yes, both Flow and legacy automation tools can trigger an email alert using a saved email template, making templates reusable across manual sends and automated workflows.
Are email templates shared across the whole org by default?
No — templates are organized into folders with configurable sharing, similar to reports, so access can be restricted to specific teams if needed.
Can I A/B test different email templates?
Native Salesforce doesn't include built-in A/B testing for standard email templates — this typically requires a marketing automation tool (like Marketing Cloud or Pardot) layered on top.
Can attachments be included in an email template?
Yes, files can be attached to Classic email templates; Lightning templates support inserting images inline but handle file attachments differently depending on how the email is sent.
Why isn\'t my merge field populating correctly?
Usually caused by referencing the wrong object context (e.g. a Contact merge field used in a template sent from a Lead) or a typo in the merge field API name.
Can email templates be tracked for opens and clicks?
Native Salesforce email tracking (via Email Insights or similar) provides some visibility, but detailed open/click tracking is more robust in dedicated marketing platforms.
Can I create an HTML email template without coding?
Yes, Lightning email templates provide a visual drag-and-drop builder that doesn't require writing HTML directly, though direct HTML editing is still available for custom needs.
Can templates be personalized per record type or business unit?
Yes, by creating separate templates and organizing them into clearly labeled, appropriately-shared folders, teams can maintain distinct templates for different contexts.