Entitlement Process
An Entitlement Process is the SLA timer engine inside Service Cloud's Entitlement Management feature.
Definition
An Entitlement Process is the SLA timer engine inside Service Cloud's Entitlement Management feature. It defines the milestones a case must hit, the time allowed for each milestone, the business hours used to measure elapsed time, and the actions triggered when a milestone completes, succeeds, or violates its target. The entitlement process is what turns a written SLA (respond within 2 hours, resolve within 24 hours) into clock-driven automation that pages the on-call team when the clock runs out.
Entitlement processes attach to one or more entitlements, which themselves attach to accounts, contacts, assets, or service contracts. When a case is created and matched to an entitlement, the entitlement process clock starts. Milestones tick down against the business hours profile, fire workflow rules, send emails, escalate to other queues, and mark the case as compliant or in violation. The whole machinery is invisible to the customer and central to any contractual obligation a Salesforce-using company has agreed to.
How an Entitlement Process actually runs the SLA clock
Entitlement Management: the broader feature
Entitlement Management is the umbrella feature that wraps entitlements, service contracts, contract line items, milestones, and entitlement processes. It is enabled in Setup, Service, Entitlement Settings. The entitlement record is a contractual right held by a customer (the account or contact), referencing one or more products or assets. The entitlement process is the operational logic attached to that record. The distinction between entitlement (what the customer owns) and entitlement process (how it operates) is the most common confusion in Service Cloud SLA setup.
Milestones: the unit of SLA tracking
A milestone is a single SLA target inside an entitlement process: First Response, Initial Resolution, Final Resolution, Customer Notification. Each milestone has a Trigger Time (minutes from case creation), a Business Hours profile, an Order (the sequence in the process), and a set of Time Trigger actions (what happens when the clock hits a specified point). Milestones support warning triggers (alert at 75 percent of the time), violation triggers (alert when missed), and success triggers (cleanup when completed). The combination is rich enough to model most contractual SLAs without writing Apex.
Business hours: the SLA clock
Entitlement processes measure elapsed time against a Business Hours profile, not wall-clock time. A 4-hour SLA on a Monday 5 PM case might mean Tuesday 1 PM if business hours are 9-to-5. Business hours support multiple profiles (one per region, one per support tier), holidays, and time zones. The default business hours profile is the org default. Picking the right business hours profile on the entitlement process is the most common SLA setup error. Wrong profile means the clock measures wrong, and milestone violations fire when nobody expects them.
Case auto-matching and entitlement lookup
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. Without this, agents have to manually attach the entitlement to the case, which is the most common reason SLA clocks never start. Auto-population picks the most specific match: an entitlement tied to an asset wins over one tied to a contact, which wins over one tied to an account. Multi-entitlement accounts may need a Case Trigger or Flow to pick the right one.
Milestone actions and the Entitlement Process Designer
Time Trigger actions fire at specified offsets before, at, or after the milestone target. Actions include sending an email alert, creating a task, updating a field, sending an outbound message, or invoking an Apex action. Multiple actions per trigger are supported. The Process Designer in Setup is a drag-and-drop builder that surfaces the structure, but the underlying records (MilestoneType, EntitlementProcessMilestone) are queryable through SOQL and accessible from Apex if Flow does not cover the case.
Stopping the clock: case status mapping
Entitlement processes need to know when the SLA clock pauses. The Stopped Status field on the entitlement process lists the case statuses that pause the clock (typically Waiting on Customer, On Hold). When the case moves into a stopped status, the milestone tracker pauses elapsed time. When the case moves back into an active status, the timer resumes. Without configured stopped statuses, the clock runs through the customer's response time, which inflates violation rates and frustrates the support team. Audit the stopped status list any time the case process changes.
Reporting on SLA compliance
Salesforce includes the Case Milestones report type out of the box. The report shows each milestone, its target time, its completion time, and whether it was completed or violated. The IsCompleted, IsViolated, and ElapsedTimeInMins fields are the operational data. Most Service Cloud orgs build a dashboard from this report type tracking violation rate by team, by region, and by entitlement. Without the report, the milestones fire actions in the background and nobody knows whether the SLA is being met.
Configuring an Entitlement Process for Service Cloud SLAs
Building an entitlement process is a multi-step configuration: enable the feature, design the process, attach milestones, configure stopped statuses, attach to entitlements, and validate against real cases.
- Enable Entitlement Management
Setup, Entitlement Settings, Enable Entitlement Management. Also enable Auto-Population and confirm the Case page layout shows the Entitlement field and the Case Milestones related list.
- Configure business hours profiles
Setup, Business Hours, New. Build one profile per region or support tier (US Business Hours 9-5 EST, EU Business Hours 9-5 CET, 24x7 Premium Support). Add holidays for the region. Without correct business hours, SLA clocks measure wrong.
- Create the entitlement process
Setup, Entitlement Processes, New. Give it a name (Standard Support Process), pick the Case Entry Criteria (formula that decides which cases the process runs on), set Business Hours, set Stopped Statuses.
- Define milestone types
Setup, Milestone Types, New. Create entries like First Response, Resolution Time, Customer Update. These are reusable across processes. Each milestone type is the unit of tracking.
- Attach milestones to the process
Inside the entitlement process, Add Milestone. Pick the milestone type, set the Trigger Time (minutes), set the Business Hours profile (can override the process default), and order the milestones in sequence.
- Configure milestone time triggers
For each milestone, add Warning, Violation, and Success time triggers. Each trigger has an offset (minutes before or after the target) and a set of workflow actions (email alert, task, field update).
- Attach the process to entitlements and test
Open an entitlement record, set the Entitlement Process field to the new process, then create a test case. Confirm the case auto-populates the entitlement, the milestones appear in the related list, and the timer starts.
Formula that decides which cases the process applies to. Defaults to all cases on the entitlement. Refine with Type, Priority, or RecordType filters.
Profile that determines how elapsed time is measured. Overridable per milestone. Wrong profile is the single biggest SLA setup mistake.
List of case statuses that pause the SLA clock. Typically Waiting on Customer, On Hold. Without these, the clock counts customer response time toward the SLA.
Action that fires at a milestone offset. Supports warning, violation, and success offsets with workflow actions per trigger.
Reusable definition of an SLA target. Created once, attached to many processes. Examples: First Response, Resolution, Escalation Notification.
- Cases must be matched to an entitlement for the process to run. Without auto-population or a Flow to set the entitlement, the SLA clock never starts.
- Business hours profiles must include holidays for the region. A missing holiday means the SLA clock runs through Christmas Day, generating false violations and angering customers.
- Time Trigger actions reference workflow actions, which are deprecated in favor of Flow. Migrate triggers to Flow-based actions for any new entitlement process built today.
- Changing the entitlement process on an in-flight case does not retroactively change milestones already created. The new process applies to future milestones only.
- The Entitlement Process Designer UI is older and can be slow with large milestone sets. Use the Tooling API or Metadata API for bulk edits.
Trust & references
Cross-checked against the following references.
- Entitlement Management OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Entitlement Process.
- Entitlement Management OverviewSalesforce Help
- Create an Entitlement ProcessSalesforce 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 an Entitlement Process define?
Q2. What's a typical milestone?
Q3. What can milestones trigger when at risk?
Discussion
Loading discussion…