A Sales Cloud or standard Salesforce license already lets users work with Cases. So why pay for Service Cloud? Because the tools that make a support team fast, like Omni-Channel routing, the Service Console with Knowledge, digital channels and SLA tracking, sit behind the Service Cloud User license.
Hereβs how it breaks down for a single user. Exact access can vary by edition and contract, so confirm against your own org.
| Capability | Sales Cloud / standard license | Service Cloud User license |
|---|---|---|
| Case management (create, view, edit) | Yes | Yes |
| Lightning console apps | Yes | Yes |
| Omni-Channel routing | No | Yes |
| Messaging and chat (web, in-app, SMS, WhatsApp) | No | Yes |
| Knowledge in the Service Console | No | Yes |
| Entitlements, Milestones and Service Contracts | No | Yes |
| CTI and Service Cloud Voice | No | Yes |
| Bots and AI agents for service | No | Yes |
| Field Service | No | Prerequisite |
| Assignment rules, escalation rules, macros, quick text | Edition-dependent | Yes |
A tabbed workspace where agents keep several cases, contacts and conversations open at once, with split view, related records and a utility bar.
Omni-Channel pushes cases, messages and calls to the right agent based on skills, availability and capacity, so nobody cherry-picks the queue.
Messaging for In-App and Web, SMS and WhatsApp conversations land in the console next to cases from Web-to-Case and Email-to-Case.
Note: Salesforce has retired legacy Live Chat in favour of Messaging for In-App and Web. Plan new builds on Messaging.
A searchable library of articles that agents can read and attach to cases from inside the console, and that customers can use in a help center.
Authors and readers also need the Knowledge User checkbox on their user record, which is separate from the Service Cloud User checkbox.
Define what support each customer is owed, then track first-response and resolution times against it, with warnings and actions when a milestone is about to be missed.
Service Contracts tie those entitlements to the agreement each customer signed.
Connect a phone system so calls pop the right record in the console. Service Cloud Voice brings telephony in natively with transcripts.
Voice is licensed separately. Third-party CTI partners like Five9 or RingCentral have their own licensing.
Service bots and Agentforce agents for service, Next Best Action recommendations, and Field Service for scheduling technicians all build on Service Cloud.
Field Service users need a Service Cloud license first, then a Field Service license on top.
Some features in older comparisons are listed as Service Cloud only, but most Enterprise and Unlimited orgs have them regardless. Check your edition before buying licenses just for these:
About service analytics: standard reports and dashboards work on any license. The prebuilt Service Analytics app runs on CRM Analytics and needs its own license.
Yes. Many teams buy a Sales and Service bundle for people who do both, like account managers who also handle support for their own customers.
No. Customers access cases and Knowledge through Experience Cloud, which uses its own community licenses. Guest visitors reading public articles donβt need a license at all.
Yes. A common setup is Service Cloud for frontline agents who take routed work, and Sales Cloud or Platform licenses for people who only view or update cases now and then.
Legacy Chat has been retired. New setups should use Messaging for In-App and Web, which also supports bots and Agentforce agents.
Weβll review your support process and recommend the right mix before you buy.