A Lead Auto-Response Rule sends an automatic email to the prospect when a new Lead is created, with the message tailored to criteria you define. It’s how you say “thanks, we got your enquiry, someone will be in touch” within seconds of a form submission — no rep involvement.
What it does vs Assignment Rules
| Feature | Targets | Action |
|---|---|---|
| Lead Assignment Rule | The owner in Salesforce | Sets OwnerId — routes to user or queue |
| Lead Auto-Response Rule | The prospect (lead’s email) | Sends an email using an email template |
Both rules can fire on the same Web-to-Lead submission and they’re configured independently.
Where it fires
Like assignment rules, auto-response rules fire when:
- A Web-to-Lead form submits
- An API caller sets
EmailHeader.triggerAutoResponseEmail = true - A Data Loader / Wizard insert is configured to trigger it
A manual UI insert does not trigger auto-response by default — that’s a feature, not a bug. You don’t want every rep-created lead spamming the prospect.
Anatomy of a rule
- One active rule at a time per org
- Many entries in priority order
- Each entry has:
- Order
- Criteria (field filter or formula)
- Email template to send
- From address (a verified org-wide email address or the rule creator)
- Reply-to option
The first entry whose criteria match wins, and only that email goes out.
Example
Lead Auto-Response Rule: "Standard Confirmations"
Entry 1:
Criteria: Lead.Country = 'India'
Template: "Thanks (India)"
From: [email protected]
Entry 2:
Criteria: Lead.LeadSource = 'Webinar'
Template: "Thanks for joining the webinar"
Entry 3 (default):
Template: "Thanks for getting in touch"Template variables
Templates can pull merge fields from the Lead, the owner, the org, and a related Account/Contact. Common merges:
Hi {!Lead.FirstName},
Thanks for your interest in {!Organization.Name}. We've received your request
about {!Lead.Description} and will get back to you within one business day.
— {!Lead.Owner.Name}If the merge resolves to null, Salesforce shows an empty string — so guard with formula fallbacks for required-feeling fields.
Delivery and deliverability
- Comes from a Salesforce IP — set up SPF/DKIM/DMARC to keep it out of spam folders. Setup → Email → Deliverability and Email Authentication Settings.
- Volume counts against the daily org email limit (5,000 external emails / 24 hours per org for most editions).
- Bounces show up on the Lead record (HTML
EmailBouncedReason).
When you’ve outgrown it
Auto-Response Rules send one email per matched criterion. For nurture sequences, scoring, A/B testing, or branded transactional templates, move to Pardot / Marketing Cloud Account Engagement, Marketing Cloud, or a third-party email platform.
Common follow-ups
- Difference vs auto-assignment? — Auto-assignment changes ownership; auto-response sends mail to the prospect.
- Why didn’t my UI-created lead get an auto-response? — Manual inserts don’t trigger it unless you tick the option (or call the API with the email header).
- Daily email cap? — Edition-dependent, commonly 5,000/day external for Enterprise.
Verified against: Salesforce Help — Auto-Response Rules. Last reviewed 2026-05-17 for Spring ‘26.