Context
We recently faced an issue where changes made to an email forwarding setup unintentionally impacted the Production Email-to-Case process. As a result, incoming emails stopped creating cases in Salesforce until the configuration was corrected.
Questions
- What backup options are available if Email-to-Case stops working?
- How can we ensure emails still create cases in Salesforce during such outages?
- Are there any monitoring or alerting mechanisms to detect issues early?
- Has anyone implemented a failover or secondary routing solution for Email-to-Case?
#Salesforce Admin #Systems Administrator #Administrator #Salesforce Developer #Salesforce_developer #Beginner Developer #Sales Cloud
To improve Email-to-Case reliability and minimize the impact of routing failures, I would recommend the following approach:
- Maintain an email backup: Configure your email server to retain a copy of every incoming support email in the original mailbox or a dedicated backup folder before forwarding it to Salesforce.
- Configure a secondary routing option: Maintain a separate backup support mailbox or alternate intake channel. If the primary forwarding configuration fails, your email administrator can redirect incoming emails to the backup route. Test this setup carefully to avoid duplicate cases.
- Monitor processing failures: Configure the Automated Case User's email address to deliver Salesforce Email-to-Case error notifications to a monitored internal mailbox or distribution group.
- Enable error notifications: In Setup, navigate to Feature Settings → Service → Email-to-Case and review the option to notify senders about processing errors.
- Test the Salesforce routing address directly: Send a test email to the generated Email Services Address. If a case is created, investigate the external email forwarding configuration. If no case is created, check the Automated Case User's permissions, record types, validation rules, Apex triggers, and Flow automation.
- Implement monitoring: Use email-platform monitoring to alert administrators when forwarding rules change or message delivery fails. You can also periodically send test emails and verify that corresponding cases are created.
- Establish a recovery procedure: During an outage, preserve affected emails and create or resubmit cases after the issue is resolved. Before replaying messages, check whether a case already exists to avoid duplicates.
Salesforce documentation:
- Troubleshooting Email-to-Case: https://help.salesforce.com/s/articleView?id=000384980&language=en_US&type=1
- Email Retention and Error Prevention: https://help.salesforce.com/s/articleView?id=000387063&language=en_US&type=1
- Email-to-Case Forwarding Guidelines: https://help.salesforce.com/s/articleView?id=service.customizesupport_forwarding_guidelines.htm&language=en_US
For a production environment, I would prioritize retaining inbound emails, monitoring processing errors, and documenting a tested recovery procedure before implementing a more complex failover solution.
I hope this helps! If you find this answer helpful, please select it as the Best Answer.
Thanks,
Deepak Sachdeva
Nubys Technology Pvt. Ltd.
