Auto-response rules are mechanically simple but business-critical. The customer's first impression of your team depends on the email landing within seconds, looking personal, and pointing them to the right next step. Configure deliverability before activating the rule, test every entry, and monitor inbox placement after launch.
- Plan the segment-to-template mapping
List every Lead or Case segment that should receive a different acknowledgment. Enterprise versus SMB, Premium Support versus Standard, partner referral versus direct inbound. Each segment maps to one template, and the template should explicitly tell the customer what to expect next.
- Create or update the email templates
Setup > Email Templates > New. Use Lightning Email Builder for new templates. Include personalization tokens, a clear next step (calendar link, support phone number, knowledge base URL), and a reply-to address. Save the template and preview it with sample data.
- Verify the org-wide From Email address
Setup > Organization-Wide Addresses > New. Add the sender (support@yourdomain.com, hello@yourdomain.com). Salesforce sends a verification email to the address. The owner must click the verification link before the address can be used in auto-response rules.
- Create the auto-response rule
Setup > Lead Auto-Response Rules (or Case Auto-Response Rules) > New. Name the rule for the year and channel mix (Lead Auto-Response 2026). Each object supports one active rule, so the name should reflect the current strategy.
- Add rule entries in priority order
For each entry: set the order number, criteria, From Name, From Email, reply-to address, and email template. Place narrow criteria at the top, broad fallbacks below, and a catch-all default at the bottom that guarantees every Lead or Case receives some acknowledgment.
- Activate the rule and enable on intake paths
Activate from the rule detail page. For Web-to-Lead and Web-to-Case, check the Use Active Auto-Response Rule box in the form settings. For API integrations, set EmailHeader.useAutoResponseRules = true in the call.
- Test every entry through every channel
Submit test Web-to-Lead/Web-to-Case forms covering each entry's criteria. Send a test inbound email if Email-to-Case is configured. Confirm the right template arrives, the personalization tokens populate, and the reply-to address works when the customer hits reply.
- Build the post-launch deliverability monitor
Setup > Email Logs lets you see delivery, bounce, and spam complaint events. Schedule a weekly check for the first month after launch. Pair with a report on Leads/Cases created without an auto-response logged in their related activity history.
Defines which records receive which template. First-match-wins; place narrow criteria first and broader fallbacks below.
The verified sender address. Salesforce requires verification before use; unverified addresses silently fail the auto-response.
The Lightning Email Template, Visualforce template, or Classic template that determines the email content and personalization.
- Only one Auto-Response Rule can be active per object. Activating a new rule auto-deactivates the previous one, which can break customer-facing email if the new rule is incomplete.
- The From Email must be a verified Organization-Wide Address. Unverified addresses cause the rule to fail silently with no error in the UI, and customers receive nothing.
- Entry order matters absolutely. Broad criteria entries placed above narrow entries short-circuit them, and Leads receive the wrong template for their segment.
- Auto-response rules do not fire on manual Lead/Case creation by default. Web-to-Lead, Web-to-Case, Email-to-Case, and API-with-flag are the standard intake paths that trigger them.
- Deliverability problems (SPF/DKIM/DMARC misconfiguration, blacklisted sending domain) silently push auto-responses to spam folders, which destroys the entire point of the automation.