Mass Email in Salesforce Lightning: What It Is, How It Works, and Where It Stops

TL;DR

Mass email in Salesforce Lightning uses the native List Email feature to send personalized emails to Contacts, Leads, and Person Accounts. It supports merge fields, email templates, basic tracking, and one-time scheduling, but applies sending limits and supports only standard recipient objects.

• Set up List Email from a list view or Campaign using Contacts, Leads, or Person Accounts as recipients.
• Understand the native sending limits, including the 5,000 external recipient daily cap and per-send recipient limits.
• Evaluate whether basic tracking, one-time scheduling, and standard object support meet your campaign requirements.
• Consider a Salesforce-native solution when you need higher sending volumes, custom object support, deeper reporting, or engagement-driven automation.

Introduction

Why do teams that search for "mass email in Salesforce Lightning" usually end up looking at a third-party app within a week? Not because the native feature is broken, but because its ceiling shows up mid-campaign, not during setup.

In Salesforce Lightning, native bulk sending runs throughList Email, the feature that personalizes sends to Contacts, Leads, and Person Accounts with merge fields, supports templates, and logs basic delivery data; all without leaving Salesforce.

This guide explains how List Email works in Salesforce Lightning, how to send mass emails, the native limits that apply, and what capabilities are available out of the box.

What is List Email in Salesforce Lightning?

List Email is the native Lightning feature that sends the same message to multiple recipients while personalizing each copy with merge fields from the recipient's record. Every recipient gets an individually generated email; addresses are never exposed to one another the way they would be in a CC'd group email.

It's one of several native paths Salesforce provides for bulk sending, built for everyday CRM communication rather than large-scale marketing campaigns, and it inherits Salesforce's native sending limits, tracking, and reporting covered in detail below.

List email vs mass email vs campaign email

Mass Email is the legacy Salesforce Classic name for the same underlying capability. List Email is the current Lightning implementation. Campaign Email isn't a separate Salesforce feature at all; it's shorthand for sending a List Email to Campaign Members through a Campaign record.

Salesforce's documentation also distinguishes betweenemailing a group with List Email and Mass Email, as shown in the comparison below.

Which objects support it - Contacts, Leads, Person Accounts, and why custom objects don't

List Email natively supports Contacts, Leads, and Person Accounts. Build your list view on one of these objects, since Salesforce treats Person Accounts as contacts for this feature.

If your recipients live on acustom object, Applications, Event Registrations, or Donors, then native List Email has no path to send directly to those records. You'd need to export them and match them to Contacts first, which is exactly the kind of manual workaround that breaks down as volume grows.

How to send a mass email in Salesforce Lightning (step-by-step)

List Email is Salesforce Lightning's native way to send the same personalized email to multiple recipients. Before you begin, make sure your recipients are organized in a Contact or Lead list view, or as Campaign Members, since these are the supported starting points for List Email.

You'll also need the"Allow sending of List Emails" permission on your user profile. Without it, the Send Email action never appears, regardless of which object or list view you're working from.

Step 1 – Build the list view

Start by opening a Contact or Leadlist view, or a Campaign containing the Campaign Members you want to reach. If you're working from Contacts or Leads, either select an existing list view or create a new one using filters that match your target audience. Taking time to define the right filters before sending helps ensure the email reaches only the intended recipients and reduces the risk of sending to outdated or irrelevant records.

Avoid using the default Recently Viewed list. This view simply displays records you've opened recently and isn't intended for email campaigns. Instead, build your audience using meaningful criteria such as lead status, owner, industry, campaign membership, or any other fields that reflect who should receive the email.

Step 2 – Select recipients and start a List Email

Once you've confirmed the correct audience, select the recipients you want to email. Salesforce lets you send a List Email to up to 500 recipients when using Select All from a list view, or up to 200 manually selected records. If your audience exceeds these limits, you'll need to divide it into multiple sends.

