Case Management Setup

Case Management Setup

This skill activates when an admin needs to configure or troubleshoot the full Service Cloud case handling layer: inbound channels (Email-to-Case, Web-to-Case), routing and assignment, time-based escalation, auto-response emails, case team collaboration, and entitlement/milestone SLA tracking.

Before Starting

Gather this context before working on case management configuration:

• Which inbound channels are needed? Email-to-Case and Web-to-Case have different limits and configuration paths. Email-to-Case uses routing addresses; Web-to-Case generates an HTML form.
• What are the SLA requirements? Escalation rules require business hours to be configured first, or the clock runs 24/7. Entitlements require the Entitlements feature to be enabled in Setup before any configuration is possible.
• Are assignment rules already active? Auto-response rules ONLY fire when an assignment rule also fires. This is the single most common false assumption in case management setup. If assignment rules are not active or not matching, auto-responses will not send regardless of auto-response rule configuration.
• What are the queue membership and deletion policies? Deleting a queue that owns open cases orphans those cases — they have no owner and no queue. Enforce a transfer-before-delete policy.

Core Concepts

Inbound Channel Limits and Behaviors

Email-to-Case converts inbound customer emails into cases. Key limits and behaviors:

• Maximum inbound email size: 25 MB (attachments included). Emails exceeding this limit are rejected.
• Email body is truncated at 32,000 characters. Content beyond that limit is silently dropped — not stored in an attachment.
• Thread ID handling is critical. Salesforce embeds a thread ID token in outgoing case emails. When the customer replies, Salesforce reads the token to find the parent case and adds the reply as a new Email Message record. If the routing address is misconfigured or the thread ID is stripped by a mail server, the reply creates a new case instead of threading. Test threading end-to-end before go-live.
• On-Demand Email-to-Case (recommended) uses Salesforce-hosted routing addresses. Classic Email-to-Case uses a local email agent. Use On-Demand unless firewall or data residency requirements prevent it.

Web-to-Case converts form submissions from a website into cases. Key limits:

• 50,000 pending Web-to-Case requests is a hard org-level limit. If this queue is full, new submissions are silently dropped — Salesforce does not queue them or send an error to the submitter. Monitor the pending count in Setup and clear it regularly.
• Web-to-Case has no native field validation. All validation must be done in the HTML form (JavaScript) or via Apex triggers / Flow after the case is created.
• If the submitter's email matches an existing Contact record, Salesforce automatically populates the Contact lookup. If no match is found, the contact field is blank — no new Contact is created automatically.

Assignment Rules and Auto-Response Dependency

Only one assignment rule can be active per object. For cases, this means one active case assignment rule at all times. Rule entries are evaluated in order; the first match wins.

Auto-response rules depend entirely on assignment rules. The auto-response rule fires ONLY when the active assignment rule fires. If no assignment rule is active, if no rule entry matches the incoming case, or if the case was created in a way that does not trigger the assignment rule (e.g., via the API without the Sforce-Auto-Assign: true header), the auto-response will not fire. This is a platform behavior, not a configuration bug.

Escalation Rules

Escalation rules re-route or notify when cases are not resolved within a time threshold. Critical behaviors:

• Only one active escalation rule per org (not per object). The rule contains multiple entries with time-based conditions.
• The escalation engine runs on an hourly cadence. Escalation is not real-time. A case that crosses the threshold at 9:05 AM will not be escalated until the engine next runs, potentially at 10:00 AM. Design SLAs with this lag in mind.
• Business hours must be explicitly assigned to the escalation rule entry, OR the time clock runs 24 hours a day, 7 days a week. Forgetting to attach a business hours record is the most common escalation misconfiguration.
• Deactivating and reactivating an escalation rule can trigger a wave of immediate escalations for all cases that were accumulating escalation time while the rule was inactive. Re-activation causes the engine to evaluate all open cases against the rule simultaneously. This can generate hundreds of escalation actions and emails at once in a large org. Always test reactivation in a sandbox and warn stakeholders.

