PranavNagrecha/AwesomeSalesforceSkills / skills/admin/email-to-case-configuration
email-to-case-configuration
VerifiedConfiguring Salesforce Email-to-Case: Standard vs On-Demand mode selection, routing address setup, email threading via Lightning tokens, auto-response rules, attachment limits, and per-address case field defaults. Trigger keywords: email-to-case, routing address, on-demand email-to-case, email threading, case from email, email agent, routing address setup, Case.settings-meta.xml, EmailToCaseRoutingAddress, emailServicesAddress, isVerified, caseOrigin, enableThreadTokenInBody, useEmailHeadersForThreading, overEmailLimitAction, unauthorizedSenderAction, enableE2CAttachmentAsFile, saveEmailHeaders, newEntityRecordType, casePriority, EmailMessage.EmailRoutingAddressId, auto-response loop. NOT for the wider case layer (queues, escalation rules, case teams, entitlements) - use admin/case-management-setup. NOT for routing case work items to agents after creation - use admin/omni-channel-routing-setup. NOT for the email templates or letterheads themselves - use admin/email-templates-and-alerts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 32.3 KB |
| references/examples.md | markdown | 6.0 KB |
| references/gotchas.md | markdown | 24.4 KB |
| references/llm-anti-patterns.md | markdown | 8.4 KB |
| references/metadata-examples.md | markdown | 18.6 KB |
| references/well-architected.md | markdown | 11.1 KB |
| scripts/check_email_to_case_configuration.pyexecutable | script | 27.9 KB |
| templates/email-to-case-configuration-template.md | markdown | 3.6 KB |
templates/email-to-case-configuration-template.md
View on GitHub# Email-to-Case Configuration — Work Template
Use this template when setting up or troubleshooting Email-to-Case for an org.
## Scope
**Skill:** `email-to-case-configuration`
**Request summary:** (fill in what the user asked for — e.g., "set up Email-to-Case for support@acme.com" or "customer replies are creating new cases instead of threading")
---
## Context Gathered
Answer these before proceeding:
- **Email-to-Case mode required:** On-Demand / Standard (circle one)
- If Standard: reason (data residency / firewall policy / other): ___________________
- **Inbound support addresses to configure:**
1. ___________________
2. ___________________
3. ___________________
- **Case defaults per address:**
| Address | Case Origin | Status | Priority | Default Owner / Queue |
|---|---|---|---|---|
| | | | | |
| | | | | |
- **Auto-response emails required?** Yes / No
- If Yes: confirmed active case assignment rule exists? Yes / No
- Auto-response From address (must NOT be a routing address): ___________________
- **Known constraints:**
- High attachment volume? (On-Demand 35 MB total inbound message limit; ~25 MB effective attachments after MIME overhead): ___________________
- Email security gateway in use? (threading token stripping risk): ___________________
---
## Approach
Which pattern from SKILL.md applies?
- [ ] On-Demand Email-to-Case with verified threading (single address)
- [ ] Multiple routing addresses for channel-based classification
- [ ] Standard Email-to-Case with local agent (justify above)
- [ ] Troubleshooting existing configuration (describe symptom below)
**Symptom / scenario (if troubleshooting):** ___________________
---
## Configuration Steps
Track each step as you complete it:
- [ ] Email-to-Case enabled in Setup; mode selected and documented
- [ ] On-Demand Service option enabled (if applicable)
- [ ] Routing address(es) created with correct case defaults
- [ ] Salesforce-generated address(es) copied and recorded
- [ ] Mail server forwarding rule(s) configured and active
- [ ] Routing address(es) verified (Send Verification Email → click link → status = Verified)
- [ ] Active case assignment rule confirmed; entries match Email-to-Case cases
- [ ] Auto-response rule configured with non-routing From address (if applicable)
- [ ] Threading tested end-to-end through production mail gateway
- [ ] Checker script run; issues resolved
---
## Checklist (from SKILL.md)
- [ ] Email-to-Case feature enabled; mode documented and justified
- [ ] Each routing address has external email, Salesforce target address, and verified status
- [ ] Mail server forwarding active and tested: inbound email creates a case
- [ ] Threading tested end-to-end: reply adds Email Message to original case (not new case)
- [ ] Active assignment rule with entries matching Email-to-Case cases; catch-all to queue
- [ ] Auto-response rule (if used): valid template, From address is not the routing address
- [ ] Attachment limits communicated: On-Demand 35 MB total inbound message (~25 MB effective attachments after MIME encoding); no per-attachment cap
- [ ] Checker script output reviewed
---
## Notes
Record any deviations from the standard pattern and the reason:
- ___________________
- ___________________
## Routing Address Record (fill in after configuration)
| Field | Value |
|---|---|
| Routing Name | |
| External Email Address | |
| Salesforce-Generated Address | |
| Verification Status | Verified / Unverified |
| Case Origin | |
| Case Status | |
| Case Priority | |
| Default Owner / Queue | |
| Auto-Response Rule Active | Yes / No |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |