Service Cloud Solution Design
Designing the routing and service-level machine
Most solution-design questions are about one chain of records. Get the order right:
- A case arrives (Email-to-Case, Web-to-Case, messaging, phone/CTI) with a record type bound to a support process.
- Auto-response rules acknowledge the customer. They do not assign ownership.
- Assignment rules set the owner - typically a queue - by evaluating criteria in order; first match wins.
- Omni-Channel pulls work from queues and pushes it to the right agent by capacity, skills, and priority.
- Escalation rules act on aging cases, reassigning or notifying based on case age against business hours.
- Entitlements and milestones measure whether you met the promise; a Service Contract groups entitlements for an account.
Distinguish carefully: an entitlement defines what the customer is owed; a milestone is a time-based target on a case; an SLA is the business promise expressed through those milestones. Assignment rules are evaluated at creation or manual re-evaluation - not continuously.
Traps: expecting escalation rules to route like Omni-Channel; assuming queues auto-distribute without Omni-Channel or assignment; confusing Service Contracts with Entitlements; forgetting business hours and holidays, which silently change every milestone calculation.
Worked example: A Platinum case must be answered within one hour. Design: Service Contract on the account → Platinum entitlement → first-response milestone of one hour → entitlement process bound via the case record type and support process. Without business hours configured, the target drifts over weekends.
Rule of thumb: draw the case's life as a timeline; every rule you add must have a clear moment on that timeline.