Salesforce sends bulk email natively through List Email in Lightning and Mass Email in Classic, both capped at 5,000 sends per org per day on a rolling 24-hour window, with up to 500 recipients per send and no built-in open or click tracking. That 5,000 cap is identical on Professional, Enterprise, and Unlimited, so upgrading editions adds no volume. For higher volume, engagement data, and stronger deliverability, a Salesforce-native app like MassMailer clears the limits while keeping data in the CRM.

Sending Mass Emails Through Salesforce Setup, daily caps, and how to scale

Introduction

Sending mass emails through Salesforce sounds simple until your campaign stops at 5,000 recipients, or you open the report and find no way to see who actually read it. Salesforce does send bulk email to leads and contacts natively, through List Email in Lightning and Mass Email in Classic.

However, both tools carry a hard daily cap, a 500-recipient ceiling per send, and almost no engagement tracking. For an internal note, that works fine. For real marketing campaigns, those limits decide whether your send lands or stalls halfway.

This guide walks through how to send bulk email in Lightning and Classic step by step, the exact limits for each email type, and how to scale once your list outgrows what Salesforce allows.

List Email vs Mass Email: what each one does

They are the same feature under two names. When Salesforce moved orgs to Lightning Experience, it rebranded Mass Email as List Email, so the label you see depends entirely on your interface. Classic shows Mass Email. Lightning shows List Email.

Each send delivers an individually addressed copy of one email to every recipient on your list. So every contact receives their own message, Salesforce resolves merge fields per record, and personalization like first name or company renders correctly.

Recipients never see each other, and the platform meters each copy against your daily allowance, which the limits section below explains in full.

Both tools share one important boundary: they only pull from Lead and Contact records. So if your audience lives on a custom object, native sending cannot reach it, and you will need an AppExchange app or an Apex solution instead.

Before you build anything, confirm which object holds your list. For a closer look at the Lightning workflow, the send mass email in Salesforce Lightning guide breaks the interface down screen by screen.

How to send bulk emails in Salesforce Lightning (List Email)

You send a List Email from a Lead or Contact list view rather than from a single record, so the setup begins before you ever click send. Follow these steps in order.

1. Confirm access and deliverability first

Before the button even appears, an admin opens Setup, types Deliverability into Quick Find, and sets Email Deliverability "Access level" to All emails under Setup → Email → Deliverability. Next, your profile or permission set needs the "Allow sending of List Emails" permission.

When either piece is missing, the Send List Email button stays hidden or greys out, which is the single most common reason teams cannot find the feature.

2. Build a filtered list view

On the Contacts or Leads tab, create a list view that defines your audience. Then add two filters on every campaign: "Email Opt Out equals False" to honor unsubscribe compliance, and "Email not equal to blank" so empty records never burn your daily allowance. Save the view, and set its visibility so the right users can reuse it.

3. Select your recipients carefully

Open the list view and choose who receives the send. Select All on a filtered view includes up to 500 recipients in one send. However, when you tick individual checkboxes instead, Salesforce caps the selection at 200. So for anything above 200, filter the view down and use Select All rather than hand-picking names.

4. Compose the List Email

Click the dropdown caret beside the list view buttons, then choose Send List Email. Now add your subject line and body, insert merge fields for personalization, and attach any files you need. To keep branding consistent across sends, drop in a reusable layout from the email template builder instead of rewriting copy each time.

Click Send to deliver immediately, or select Save for Later to set a future date and time. Scheduling lets you land in the inbox during a weekday morning, when open rates tend to peak, without sitting at your desk to hit send.

Test the send before going full volume

Before a full send, point the list view at a few internal records and email yourself a test, so a broken merge field surfaces before 500 people see it. By default, List Email goes out from your personal user address, though you can pick a verified org-wide email address when one exists, which keeps replies flowing to a shared inbox.

Once the send completes, Salesforce records an HTML status report that shows which copies were delivered and which failed. Keep the 500-per-send ceiling front of mind, because a 4,000-contact campaign turns into eight separate sends. So at mid-size volume, the manual repetition adds up quickly, and the limits below explain exactly why.

How to send mass emails in Salesforce Classic

In Classic, the workflow starts from a tab button rather than a list view action. For contacts or person accounts, open the Contacts or Cases tab and click Mass Email Contacts. For leads, open the Leads tab and click Mass Email Leads.

From there, Classic runs a short wizard. First, pick an existing list view to define your recipients, then review the list and clear anyone you want to skip. Next, choose an email template, because Classic requires one.

You cannot type the body at send time the way Lightning allows, so build and save your template under Setup → Email → Email Templates beforehand. After that, set the processing options, decide whether to send now or schedule a delivery date, and confirm.

Classic Mass Email draws from the same daily org allowance as Lightning, so switching interfaces never resets or raises your volume. When your org already runs Lightning, use List Email and treat Classic as the legacy path.

Salesforce mass email limits and the daily sending cap

Salesforce caps mass and list email at 5,000 sends per organization per day, and that ceiling holds no matter which edition you run. According to Salesforce Help, Professional, Enterprise, and Unlimited all share the same 5,000 daily mass email limit.

So upgrading your edition buys more storage, more automation, and more users, yet not a single extra mass email. Teams that budget for an upgrade expecting higher volume are often surprised here.

It helps to separate the counters before you plan a campaign:

