Send Mass Email in Salesforce Classic: Steps, Limits & What Changed

Salesforce Classic's Mass Email feature was the original way Salesforce users sent bulk personalized emails from the CRM. Even as most users have moved to Lightning Experience — where the equivalent feature is called 'List Email' — Classic mass email remains relevant for legacy orgs, hybrid setups, or Classic-only customizations. This page covers the Classic workflow step by step, how it compares to Lightning, every limitation that applies, and what to do when 5,000 emails per day isn't enough. For all mass email methods in Salesforce, see the Salesforce mass email guide.

What Salesforce Classic Mass Email Is

Classic Mass Email sends a single email template — with merge fields, HTML formatting, and optional attachments — to a filtered list of contacts, leads, or campaign members in one action. Each recipient gets an individually addressed copy with their own merged values. Salesforce queues and delivers the messages asynchronously, logging the send event to each recipient's Activity History.

Unlike sending from individual records, Classic Mass Email is initiated from the Tools section under the Contacts or Leads navigation tab. It requires a Lightning Email Template or a Classic HTML or Text template. Visualforce email templates are explicitly not supported for mass sends — as noted in Salesforce's mass email limitations documentation. For all Salesforce email sending methods, see Salesforce email overview.

Step-by-Step: How to Send Mass Email in Salesforce Classic

In Salesforce Classic, the Mass Email feature is accessed through the navigation tabs — not from individual records or campaigns. Here is the complete send workflow:

  1. Navigate to Tools. In the Classic navigation bar, click the Contacts or Leads tab. Scroll to the Tools section at the bottom and click Mass Email Contacts or Mass Email Leads.
  2. Select recipients. Choose a list view from the View dropdown to filter your target audience. Only records in that view are available. Check individual boxes or select all visible records.
  3. Choose the sender and template. Select which user the email sends from (yourself or another user with appropriate permission), then click Next and select your email template. Text, HTML, and Custom formats are supported — Visualforce is not.
  4. Configure send options. Choose whether to BCC yourself and whether to store an activity on each recipient's record. Always enable 'Store an activity' — without it, no send record appears in Activity History.
  5. Preview and send. Review a merged preview using a sample recipient's data. Verify the From address, subject line, and template rendering, then click Send. Salesforce processes the queue asynchronously.
  6. Check the HTML Email Status Report. After the send completes, run the standard HTML Email Status Report under Salesforce Reports to see per-recipient delivery, bounce, and failure status. Open and click tracking is not available natively.

Classic vs. Lightning: What Changed With Mass Email

When Salesforce introduced Lightning Experience, Mass Email was renamed List Email and moved from the navigation tab Tools section to a list view action. The core capability is the same — select a list, pick a template, send personalized copies — but the access path and some constraints differ. As Salesforce Ben's Lightning mass email guide explains, the Lightning version is more accessible and better integrated with the modern interface.

  • Access path: Classic: Tools section under the Contacts or Leads navigation tab. Lightning: Send List Email action from the dropdown on any Contact or Lead list view — faster to reach, no page navigation required.
  • Template support: Classic supports Text, HTML, and Custom templates (no Visualforce). Lightning supports Lightning Email Templates — responsive, mobile-friendly, drag-and-drop. Classic Visualforce templates also don't work in Lightning List Email.
  • Activity logging: Both log a send activity to Activity History when enabled. See Salesforce email log for how Activity History works across both interfaces.
  • Tracking: Neither provides per-contact open or click tracking. The HTML Email Status Report is available in both basic and delivery status. Full engagement tracking requires a dedicated AppExchange mass mailer.
  • Daily limit: Both share the same 5,000/day org-wide ceiling. See Salesforce mass email limits.

Salesforce Classic Mass Email Limitations Every Team Should Know

