How to Send Mass Emails from Salesforce: List Email, Campaigns & Beyond the 5,000 Limit

Salesforce includes native mass email capability — but it works differently depending on which method you use, and all of them share the same daily ceiling. Whether you're a sales rep targeting 300 leads from a list view or a marketer sending a campaign to 4,000 contacts, the steps, template requirements, and tracking behavior differ by method. Knowing these differences before you send prevents two costly outcomes: sends that fail silently because the limit was already consumed, and campaign reports showing zero engagement because setup was incomplete.

For a conceptual overview of bulk sending and its constraints, see bulk email Salesforce. For the limit rules and how the rolling 24-hour window works, see Salesforce mass email limits.

The Three Native Mass Email Methods at a Glance

Salesforce provides three native routes for mass email. As Salesforce Trailhead documents, List Email in Lightning replaced the Classic Mass Email interface — but the shared limit structure applies to all three:

  • List Email (Lightning): Send a personalized template to up to 500 recipients per batch from a filtered Contact or Lead list view. Requires the 'Allow sending list emails' permission set by an admin. Supports merge fields, Lightning templates, and attachments.
  • Campaign-linked send: Associate a List Email with a Salesforce Campaign before sending. Campaign Members progress through statuses (Sent → Opened → Clicked) as engagement is tracked. Salesforce's most complete native reporting method for mass sends. See Salesforce campaign management.
  • Mass Email Contacts (Classic): Legacy feature in Classic (Setup → Mass Email). Up to 250 recipients per batch using Classic email templates. Tracking appears in HTML Email Status reports. Most organizations have migrated to Lightning List Email.

All three draw from the same 5,000-email org-wide daily pool. Sales list emails consume capacity that marketing campaigns also need. See Salesforce email limitations per day for how the two separate daily limits — org-wide mass and per-user single — interact.

Step-by-Step: Sending a List Email in Salesforce Lightning

  • Enable the permission: An admin must enable 'Allow sending list emails' on the user's profile or permission set. Without it, the Send List Email action won't appear in list view menus.
  • Build your list view: Navigate to Contacts or Leads. Create a filtered list view for your target audience. List Email caps at 500 recipients per batch — if your view has more records, plan to send in batches.
  • Select recipients and open the action: Tick recipient checkboxes (or select all up to 500), click the dropdown arrow next to 'New,' and select 'Send List Email.'
  • Choose a template: Select a Lightning email template or compose directly. Templates are required for merge fields. See Salesforce Lightning email templates for template type options.
  • Review and send: Click the Review tab to confirm merge field rendering and recipient list. Verify the From address, then click Send.
  • Check the results: Open any recipient record — Activity Timeline shows the email as sent. Aggregate open/click totals appear in the List Email report under Reports.

Step-by-Step: Sending a Campaign-Linked Email

Campaign-linked sends provide per-member engagement tracking — but the Campaign must be associated before you send, not after. See Salesforce campaign email limit for per-campaign volume rules.

  • Set up the Campaign and add members: Create or open the Campaign. Add target Contacts or Leads as Campaign Members with an initial status of 'Sent' (or your org equivalent). Members can be added manually, via report, or through import.
  • Configure Campaign Member Statuses: Edit the Campaign's Member Statuses to include Sent, Opened, Clicked, and Unsubscribed. These values update automatically as recipients engage. Without this configuration, engagement doesn't write back to the Campaign.
  • Send List Email from the Campaign record: From the Campaign record, click 'Send List Email' from the Activity or related list. Select your template. The Campaign association is set automatically because you're sending from the Campaign object.
  • Monitor in Campaign reports: Campaign Member reports show each member's status progression. This per-member view is Salesforce's most complete native analytics. See Salesforce campaign performance tracking for report setup.

Planning Around the 5,000-Email Daily Cap

