Entitlement Management
Entitlement Management is the Service Cloud feature that lets a customer-support organization track contractual service-level agreements (SLAs) and the customer-facing rights (entitlements) tied to product purchases, service contracts, or assets.
Definition
Entitlement Management is the Service Cloud feature that lets a customer-support organization track contractual service-level agreements (SLAs) and the customer-facing rights (entitlements) tied to product purchases, service contracts, or assets. The feature provides the data model (Entitlement, ServiceContract, ContractLineItem, EntitlementContact, MilestoneType records), the SLA timer engine (Entitlement Processes with milestones), and the UI surfaces (case page Entitlement field, Milestone tracker, Entitlement Processes setup) needed to model and operate against contractual support obligations.
Entitlement Management sits at the intersection of three concepts. An Entitlement is the customer's right to receive support (linked to an Account, a Contact, or an Asset). A Service Contract is the broader contractual agreement that contains multiple Entitlements. An Entitlement Process is the SLA timer that runs on each Case matched to an Entitlement. Together they let a Service Cloud team enforce "platinum customers get 1-hour response, gold customers get 4-hour response, silver customers get next-business-day response" with platform-tracked compliance and escalation actions when SLAs are missed.
How Entitlement Management structures Service Cloud SLAs
The data model: Entitlement, ServiceContract, ContractLineItem
Entitlement Management uses several connected objects. Entitlement holds the actual customer right: linked to Account, Contact, or Asset; tied to a specific Entitlement Process; valid between Start Date and End Date. Service Contract is the broader contractual agreement holding multiple Entitlements. ContractLineItem links specific products or services to the contract. EntitlementContact links contacts allowed to request support under the entitlement. The model is built for B2B service relationships where the customer has structured rights, not for B2C support where every customer gets the same SLA.
Entitlement matching: how cases find the right entitlement
When a Case is created, Salesforce can auto-populate the Entitlement based on the Case Account, Contact, or Asset. Setup, Entitlement Settings, Enable Entitlement Auto-Population. The platform picks the most specific match: an entitlement on the Asset beats one on the Contact, which beats one on the Account. Multi-entitlement accounts may need a Case Trigger or Flow to pick the right one. Without auto-population, agents must manually attach the entitlement to the case, which is the most common reason SLA clocks never start.
Entitlement Process and SLA timing
Each Entitlement is tied to an Entitlement Process, the SLA timer engine. The process defines milestones (First Response, Resolution Time, Customer Update), business hours, stopped statuses, and time-trigger actions. When the case is matched to an entitlement, the entitlement process starts ticking. Milestones fire workflow actions (email alerts, task creation, field updates) at warning, violation, and success points. The process is what turns a written contract into operational automation.
Service Contracts and Contract Line Items
Service Contracts model the broader business agreement above Entitlements. A Service Contract might cover an enterprise account for 12 months, with Contract Line Items for "Cloud product, Premium Support tier" and "On-premises product, Standard Support tier". Each line item can spawn one or more Entitlements with specific support rights. The Service Contract drives the renewal cycle, the line items drive the pricing, and the entitlements drive the operational SLAs. The three levels separate concerns cleanly.
Entitlement Contacts: who can request support
EntitlementContact records list which Contacts are authorized to file cases under an entitlement. A platinum support contract might list five named support contacts. If a sixth person from the same company files a case, the entitlement does not auto-match because they are not on the EntitlementContact list. This is the platform mechanism for "named contact" support tiers common in enterprise B2B agreements. Setup, Entitlement Settings, Enable Entitlement Contact Verification turns the requirement on.
Usage-based entitlements: limited support credits
Some support contracts include a limited number of support cases or hours: 50 cases per year, or 100 support hours. Usage-Based Entitlements track this consumption. Each case consumes from the entitlement allocation, and when the limit is hit, new cases under that entitlement fail (or trigger an upsell prompt). The feature is rare but useful for niche B2B contracts. Setup the entitlement with a Usage Type (Cases or Hours) and a Max Usage. The platform enforces the cap automatically.
Reporting and SLA compliance dashboards
Entitlement Management includes several standard report types: Cases with Entitlements, Cases with Milestones, Entitlements with Account, Usage-Based Entitlements with Usage History. Most Service Cloud teams build a dashboard tracking SLA compliance: percent of cases meeting first-response milestone, average resolution time by tier, violation count by team. The dashboard is what makes Entitlement Management visible to leadership. Without it, the operational data is captured but never surfaces in a digestible form.
Setting up Entitlement Management for SLA tracking
Setting up Entitlement Management is a multi-step Setup workflow: enable the feature, configure business hours, design entitlement processes, create entitlement records, attach to accounts and cases, build reports.
- Enable Entitlement Management
Setup, Entitlement Settings, Enable Entitlement Management. Enable Auto-Population. Add the Entitlement field and Case Milestones related list to the Case page layout.
- Configure business hours profiles
Setup, Business Hours, New. Build one profile per region or support tier. Add holidays. Wrong business hours means wrong SLA clocks.
- Define milestone types
Setup, Milestone Types, New. Create reusable milestone definitions (First Response, Resolution Time, Customer Update). These attach to entitlement processes later.
- Build entitlement processes
Setup, Entitlement Processes, New. For each support tier (Platinum, Gold, Silver), build a process with milestones, business hours, and stopped statuses.
- Create entitlement records
App Launcher, Entitlements, New. For each account or asset, create an Entitlement linked to the right Entitlement Process. Set Start Date and End Date.
- Configure Entitlement Contacts if needed
For named-contact support, enable Entitlement Contact Verification. Add EntitlementContact records for each authorized contact per entitlement.
- Test with a real case
Create a case on an entitled account. Confirm the Entitlement auto-populates, the milestones appear in the related list, and the SLA clock starts.
- Build the SLA compliance dashboard
Reports, New, Cases with Milestones. Build the dashboard tracking IsCompleted and IsViolated rates by team. This is the leadership surface for the feature.
Org-level toggle that activates the Entitlement, ServiceContract, ContractLineItem objects and related model.
Automatically matches new cases to the right entitlement based on Account, Contact, or Asset.
Restricts case creation to listed EntitlementContacts on the entitlement.
The SLA timer engine attached to entitlements, defining milestones, business hours, and stopped statuses.
Variant that tracks limited support credits (cases or hours) and enforces caps.
- Without Entitlement Auto-Population, cases require manual entitlement attachment, which most agents skip. SLA clocks never start.
- An entitlement can have only one Entitlement Process at a time. Changing the process mid-period does not retroactively re-run on existing milestones.
- Business hours profiles need region-specific holidays. A US holiday list on an EMEA entitlement creates SLA-violation false positives.
- Usage-Based Entitlements are tracked at runtime. Bulk-uploading historical cases against a usage entitlement may bypass the counter; test the bulk path.
- Entitlement Contact Verification rejects cases from unlisted contacts. This is the right behavior for named-contact support tiers and a source of complaints when the contact list is stale.
Trust & references
Cross-checked against the following references.
- Entitlement Management OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Entitlement Management.
- Entitlement Management OverviewSalesforce Help
- Set Up Entitlement ManagementSalesforce Help
- Milestones in Entitlement ManagementSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Entitlement Management do?
Q2. What components make up Entitlement Management?
Q3. Why is Entitlement Management essential for tiered support?
Discussion
Loading discussion…