Email typeLimitScope
Mass Email (Classic) / List Email (Lightning)5,000 per dayPer org, shared across all users and automations
Single emails to external addresses5,000 per dayPer user
Recipients per List Email send500 (Select All) / 200 (manual)Per send
MassEmailMessage API call250 recipientsPer call
Developer sandbox15 per dayPer org (test safeguard)

Mass and list emails share one 5,000 org-wide pool, while single emails to external addresses run on a separate 5,000-per-user pool. Automated sends through the MassEmailMessage API draw from the same mass pool at 250 recipients per call, so heavy Apex jobs eat into the budget your marketing team also uses.

The rolling 24-hour window

Beyond the headline number, the mechanic that quietly breaks campaigns is the rolling 24-hour window. Salesforce does not reset the counter at midnight. Instead, it ties every send to its own timestamp and restores that capacity exactly 24 hours later.

So when you send 5,000 at 8 AM, your allowance returns at 8 AM the next day, and any afternoon follow-up simply will not leave the queue. Plan sends against that rolling clock, because the calendar date gives you a false sense of headroom.

The Salesforce email limits apply at the org, user, and per-send level all at once, so the lowest ceiling you hit first is the one that actually stops your send. One correction is worth making, since the SERP still surfaces it: older guides claim 250 emails on Professional, 500 on Enterprise, and 1,000 on Unlimited. That tiering described an outdated single-email rule and no longer reflects mass email today.

Salesforce does not surface a simple running meter for the shared mass email pool, so track your own sends and avoid stacking large campaigns on one day. When the org reaches the cap, additional sends fail instead of queuing, and everyone in that batch receives nothing, with no automatic retry.

So sequence your largest campaigns first, early in the window, and leave headroom for the automated alerts and transactional mail that draw on the same pool.

Where native sending falls short: tracking, scheduling, scale

Native Salesforce sending confirms a copy was left in your org, yet it tells you almost nothing about what happened next. List Email's status report shows delivered or failed, and a little more. So opens, clicks, replies, and conversions stay invisible unless you add Account Engagement (Pardot) or a third-party app. That blind spot matters more than it first looks, because measurement is what turns a one-off send into a program you can improve.

The stakes are real. Litmus' 2025 CMOs' Guide to Email Marketing ROI puts email's return at $36 for every $1 spent, higher than any other channel. However, you only capture that return when you can see which subjects, segments, and send times actually perform.

Take tracking first: without open and click data on the record, your sales team cannot tell whether a lead engaged before a call, and your marketing team cannot score or segment on behavior. That gap compounds for B2B teams, where a single opened email can signal buying intent that your reps need to act on within hours.

What breaks as your volume grows

The same ceiling shows up in four practical ways:

  • The 500-recipient ceiling turns a mid-size list into a dozen manual sends.
  • The 5,000 daily cap stops a single large campaign before it finishes.
  • Scheduling stays basic, with no native A/B testing or send-time optimization.
  • Deliverability rides on Salesforce's shared infrastructure, so inbox placement depends on a reputation you do not control.

Reporting feels the same ceiling. Because List Email never writes opens or clicks back to the record, Campaign influence and email ROI reports have nothing behavioral to read, so attribution stops at sent. Scheduling stays just as bare: you can pick a future time, yet there is no holdout group, no automatic winner selection, and no send-time optimization, so every A/B test becomes a manual build-measure-repeat loop.

Bounce handling is another quiet gap, since native sends flag hard failures yet never suppress repeat offenders automatically. Worse, Salesforce counts every attempted send against your cap, whether it bounces or not, so a stale list quietly wastes your daily allowance too. So a dirty list keeps hurting your sender score with every campaign.

To close the visibility gap, most teams add a way to track emails in Salesforce and a plan to authenticate the sending domain with SPF, DKIM, and DMARC. Native sending fits internal announcements well, while marketing campaigns outgrow it fast.

How to send unlimited, tracked mass emails from Salesforce

To clear those limits without leaving Salesforce, switch from the built-in tools to a Salesforce-native sending app. MassMailer is one such app. It installs directly inside your org and sends from your live Lead and Contact records, so your CRM stays the single source of truth.

There is no external platform to sync and no second database to maintain, which keeps your data and your permissions exactly where they already live.

The difference shows up precisely where native sending runs out of room. MassMailer sends past the 5,000-per-day ceiling, so a large campaign goes out in one motion. It writes opens, clicks, and bounces straight onto the Salesforce record, so engagement sits next to each contact for scoring and reporting. On top of that, it verifies addresses before a send, builds templates without code, and supports dedicated IP warm-up so high-volume campaigns reach the inbox.

For teams that have outgrown List Email, a purpose-built mass email marketing for Salesforce app removes the volume, tracking, and deliverability limits together, while keeping the workflow your admins already know.

Conclusion

Sending mass emails through Salesforce comes down to three decisions. First, choose your interface: List Email in Lightning or Mass Email in Classic. Next, plan around the 5,000-per-day rolling cap and the 500-per-send ceiling so no campaign stalls midway.

Finally, decide whether native tracking is enough for what you need to measure. For a quick internal note, the built-in tools deliver. For marketing campaigns that need volume, engagement data, and reliable deliverability, they hit a wall fast.

That is where a Salesforce-native app like MassMailer fits, clearing the caps while keeping your data inside the CRM. Start a free MassMailer trial and send your next campaign to the full list, with every open, click, and bounce tracked on the record.