After selecting your recipients, click Send Email and choose Sales List Email. Salesforce opens the List Email composer, where you'll prepare the message before sending. If the option doesn't appear, verify that your user has the required permission and that you're working from a supported list or Campaign Member view.

Step 3 – Compose your email or choose a template

In the List Email composer, you can either write a new email or select an existingLightning email template. Templates help maintain consistent branding and messaging while reducing the amount of manual work for recurring communications. You can edit the subject line, message content, and other supported fields before sending.

If you're using merge fields, preview the email carefully before moving on. Blank values usually indicate that the template references a field that doesn't contain data for the selected recipients or that the merge field isn't appropriate for the recipient or related record. Catching these issues during composition helps avoid sending incomplete or incorrectly personalized emails.

Step 4 – Personalize the message and review attachments

List Email supports a merge field, allowing Salesforce to personalize each email with information stored on the recipient's record, such as a first name or company name. Although every recipient receives the same email, merge fields ensure each copy is generated individually using that person's Salesforce data.

You can also include attachments where appropriate. Salesforce shares attachments as downloadable links rather than embedding the files directly into every email. Before sending, confirm that any attached files are the correct versions and that recipients have the appropriate access if you're sharing Salesforce Files.

Step 5 – Review, schedule, and send

Before sending, use the Review page to check how your email will appear to recipients. Verify that merge fields resolve correctly, links work as expected, attachments are included, and the email content reflects the audience you've selected. A final review helps catch issues that are much easier to fix before the email leaves Salesforce.

When everything looks correct, choose whether to send immediately, schedule the email for a later date and time, or save it as a draft. If you schedule the send, it's good practice to review the recipient list before the scheduled time to make sure it still reflects your intended audience, especially if the underlying records change frequently.

Salesforce Lightning mass email daily limits

Salesforce doesn't apply a single email limit across all sending capabilities. Depending on how emails are sent, organizations may need to consider daily recipient limits, per-send limits, and edition-specific restrictions.

Understanding these limits can help teams plan campaigns more effectively and avoid unexpected sending issues when using native Salesforce email capabilities.

Limits by edition (Professional, Enterprise, Unlimited)

Salesforce applies email limits based on both your edition and the feature being used. Most Salesforce orgs can send emails to up to 5,000 external recipients per day, while Developer and Trial editions are limited to 10 recipients per day for Mass and List Email sends.

You may also come across a 15-recipient limit for Developer editions, but that applies to workflow-triggered email alerts, not List Email. Understanding which limit applies can help avoid confusion when troubleshooting sending restrictions or planning larger email sends.

What happens when you hit the limit

Once an organization reaches its daily email allocation, additional Mass or List Emails won't be sent until the limit resets. Salesforce calculates email limits using Greenwich Mean Time (GMT), which may differ from your local time zone.

Test sends also count toward the same daily allowance, so it's worth accounting for them when planning larger email sends. Keeping both recipient limits and testing requirements in mind can help avoid unexpected interruptions during time-sensitive communications.

The table below provides a quick overview of the most important restrictions and where they apply.

Understanding these limits can help teams plan email sends more effectively and avoid unexpected interruptions.

What List Email cannot do natively?

Native List Email includes several built-in capabilities for sending personalized emails in Salesforce Lightning. It's equally important to understand which capabilities are outside its scope. The following limitations relate specifically to email tracking, scheduling, and sender configuration.

Native tracking has limitations

Native List Email provides basic email tracking capabilities, allowing teams to understand whether recipients engaged with an email at a high level. Setting up and interpreting tracking information can also require additional configuration depending on reporting needs.

Salesforce doesn't natively use email opens or clicks to automatically trigger follow-up actions, which means engagement data isn't immediately connected to downstream automation.

Scheduling is limited

Salesforce Lightning List Email supports scheduling emails for a single future date and time. It doesn't support recurring schedules or emails triggered automatically by Salesforce record changes or predefined conditions.

