Four Separate Ceilings — and Most Teams Only Know About One
Salesforce List Email — the Send List Email action available from any Contact or Lead list view in Lightning — is constrained by four independent limits. The 5,000 daily org-wide cap is the most cited. The 500-recipient per-batch ceiling, the 200-record manual selection cap, and the restriction to Contacts and Leads only are equally real. Understanding all four is essential for any team planning bulk email sending in Salesforce without mid-send surprises.
The Shared 5,000 Daily Org Limit
List Email sends draw from the same org-wide 5,000 daily mass email pool shared by campaign sends, Apex MassEmailMessage calls, and every other bulk sending method. According to Salesforce’s official email limits documentation, each recipient targeted in a List Email send consumes one slot from this shared pool. There is no separate List Email allocation.
A sales rep’s 2,000-contact list email in the morning leaves only 3,000 slots for marketing’s afternoon campaign — with no Salesforce alert when the pool is exhausted mid-send. For the rolling 24-hour reset mechanics, see Salesforce daily email limit.
The 500-Recipient Per-Batch Ceiling
Each individual Send List Email operation is limited to 500 recipients when “Select All” is used on a filtered list view. This is a per-operation UI constraint, not a daily deduction — it determines how many records a single send action can target, independent of how many daily slots remain.
Audiences larger than 500 require multiple sequential operations against filtered subsets of the same list view. A 2,000-contact audience needs at a minimum four separate Send List Email operations, each targeting a non-overlapping filtered segment. The Salesforce Mass Email from List View guide covers filter strategies for splitting large audiences into clean batches.
The 200-Record Manual Selection Cap
When users manually select individual records using checkboxes — rather than using “Select All” on a filtered view — the per-operation cap drops to 200 records. This is a UI-level constraint and cannot be changed through configuration or permissions.
Most high-volume List Email sends use “Select All” on filtered views rather than manual selection, so the 200-record cap is primarily encountered when teams cherry-pick specific records. For precise targeted sends, adding records to a Campaign and sending from the Campaign Members related list provides both the targeting flexibility and member status tracking. See how to send mass emails from Salesforce for a full method comparison.
Object Restrictions: Contacts and Leads Only
Native List Email in Lightning is restricted to Contact and Lead list views. Custom objects — students, members, patients, event registrants, donors — cannot be targeted with Send List Email. This is an object-level constraint, not a permission issue, and cannot be resolved through admin settings or configuration changes.
For organizations where a custom object is the primary audience — education platforms, nonprofits, event companies, healthcare providers — native List Email is not viable regardless of volume. An AppExchange-native solution with custom object support is required. For which methods support custom objects, see the bulk email in Salesforce guide.
List Email Tracking Gaps
List Email sends in Lightning provide only aggregate delivery data: total sent, total bounced. There is no per-recipient open tracking, no individual click data, and no engagement timeline per contact. As the Salesforce email reporting guide documents, List Email confirms delivery at the org level but provides no post-delivery engagement visibility.
Campaign-linked List Email sends can enable member status progression if an AppExchange tool writes engagement events back to Campaign Member records — but native Salesforce does not do this automatically. For contact-level open and click data from list sends, an AppExchange solution is required. See how to track emails sent from Salesforce for the full setup and gap analysis.
Going Beyond All Four List Email Limits
All four constraints share the same resolution: an AppExchange-native email solution that operates inside Salesforce but outside the native List Email infrastructure. MassMailer removes the daily ceiling, eliminates the per-batch cap, supports custom objects as send targets, and writes per-contact engagement data to Activity History and Campaign Member records. Clients like UMass Boston (16,000+ students) and Opal Group (custom event objects) exceed all four native List Email constraints without external platform sync.
Which List Email Limit Is Blocking Your Team?
Book a 20-minute call. We’ll identify which of the four List Email limits is affecting your sends, review your current setup, and show you exactly how MassMailer removes each constraint without changing your Salesforce workflows.
Key Takeaways
- List Email is subject to four independent limits: a shared 5,000 daily org cap, a 500-recipient per-batch ceiling, a 200-record manual selection cap, and a restriction to Contacts and Leads only.
- List Email draws from the same daily pool as campaign sends and Apex bulk jobs — there is no separate List Email allocation from the shared 5,000.
- “Select All” on a filtered list view supports up to 500 recipients per send; manually selecting individual records caps at 200 per operation.
- Custom objects cannot be targeted with native List Email, regardless of admin configuration — an AppExchange solution is required for custom object sends.
- List Email provides only aggregate delivery data (sent, bounced) — there is no per-recipient open or click tracking in native Salesforce Lightning.
- All four constraints are addressed by AppExchange-native email solutions like MassMailer, which operate inside Salesforce without the native List Email restrictions.
