Service Cloud is Salesforce’s product for customer-service teams — the contact-centre side of the platform. It’s where support agents log and resolve customer issues, where knowledge articles live, where chat / phone / email channels route into one queue, and where field technicians get dispatched. If Sales Cloud is “win the deal”, Service Cloud is “keep the customer”.
What you get out of the box
| Capability | What it does |
|---|---|
| Case Management | Log issues, track status, route to the right agent, link to Account/Contact/Asset |
| Omni-Channel Routing | Push email, chat, social, voice cases to the right available agent automatically |
| Knowledge Base | Internal and customer-facing articles, with version control and approval workflows |
| Entitlements & SLAs | Define service levels, milestones, and business hours per customer/contract |
| Service Console | Tabbed split-view UI optimised for agents handling many cases at once |
| Email-to-Case / Web-to-Case | Auto-create cases from inbound channels |
| CTI / Open CTI | Integrate with telephony for click-to-dial, screen pops, call logging |
| Live Agent / Chat / Messaging | Real-time chat on your website or via WhatsApp, SMS, Facebook |
| Field Service | Dispatch technicians, schedule jobs, mobile app for on-site work |
| Service Reports & Dashboards | Built-in case metrics: first response, resolution time, CSAT |
Core data model
Account ──┬── Contact ── Case
│
├── Asset ── Case (product-tied cases)
│
└── Contract ── Entitlement ── Case (SLA-bound cases)The Case object is the centre of gravity. Everything in Service Cloud points at or hangs off a Case.
Key objects
- Case — a customer issue (the “ticket”)
- Solution (legacy) — proposed answer to a Case; now mostly replaced by Knowledge
- Knowledge Article — published article in the knowledge base
- Entitlement — the SLA contract tying a customer to a service level
- Milestone — checkpoints within an entitlement (e.g. first response in 1 hour)
- Asset — a product instance the customer owns
- Contract — the umbrella agreement
- CaseComment / EmailMessage — communication on a Case
- ServiceAppointment, WorkOrder — Field Service objects
Editions and pricing tier
Service Cloud is sold separately from Sales Cloud, though a “Service Cloud” licence includes a lot of Sales Cloud functionality (Accounts, Contacts, Reports). Edition tiers — Essentials, Professional, Enterprise, Unlimited — gate features like Entitlements, Workflow, Process Builder, and API access.
How it differs from Sales Cloud
| Sales Cloud | Service Cloud | |
|---|---|---|
| Focus | Pre-sale: Leads → Opportunities → Quotes → Orders | Post-sale: Cases → resolutions → renewals |
| Primary object | Opportunity | Case |
| Console | Sales Console | Service Console |
| Routing | Lead/Opportunity assignment rules | Omni-Channel + case assignment rules |
| Channels | Email, phone, dialer | Email, phone, chat, social, SMS, voice, video |
Common follow-ups
- What’s the difference vs Service Cloud Automation? — Automation is the optional add-on that brings AI agents, bots, and orchestration to Service Cloud.
- Can a single org run both Sales and Service Cloud? — Yes — they share the data model.
- Field Service is part of Service Cloud? — Field Service is an add-on, licensed separately on top of Service Cloud.
Verified against: Salesforce Help — Service Cloud. Last reviewed 2026-05-17 for Spring ‘26.