Service Cloud is Salesforce's customer support platform. At its core is the Case object — every support ticket, complaint, or service request is a Case. Getting the fundamentals right at setup determines whether your support team loves or resents the system.
The Case Lifecycle
A Case typically moves through: New → In Progress → Waiting on Customer → Resolved → Closed. Define your statuses to match your team's actual workflow. Create a validation rule that requires a Resolution Summary before a case can be Closed — otherwise closed cases become black boxes.
Queues
Queues are waiting areas for unassigned cases. Create a queue per team or tier: "Tier 1 Support", "Billing", "Technical Escalations". Members of a queue can accept or be assigned cases from it.
Cases sit in a queue until an agent takes ownership. Reports on queue depth (unassigned cases per queue) are one of your most important operational metrics.
Case Assignment Rules
Assignment Rules automatically assign new cases to a queue or user based on case criteria. Setup → Case Assignment Rules. Rule entries are evaluated in order — the first match wins. Common rules:
- Product = "Enterprise" → Assign to Enterprise Support queue
- Origin = "Email" + Priority = "High" → Assign to Tier 2 queue
- Default (no match) → General Support queue
Always have a default catch-all rule at the bottom. A case that doesn't match any rule stays unassigned and can be missed.
Escalation Rules
Escalation Rules automatically escalate cases that have been open too long without action. Setup → Escalation Rules. Configure: If a High Priority case is not modified in 4 hours → escalate to senior agent + notify manager. This is the declarative alternative to building Flow timers for SLA escalation.
Entitlements and SLA Milestones
Entitlements define the level of support a customer is entitled to based on their contract or product tier. An Entitlement Process defines the milestones (First Response, Resolution) with time targets.
When a case is created, if the customer has an active Entitlement, the process attaches to the case and starts tracking milestone compliance. Violated milestones trigger alerts or escalation automatically.
Setup path: Service Setup → Entitlements → Entitlement Processes → New. Add milestones (First Response: 4 hours, Resolution: 24 hours). Then enable the Entitlement Process on the relevant cases via the Case Origin or Account.
Email-to-Case
Enable Email-to-Case to auto-create Cases from inbound emails. Setup → Email-to-Case. Each configured email address creates a routing address that, when emailed, creates a Case with the email body as the first Case Comment. Map the From address to Contact lookup for auto-association. This eliminates manual case creation for email-heavy support teams.
Omni-Channel Routing (Optional)
For teams handling chat, email, and phone in parallel, Omni-Channel queues and routes work items across channels based on agent availability and capacity. It's a significant configuration investment but eliminates the manual "who picks up this case" overhead entirely for teams above ~10 agents.