Teams that require recurring, trigger-based, or event-driven communications should account for these limitations when planning their email processes. In such cases, capabilities such as outreach automation can support more flexible email workflows.

Shared sender identities and engagement automation require additional setup.

By default, List Emails are sent from the user who initiates the send. Organizations that want emails to consistently come from a shared or branded address must configure an Organization-Wide Email Address separately. Similarly, engagement-based automation isn't enabled automatically for native email tracking capabilities.

Teams that want recipient actions to initiate downstream processes must deliberately configure the appropriate workflows and automation. Organizations using shared sender addresses or engagement-based workflows may need additional configuration to align email sends with their existing Salesforce processes.

When native List Email is enough and when it isn't

Native List Email supports many common Salesforce email use cases. The examples below can help teams determine whether it aligns with the way they currently manage email communication inside Salesforce.

Native List Email is enough when:

• Your recipients are Contacts, Leads, Person Accounts, or Campaign Members.
• Lightning email templates and merge fields provide sufficient personalization.
• One-time scheduled sends meet your requirements.
• Your email process doesn't depend on engagement-based automation.

You may need more than Native List Email when:

• You work with recipients stored on custom objects.
• You need recurring or event-based email sends.
• Multiple teams manage email communication from Salesforce.
• Engagement data needs to trigger follow-up actions or other Salesforce processes.
• Your email processes involve multiple steps, approvals, or automated workflows.

Native List Email works well for simple, one-off sends to standard Salesforce objects. As soon as custom objects, recurring sends, or cross-team workflows enter the picture, you'll hit its limits. That's where MassMailer comes in, built to clear those limits while keeping everything native.

How MassMailer improves mass email in Salesforce

MassMailer is a Salesforce-native app that handles the gaps covered above: custom object recipients, recurring and triggered sends, and multi-step approvals. Sends, opens, clicks, and bounces log directly to the recipient's record, so marketing and sales work off the same engagement data instead of switching tools to compare notes.

Flow Builder gets a ready-made action "Email via MassMailer" that connects a list view and a template to a schedule or a record-triggered flow, so recurring or event-based sends no longer depend on someone remembering to click a button.

What changes in practice:

• Higher sending volumes become easier to manage. Campaigns are no longer limited by Salesforce's native List Email sending limits, making it practical to reach larger audiences without splitting sends across multiple days.
• Recipient engagement data is written directly to Salesforce records. Every open, click, and bounce writes back to the Contact or Lead record automatically, so a rep can see engagement history before picking up the phone instead of asking marketing for a report.
• Recurring and event-driven emails can be automated through Salesforce Flow. A weekly nurture email or a re-engagement send tied to a Flow Builder trigger fires on schedule without anyone opening a list view and clicking send by hand.
• Custom object recipients are no longer excluded. Teams tracking recipients on custom objects, such as Applications, Event Registrations, and Donors, can send directly to those records instead of exporting them and matching them to Contacts first.
• Engagement data can trigger follow-up actions. Opens, clicks, and other engagement data can feed Salesforce Flows to update records, assign follow-up tasks, or send additional emails automatically instead of relying on manual updates.

Quick Comparison Table:

The table below compares the core capabilities of Salesforce's native List Email and MassMailer for sending mass emails within Salesforce.

The two aren't really competing on the same axis. Native List Email is about staying inside Salesforce with zero setup; MassMailer is about staying inside Salesforce while removing the ceiling that native sending eventually runs into.

Conclusion

Native List Email provides a straightforward way to send personalized emails in Salesforce Lightning using list views, Campaigns, merge fields, and one-time scheduling. Understanding how its native capabilities and limits work together makes it easier to decide whether it aligns with your team's current email processes.

For organizations that require more advanced sending, tracking, or automation capabilities, Salesforce-native solutions such as MassMailer can extend those workflows while keeping email activity inside Salesforce.

Book a demo to see how MassMailer handles this inside your own Salesforce org.