PranavNagrecha/AwesomeSalesforceSkills / skills/admin/case-management-setup
case-management-setup
VerifiedConfiguring Salesforce case management: case queues, assignment rules, escalation rules, auto-response rules, Email-to-Case, Web-to-Case, case teams, entitlements, and milestones. Use when setting up or troubleshooting the Service Cloud case handling layer. Trigger keywords: email-to-case, web-to-case, escalation rules, case teams, entitlements, milestones, auto-response, case queue. NOT for Standard vs On-Demand Email-to-Case and routing-address setup — use admin/email-to-case-configuration. NOT for routing case work items to agents — use admin/omni-channel-routing-setup.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 29.7 KB |
| references/examples.md | markdown | 7.3 KB |
| references/gotchas.md | markdown | 22.5 KB |
| references/llm-anti-patterns.md | markdown | 13.7 KB |
| references/metadata-examples.md | markdown | 35.7 KB |
| references/well-architected.md | markdown | 8.4 KB |
| references/worked-example-case-intake.md | markdown | 14.3 KB |
| scripts/check_case_management_setup.pyexecutable | script | 40.9 KB |
| templates/case-management-setup-template.md | markdown | 2.9 KB |
templates/case-management-setup-template.md
View on GitHub# Case Management Setup — Work Template
Use this template when working on tasks in this area.
## Scope
**Skill:** `case-management-setup`
**Request summary:** (fill in what the user asked for)
## Context Gathered
Record the answers to the Before Starting questions from SKILL.md here.
- **Inbound channel:** [ ] Email-to-Case [ ] Web-to-Case [ ] Both
- **Email-to-Case type:** [ ] On-Demand (recommended) [ ] Classic
- **Active case assignment rule exists?** [ ] Yes [ ] No [ ] Unknown
- **Business hours configured?** [ ] Yes — name: ___ [ ] No
- **SLA requirements:** Response target: ___ Resolution target: ___
- **Entitlements required?** [ ] Yes [ ] No
- **Entitlement Management enabled in Setup?** [ ] Yes [ ] No [ ] Unknown
## Configuration Checklist
### Queues
- [ ] Case queues exist with correct names and members
- [ ] Each queue has "Case" in its Supported Objects list
- [ ] Queue email addresses configured for notifications
### Assignment Rules
- [ ] One active case assignment rule exists
- [ ] Rule entries ordered from specific to catch-all
- [ ] Catch-all entry exists as the last entry
- [ ] Tested: cases from Web-to-Case and Email-to-Case route to correct queue
### Auto-Response Rules
- [ ] Assignment rule confirmed to fire before configuring auto-response
- [ ] Auto-response rule active with valid email template per entry
- [ ] "From" address is NOT the Email-to-Case routing address (would create loop)
### Escalation Rules
- [ ] Business hours record created and attached to each rule entry
- [ ] Time thresholds reflect business hours, not calendar hours
- [ ] Deactivation/reactivation impact communicated to stakeholders
- [ ] Tested in sandbox before production activation
### Email-to-Case
- [ ] Routing address created and mail server forward rule configured
- [ ] Thread ID handling tested end-to-end (reply threads into parent case)
- [ ] Subject-line thread ID enabled as fallback if body processing unreliable
- [ ] Body truncation at 32,000 characters communicated to support team
### Web-to-Case
- [ ] Form HTML embedded on external site with client-side validation added
- [ ] Pending request count monitored (hard limit: 50,000)
- [ ] Post-creation Flow configured for server-side validation if needed
### Case Teams (if applicable)
- [ ] Case team roles created with correct access levels
- [ ] Predefined teams built referencing the correct roles
- [ ] Team members are active users
### Entitlements and Milestones (if applicable)
- [ ] Entitlement Management enabled in Setup
- [ ] Business hours attached to entitlement process
- [ ] Milestones configured with warning and violation actions
- [ ] Automation (Flow or Apex) applies entitlements to new cases
- [ ] Lightning limitation acknowledged: no template-on-product UI
## Approach
Which pattern from SKILL.md applies? Why?
(fill in)
## Deviations
Record any deviations from the standard pattern and why.
(fill in)
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 |