Before building a mass email workflow around Salesforce Classic, understand the full constraints documented in Salesforce's mass email limitations:

  • 5,000 emails per org per day: All mass email, list email, and API-triggered sends share a single 5,000/day ceiling measured in GMT. Duplicate addresses count individually. This limit is org-wide — not per user. See Salesforce mass email limits.
  • Contacts and Leads only: Classic Mass Email targets only standard Contact and Lead records (plus Person Accounts and org-internal users). Custom objects are completely excluded — native mass email cannot reach them, regardless of your Salesforce edition.
  • No Visualforce email templates: Classic mass email explicitly excludes Visualforce templates. Teams with complex Visualforce templates for branding or dynamic content must use a different template type — or a dedicated AppExchange mass mailer.
  • No per-contact open or click tracking: The HTML Email Status Report shows delivery status only. Individual open and click data is not captured for Classic mass sends. Per-contact engagement tracking requires a native AppExchange solution. See track emails in Salesforce.
  • Developer Edition orgs: 10 recipients per day: In Developer Edition and trial orgs, the ceiling drops to 10 external email addresses per day — making mass send workflow testing impractical without a full production or sandbox org.

Scaling Beyond Classic: When Native Mass Email Isn't Enough

Classic Mass Email works for infrequent, low-volume sends to standard Salesforce objects. Teams hit their ceiling when they need more than 5,000 emails per day, custom object targeting, per-contact engagement data, or multi-step drip sequences. For those use cases, a native AppExchange mass mailer is the right path — not a third-party ESP that moves data outside Salesforce.

MassMailer removes the 5,000/day ceiling, enables sends to any standard or custom Salesforce object, writes per-contact engagement (opens, clicks, bounces, unsubscribes) to Activity History in real time, and integrates with Flow Builder for trigger-based automation — all inside Salesforce. The scale-up doesn't require a platform migration: install from the AppExchange, and your existing data, object relationships, and compliance fields (Email Opt Out, Individual object) carry over. See bulk email for Salesforce and mass email marketing for Salesforce.

Best Practices for Sending Mass Email in Salesforce Classic

  • Build targeted list views before sending: Always filter your list view with 'Email Opt Out equals False,' a valid email address condition, and relevant segmentation criteria (industry, stage, geography). Unsegmented sends produce low engagement and high opt-outs. See Salesforce marketing compliance.
  • Use HTML templates with merge fields: Classic HTML templates with merge fields produce personalized sends and are compatible with the HTML Email Status Report for delivery tracking. Plain text templates skip personalization and make post-send reporting harder.
  • Always enable 'Store an activity': Without this option, no send record appears in Activity History on recipient records — leaving your team without documentation of who was contacted and when.
  • Run the HTML Email Status Report after large sends: It shows per-recipient delivery, bounce, and failure status — letting you identify addresses to suppress before the next campaign. See Salesforce email reporting.
  • Coordinate send timing across teams: The 5,000/day limit is shared org-wide. A morning send by one team can exhaust the daily quota before another team's afternoon campaign runs. Schedule sends or set org-level policies for quota allocation.

Sending More Than 5,000 Emails a Day or Need to Reach Custom Objects? Let's Map It Out.

Schedule a 30-minute working session with the MassMailer team. We'll show you how to move beyond the Classic mass email ceiling — with unlimited volume, custom object sends, per-contact engagement tracking, and Flow Builder automation — without migrating your Salesforce data anywhere.

Book a call → calendly.com/siva-devaki

Key Takeaways

  • Classic Mass Email is accessed from the Tools section under the Contacts or Leads tab. It sends a template with merge fields to a filtered list asynchronously, logging the send to Activity History when 'Store activity' is enabled.
  • Classic mass email and Lightning List Email share the same 5,000/day org-wide ceiling (GMT). Duplicate addresses count individually. The limit cannot be raised by upgrading your Salesforce edition.
  • Classic limitations: Contacts and Leads only (no custom objects), no Visualforce template support, no per-contact open or click tracking, and Developer Edition orgs are capped at 10 recipients per day.
  • In Lightning, Mass Email became List Email — same core capability, different access path (list view dropdown vs. navigation tab tool), better template support. Both share the 5,000/day limit.
  • Neither Classic nor Lightning native mass email tracks per-contact opens or clicks. The HTML Email Status Report shows delivery status only. Per-contact engagement in Activity History requires a native AppExchange mass mailer.
  • Scaling beyond Classic: install a native AppExchange mass mailer for unlimited volume, custom object sends, real-time per-contact tracking, drip campaigns, and Flow Builder automation — no data migration required.