Entitlement
An Entitlement in Salesforce defines the level of support a customer is eligible to receive, including response times, service hours, and the number of support incidents covered.
Definition
An Entitlement in Salesforce defines the level of support a customer is eligible to receive, including response times, service hours, and the number of support incidents covered. Entitlements are linked to Accounts, Assets, or Service Contracts and work with Milestones to ensure that service level agreements (SLAs) are met.
In plain English
“Here's a simple way to think about it: an Entitlement is how Salesforce knows what level of service a customer is actually owed. Premium support? 24/7 response? Used 8 of 10 incidents? The entitlement record carries the answer.”
Worked example
TechVault offers three support tiers: Basic (72-hour response), Premium (24-hour response), and Platinum (4-hour response). Each tier is represented as an Entitlement record linked to the customer's Service Contract. When a new Case is created, Salesforce checks the customer's Entitlement and automatically sets the response deadline. Milestones track whether the SLA is met.
Why an Entitlement is how Salesforce knows what level of service a customer is actually owed
Some customers paid for premium support. Some have a contract that includes 24/7 response. Some have used 8 of their 10 included incidents this quarter. An Entitlement is how Salesforce models all of those - a record that ties to an Account, Asset, or Service Contract and defines exactly what level of support that relationship entitles the customer to receive. Working with Milestones, the entitlement engine starts and stops the SLA clocks based on the actual coverage the customer has paid for.
The reason this is administrator territory rather than something the support team handles in their head is that SLA disputes turn into legal disputes. Without an entitlement record, the answer to whether a four-hour response promise applied to a particular case is somebody's memory; with it, the answer is auditable data. Build the entitlement model deliberately during Service Cloud rollout, keep contract data in sync with the entitlement records, and treat any finding that a case wasn't covered as a chance to validate the data, not just close the conversation.
How to create Entitlement
Entitlements grant the right to receive specific service — "Acme is entitled to 5 cases per month with 4-hour first response" — anchored to an Account, Asset, or Service Contract. They drive Service Cloud's SLA tracking via linked Entitlement Processes and Milestones.
- Make sure Entitlement Management is enabled
Setup → Entitlement Settings → Enable Entitlement Management. New orgs ship with this off.
- Open the parent record (Account / Asset / Service Contract)
Entitlements anchor to one of these three. Account is the most common starting point.
- Click New on the Entitlements related list
Or App Launcher → Entitlements → New.
- Set Name and Type
Type: Phone Support / Web Support / Web Or Phone Support. Drives which channels honor the entitlement.
- Set Start Date and End Date
When the entitlement is active. Cases created outside this window don't inherit the entitlement.
- Set Cases Per Entitlement and Per-Incident details
Cases Per Entitlement caps the # of supported cases over the lifetime. Per-Incident: each Case can use the entitlement multiple times.
- (Optional) Link an Entitlement Process
On the entitlement, set the Entitlement Process Name field. This is what drives SLA milestones for Cases that use this entitlement.
- Save → Cases reference the entitlement to inherit SLA
On a Case, set the Entitlement Name field → SLA milestones from the linked Entitlement Process now drive the Case clock.
Required. Convention: "<Account> - <Service Tier>" e.g. "Acme - Premium 24/7."
Required by association — entitlements anchor to one of these.
- Entitlement Management must be enabled in Setup → Entitlement Settings. Without it, the related list and the Entitlement object don't appear.
- Entitlements drive SLAs via the linked Entitlement Process. An entitlement without a process is just metadata — no clock fires on Cases.
- Cases inherit the entitlement only if you set the Case's Entitlement Name field. There's no auto-link by default — build a Flow on the Case to set it from the Account's active entitlement.
How organizations use Entitlement
Built three Entitlement records per Service Contract - "Premium 24x7" (4-hour response), "Standard Business Hours" (24-hour response), "Limited Renewal Buyback" (best-effort) - each tied to specific Asset records. When a Case is created, the entitlement engine starts the right SLA clock based on which Asset the Case references.
Uses Entitlement Processes with three Milestones - First Response (1h), Manager Touch (4h), Resolution Target (24h) - on every Premium-tier Entitlement. The Milestone Tracker on the Case page gives agents a live countdown, and a flow alerts the team lead when any Milestone enters yellow.
Ties every Entitlement to an Asset record so the SLA the customer is owed is determined by the equipment they own, not by the customer's Account tier. A small commercial customer who bought one piece of premium-tier equipment gets premium-tier response on Cases for that Asset specifically.
Trust & references
Straight from the source - Salesforce's reference material on Entitlement.
- What's Entitlement Management?Salesforce Help
Test your knowledge
Q1. Which Salesforce Cloud includes Entitlement as a key feature?
Q2. How does Entitlement help support agents be more productive?
Q3. What business function does Entitlement primarily support?
Discussion
Loading discussion…