The 5,000-email limit is org-wide, shared, and identical across all Salesforce editions. It resets on a rolling 24-hour window — not at midnight. A 4,000-email campaign at 10 AM leaves only 1,000 for the entire organization for the remainder of the day, including sales prospecting, automated notifications, and customer success emails. See Salesforce's list email limits for how list sends and campaigns compete for the same pool.

  • Allocate capacity in advance: assign daily budgets to sales (list emails), marketing (campaigns), and ops (automated workflows) to avoid any team exhausting the shared pool.
  • Schedule sends outside peak hours: if automated workflows fire heavily in the morning, schedule campaigns for the afternoon or evening to prevent collision.
  • Multiple batches are allowed: List Email's 500-batch ceiling doesn't prevent multiple sends per day — total cumulative sends just can't exceed 5,000 org-wide. For teams consistently hitting the ceiling, see MassMailer's mass email marketing solution, which removes the cap entirely.

Compliance Requirements Before Every Mass Send

CAN-SPAM, CASL, and GDPR require that commercial mass emails include a functioning unsubscribe link, a physical mailing address, and accurate sender identification. Salesforce does not automatically suppress opted-out contacts from List Email sends — your list view or Campaign must filter Email Opt Out = False. See the email opt-out Salesforce for opt-out field management.

  • Unsubscribe mechanism: Every Lightning email template used for mass sends must include a functioning unsubscribe merge field. Confirm it's present before sending at scale.
  • Physical address in footer: required by CAN-SPAM for every commercial email. Build this into your master template.
  • Accurate subject line: the subject must not be deceptive about the email's content. Salesforce doesn't validate this — it's a sender's responsibility. See Salesforce marketing compliance for CAN-SPAM and GDPR specifics.

When a Native AppExchange Tool Is the Right Move

Native Salesforce mass email works well for teams sending under 5,000 emails/day to Contacts and Leads with basic tracking needs. It becomes the wrong tool when:

  • Custom objects are the target: List Email only targets Contacts and Leads. Organizations with students, members, or clients on custom objects can't use native mass email for those records.
  • Volume exceeds 5,000/day: there is no native workaround to increase the org-wide cap. AppExchange tools remove the ceiling entirely.
  • Per-contact engagement is required: native List Email returns aggregate totals only — not individual open/click records in Activity History. An AppExchange tool writes per-contact engagement to every recipient's record.
  • Multi-step drip sequences are needed: List Email is a one-time send. Automated sequences based on engagement behavior require Flow Builder plus an AppExchange tool.

For a direct comparison of native vs. third-party architectures, see Salesforce native email vs third-party tools. For sequence automation, see Salesforce email automation.

Hitting the 5,000-Email Wall? There's a Better Way to Send at Scale from Salesforce.

If your team is managing around the daily cap, can't send to custom objects, or needs per-contact engagement in Activity History — let's talk through what a native Salesforce solution looks like for your org. 30-minute working session, no pitch deck.

Book a free strategy call → calendly.com/siva-devaki

Key Takeaways

  • Salesforce has three native mass email methods: List Email (Lightning, 500/batch), campaign-linked sends (updates Campaign Member Status), and Mass Email Contacts (Classic, 250/batch). All three share the same 5,000-email org-wide daily limit.
  • 'Allow sending list emails' must be enabled by an admin on the user's profile or permission set — it is not on by default for most profiles.
  • Campaign-linked sends deliver per-member engagement tracking (Sent → Opened → Clicked) but only if the Campaign is associated before sending. Retroactive association does not backfill historical data.
  • The 5,000-email limit is org-wide, shared by all teams and all send types, and resets on a rolling 24-hour window — not at midnight. A large morning campaign can leave sales teams unable to send list emails for the rest of the day.
  • CAN-SPAM compliance requires an unsubscribe link, physical address, and accurate subject line in every mass send. Salesforce does not automatically suppress opted-out contacts — list views must include an Email Opt Out = False filter.
  • When volume exceeds 5,000/day, custom objects are the target, or per-contact Activity History engagement is needed, a native AppExchange tool is the practical path — not a workaround.