Salesforce Case Management is the core of Salesforce Service Cloud — a structured system for capturing, routing, prioritising, escalating, and resolving customer support requests across every channel (email, web, phone, chat, social media). Cases are the equivalent of Opportunities in sales — the central work record that agents use throughout the support lifecycle. This guide covers the complete Case Management setup: Email-to-Case, Web-to-Case, assignment rules, queues, escalation rules, SLA enforcement via Entitlements, and the Lightning Service Console that agents work from daily.
The best guide is the one that makes the support workflow easy to follow.
A useful explanation should help the reader understand how case management improves service control.
That means the guide should focus on day-to-day support behaviour rather than only product terminology.
For many teams, the value is in making service work more visible and easier to manage.
It should also show how cases move through the support process from intake to resolution.
A good guide should explain why case tracking matters and how it supports consistent service.
That makes it one of the most important parts of Service Cloud use.
Salesforce case management is useful because support teams need a structured way to track requests, resolve issues, and keep service history organised. It gives agents a place to manage customer problems without losing context.
The Case Object: Core Fields and Lifecycle
A Case record contains:
- Subject: the one-line description of the issue — auto-populated from the email subject line in Email-to-Case
- Description: the full detail of the customer’s issue
- Status: tracks the case through its lifecycle — typically New, Open, Pending Customer Response, Escalated, Closed
- Priority: Low, Medium, High, Critical — used in escalation rules and agent working queues
- Origin: how the case was created — Email, Web, Phone, Chat, Social Media
- Type: categorisation of the issue — Question, Problem, Feature Request, Returns — used in reporting and knowledge base article matching
- Account: the customer company the case relates to
- Contact: the specific individual who submitted the case
- Owner: the agent or queue currently responsible for the case
- Case Number: auto-generated unique identifier (e.g., 00001234) used in all customer-facing communications
Case lifecycle: customers submit cases (via email, web form, phone, or chat), cases are captured in Salesforce and assigned to an agent or queue, agents investigate and respond, the case is resolved and closed. The case activity timeline records every interaction — agent notes, customer emails, internal comments, and status changes.
Email-to-Case: Converting Emails into Cases
Email-to-Case is the most common case creation channel in B2B support — it converts all emails sent to your support address (support@yourcompany.com) into Case records automatically.
Setup
- Setup → Service → Email-to-Case → Enable Email-to-Case
- Create a Routing Address: the email address that will receive customer emails. Salesforce provides a Salesforce-hosted email address (yourcompany@yourdomain.salesforce.com) or you can use On-Demand Email-to-Case with your own domain email.
- Configure the Routing Address settings:
- Case Owner: the default owner for cases created from this address (typically a queue)
- Case Priority: the default priority assigned to emails from this address
- Save Email: whether to store the full email content in Salesforce or just the case data
- Set up your support email address to forward all incoming emails to the Salesforce Email-to-Case routing address
- Test by sending an email to your support address — a Case should appear in Salesforce within minutes
Email threading: Email-to-Case tracks email reply chains — when a customer replies to an existing case email (which includes the case number in the subject line), subsequent emails are added to the existing Case as Case Comments rather than creating a new Case. This keeps the full email conversation on one record.
Web-to-Case: Creating Cases from Website Forms
Web-to-Case generates an HTML form that customers fill in on your website or support portal — submitting the form creates a Case record in Salesforce.
- Setup → Service → Web-to-Case → Enable Web-to-Case
- Configure the Default Case Origin and Default Response Template
- Generate the HTML form: Setup → Web-to-Case → Generate HTML — select which fields to include (Name, Email, Company, Subject, Description, Case Type, Priority)
- Embed the generated HTML on your website’s Contact Support or Help page
- When submitted, the form data is POSTed to Salesforce’s servers and creates a Case automatically
Auto-Response Rules
Auto-Response Rules send an automated email acknowledgment to customers when a Case is created — confirming receipt of their request and providing the Case Number for reference.
Setup → Service → Auto-Response Rules → Case Auto-Response Rules → New Rule:
- Create a rule with criteria (e.g., all cases with Origin = Email) and an associated Email Template
- The Email Template is sent to the Case’s Contact email address immediately on Case creation
- Best practice: the auto-response email includes the Case Number (merge field: {!Case.CaseNumber}), sets expectations on response time (“We aim to respond within 4 business hours”), and provides a link to your Knowledge Base for self-service while they wait
Case Assignment Rules
Assignment Rules automatically assign Cases to the correct agent or queue based on Case field criteria — removing manual triage work from a supervisor and routing cases to the right specialist.
Setup → Service → Case Assignment Rules → New Rule → Add Rule Entries:
- Criteria: Case Priority = Critical → Assign To: Critical Cases Queue
- Criteria: Case Type = Billing, Account.Plan__c = Enterprise → Assign To: Enterprise Billing Support Queue
- Criteria: Account.Region__c = APAC → Assign To: APAC Support Team Queue
Rules are evaluated in order — the first matching rule determines the assignment. A catch-all rule at the end ensures all non-matched cases go to a General Support queue rather than being unassigned.
Queues: Shared Case Pools
Queues are shared record pools — Cases assigned to a queue are visible to all queue members, who claim cases from the queue to work on them. Setup → Queues → New Queue:
- Queue name and label
- Supported Objects: select Case
- Queue Members: add users or groups who are members of this queue
- Queue Email: an optional email address that receives notifications when Cases are assigned to this queue
Agents work from Queues via List Views — a “My Support Queue Cases” list view filtered by Case Owner = [specific queue] shows all Cases waiting to be claimed. In Omni-Channel deployments, Cases are automatically pushed to available agents rather than requiring manual claiming.
Escalation Rules
Escalation Rules automatically escalate Cases that haven’t been responded to or resolved within SLA timeframes.
Setup → Service → Escalation Rules → New Rule → Add Escalation Entries:
- Criteria: Case Status = New AND Age Over = 4 hours AND Priority = High → Reassign to Senior Support Queue AND Notify: support-manager@company.com
- Criteria: Case Status = Open AND Age Over = 24 hours AND Priority = Critical → Reassign to Escalation Team AND Send Email Alert to VP of Support
The Case Age is calculated from the Case’s Created Date by default — or from the Case’s Last Modified Date if “Age Based On” is configured differently. Escalation Rules run on a schedule (every 15 minutes for free, or real-time with Service Cloud).
Entitlements and SLAs
Entitlements define what level of support each customer is entitled to — based on their service contract or support tier. Combined with Milestones, Entitlements enforce response and resolution time SLAs within each Case record.
Entitlement Process
- Enable Entitlements: Setup → Entitlement Settings → Enable Entitlements
- Create Entitlement Processes (Setup → Entitlement Processes): a named SLA process with defined Milestones. Example: “Enterprise SLA” with:
- Milestone 1 “First Response”: must be completed within 2 hours of Case creation for Critical priority, 4 hours for High priority
- Milestone 2 “Resolution”: must be completed within 8 hours for Critical, 24 hours for High
- Create Entitlement records on each Account: link the Entitlement Process to the Account’s support contract. When a Case is created for an Account with an Entitlement, the Entitlement Process automatically attaches to the Case.
On the Case record, Milestones appear as a section showing countdown timers: “First Response: 1 hour 45 minutes remaining.” When a Milestone is breached (timer reaches zero without completion), escalation actions fire — emails to managers, Case priority upgrades, Chatter notifications.
The Milestone completion action: when an agent sends the first response email, they click “Complete Milestone” on the First Response Milestone — stopping the timer and recording the actual response time.
Lightning Service Console
The Lightning Service Console is a specialised Salesforce app designed for support agents — it replaces the standard record navigation with a multi-panel workspace optimised for handling cases efficiently.
Key Service Console features:
- Split-pane view: Case list on the left, selected Case detail on the right — agents can review and work cases without full page navigation
- Pinned tabs: frequently accessed records (the agent’s queue list, escalated cases view) pinned as persistent tabs that don’t close when navigating
- Subtabs: each Case opens as a primary tab, with the Contact, Account, and related Entitlement as subtabs — agents see all context without opening new browser windows
- Macro support: one-click macros that perform multiple actions (update Case Status to Pending Customer Response + send email from template) in a single action — reducing repetitive clicks for common case workflows
- Knowledge sidebar: relevant Knowledge articles suggested automatically based on Case subject and description — Einstein AI matches article content to the Case to help agents resolve issues faster
Einstein Case Classification
With sufficient historical data (typically 400+ closed cases), Einstein Case Classification (available in Service Cloud Einstein) automatically classifies incoming cases:
- Suggested Case Fields: Einstein reads the Case Subject and Description and suggests values for Type, Cause, Product, Priority — reducing agent time spent on classification
- Auto-classification: when configured to auto-classify (not just suggest), Einstein populates these fields automatically on Case creation — enabling downstream routing and escalation rules to fire immediately without waiting for an agent to manually classify
Key Service Cloud Reporting Metrics
Build a Service Dashboard tracking:
- Case Volume: cases created per day/week/month by channel and type
- Average Handle Time (AHT): average time from Case creation to Case closure
- First Contact Resolution (FCR): percentage of cases resolved in a single response, without customer follow-up
- SLA Compliance Rate: percentage of Milestones completed on time vs. breached
- Customer Satisfaction (CSAT): if post-case surveys are configured, average satisfaction score per agent, team, and case type
- Open Case Age: distribution of open cases by age (0–24 hours, 1–3 days, 3–7 days, 7+ days)
The best case setup is the one that keeps service work organised from start to finish. If the case flow is unclear, support becomes harder to manage.
Conclusion
Salesforce Service Cloud’s Case Management system provides a complete infrastructure for B2B customer support — from multi-channel case capture through intelligent routing, SLA enforcement, and agent productivity tools. Email-to-Case and Web-to-Case cover the primary inbound channels without custom development. Assignment Rules, Queues, and Escalation Rules automate the triage and routing that would otherwise require a supervisor’s manual attention. Entitlements and Milestones enforce SLA commitments with real-time countdown visibility on each case. The Lightning Service Console reduces agent context-switching and enables macros for one-click workflow execution. For organisations where customer support quality directly affects renewal rates and expansion revenue, investing in the Service Cloud configuration described in this guide builds the operational foundation for consistent, measurable support performance.
Sources
Salesforce, Service Cloud Case Management Documentation (2026)
Salesforce, Email-to-Case Setup Guide (2026)
Salesforce, Entitlements and SLA Configuration Guide (2026)
Salesforce, Lightning Service Console Documentation (2026)
Gartner, Magic Quadrant for CRM Customer Engagement Centre (2025)