Case Teams

Case teams allow multiple users to collaborate on a single case, each with a defined access level, without changing the case owner.

• Case team roles define the access level (Read Only, Read/Write, Case Owner's role) and must be created before predefined teams can be built.
• A predefined team is a template — a named set of users paired with roles. Adding a predefined team to a case grants each member access per their role.
• Case team access is independent of org-wide sharing and sharing rules. A user added to a case team can see and edit the case even if they would not have access via normal sharing. This is by design — use it intentionally.
• Case team members do not receive automatic email notifications when added to a case. Use workflow rules or Flow to send notifications if needed.

Entitlements and Milestones

Entitlements represent the level of support a customer is entitled to (e.g., response within 4 business hours). Milestones are the specific time-based targets within an entitlement process.

• Entitlements must be enabled in Setup (Feature Settings → Service → Entitlement Management) before any entitlement configuration is accessible. This is often overlooked.
• Milestones exist within an entitlement process. You cannot add milestones directly to a case without an entitlement process.
• Adding entitlement templates to products (so that cases auto-receive an entitlement when created for a product) is only available in Salesforce Classic. In Lightning, entitlements must be applied manually or via Flow/Apex.
• Milestone violation and warning actions (emails, field updates) are configured on the milestone within the entitlement process, not on the case itself.

Common Patterns

Pattern: Email-to-Case with Threaded Reply Handling

When to use: Customer support team receives inbound email, needs replies to thread into the same case rather than create new cases.

How it works:

1. Navigate to Setup → Email-to-Case → Enable On-Demand Email-to-Case.
2. Create a routing address (e.g., support@yourcompany.com). Salesforce generates a Salesforce-hosted email address for the mail server to forward inbound mail to.
3. Configure your external mail server to forward inbound mail from support@yourcompany.com to the Salesforce routing address.
4. In the routing address settings, enable "Create Task for new emails" if you need agent notification.
5. Set the case origin, default status, and priority for cases created from this address.
6. Test: send an inbound email, confirm a case is created. Reply from Salesforce to the case. Have the customer reply to that email. Confirm the reply appears as an Email Message on the original case (not a new case).

Why not Classic Email-to-Case: The local email agent requires a server on-premise or a relay. On-Demand routes through Salesforce infrastructure and requires no local component.

Pattern: Web-to-Case with Assignment and Auto-Response

When to use: Customers submit support requests through a website form; confirmations should be sent automatically.

How it works:

1. Navigate to Setup → Web-to-Case. Enable Web-to-Case and configure a default case origin.
2. Select the fields to expose on the form. Salesforce generates the HTML snippet.
3. Embed the HTML in the external web page.
4. Create a case assignment rule with a catch-all entry pointing to the support queue.
5. Create a case auto-response rule. The rule fires when the assignment rule fires, sending the confirmation email to the contact email address submitted on the form.
6. Use Flow to add validation logic if required fields or format checking is needed post-submission.

Why not use the default case owner alone: Web-to-Case without an assignment rule means all cases land with the default case owner, bypassing queue routing. Auto-response also will not fire without an active assignment rule.

Pattern: SLA Tracking with Entitlements and Milestones

When to use: Business has contractual or operational SLA commitments (e.g., respond within 4 hours, resolve within 24 hours) and needs automated tracking and violation alerts.

How it works:

1. Enable Entitlement Management in Setup.
2. Create business hours records matching support team schedules.
3. Create an entitlement process. Add milestones (e.g., "First Response" — 4 business hours, "Resolution" — 24 business hours). Set warning and violation actions on each milestone.
4. Create an entitlement record for the relevant accounts or contacts.
5. Associate the entitlement with new cases (manually, via Flow, or via entitlement templates on products if using Classic).
6. Monitor milestone completion in the Case Milestones related list on the case.

Decision Guidance

Recommended Workflow

Step-by-step instructions for an AI agent or practitioner activating this skill:

1. Confirm the inbound channel scope (Email-to-Case, Web-to-Case, or both) and whether On-Demand or Classic Email-to-Case is appropriate given the org's infrastructure.
2. Configure queues first — all routing depends on queues existing with the correct members and supported objects (Case must be in the queue's Supported Objects list).
3. Configure the case assignment rule with ordered rule entries targeting the appropriate queues; confirm the rule is active.
4. Configure the auto-response rule if customer acknowledgment emails are needed; verify that the assignment rule from step 3 will fire for the same case creation events.
5. Configure escalation rule entries with explicit business hours records, correct time thresholds, and re-route or notification actions; test in sandbox before activating in production.
6. If SLA tracking is required: enable Entitlement Management, create business hours, build the entitlement process with milestones, create entitlement records, and build the automation to attach entitlements to new cases.
7. Run the check_case_management.py script against exported metadata and validate with the Review Checklist before marking configuration complete.

Review Checklist

Run through these before marking case management configuration complete:

• Email-to-Case routing address is verified and thread ID handling tested end-to-end (reply threads into parent case, not new case)
• Web-to-Case pending request count is below 50,000; monitoring alert exists if available
• Active case assignment rule exists with at least one catch-all entry; no cases are falling to the default case owner unintentionally
• Auto-response rule entries have a valid email template; confirmed that assignment rule fires for the same creation events
• Escalation rule entries each have a business hours record explicitly attached; deactivation/reactivation risk communicated to stakeholders
• All queues referenced by assignment and escalation rules exist, have at least one active member, and have Case in their Supported Objects list
• Case team roles are created before predefined teams; predefined teams contain current active users
• If entitlements used: Entitlement Management is enabled, entitlement processes are active, business hours are attached to milestones, and automation applies entitlements to new cases

Salesforce-Specific Gotchas

Non-obvious platform behaviors that cause real production problems:

1. Auto-response rule requires assignment rule to fire — The auto-response rule is not independent. It fires only when the active case assignment rule fires for that case. If the assignment rule is inactive, has no matching entry, or was bypassed (e.g., API insert without Sforce-Auto-Assign: true header), the auto-response will not send. This is the most commonly misdiagnosed "auto-response not working" issue.
2. Escalation reactivation triggers bulk escalations — Deactivating an escalation rule pauses escalation time accumulation for open cases. When you reactivate the rule, the engine evaluates all open cases at once. Cases that have been open longer than the threshold since deactivation will escalate immediately in a single wave. In a large org, this can generate thousands of emails and re-assignments at once. Always test reactivation volume in a sandbox.
3. Email-to-Case body truncation is silent — Long customer emails are truncated at 32,000 characters without any notification to the agent or customer. Content after that limit is permanently lost. If customers send lengthy technical logs or attachments-as-text, critical information may be missing from the case body.
4. Deleting a queue orphans owned cases — If you delete a queue that currently owns open cases, those cases lose their owner. They will not appear in any queue view or any individual's My Cases view until manually reassigned. Enforce a case transfer protocol before queue deletion.
5. Web-to-Case has no native validation — The generated HTML form contains no JavaScript validation. Required-field enforcement, format checks (phone numbers, email formats), and spam prevention must all be implemented in the HTML form customization or via post-creation Flow/Apex. Without this, garbage data will enter your org.
6. Entitlement template on product is Classic-only — Associating an entitlement template with a product (so cases auto-receive an entitlement) is only configurable in Salesforce Classic. In Lightning Experience, there is no equivalent UI. Entitlements must be applied to cases via Flow, Process Builder, or Apex.

Output Artifacts

Related Skills

• assignment-rules — use when the focus is on case assignment rule entry logic, criteria design, or API trigger behavior for case assignment specifically
• queues-and-public-groups — use when creating or troubleshooting the queues that assignment and escalation rules route cases into