Entitlement Processes and Milestones

Why Entitlement Processes and Milestones Matter

Entitlement Management is one of the core topics in the Advanced Cloud Applications section of the Salesforce Advanced Administrator exam. Companies that sell support agreements, warranties, or service-level agreements (SLAs) need a way to (1) confirm what level of support a customer is entitled to and (2) prove that support agents actually met the promised response and resolution times. Entitlement Management answers both needs. On the exam you will see scenario-based questions such as "Universal Containers wants to ensure that high-priority cases receive a first response within two hours and that managers are notified if that deadline is missed." Recognising that this is an entitlement process with a milestone and a violation action, rather than an escalation rule or a workflow time trigger, is exactly the skill being tested. Understanding the terminology, the order of setup, and the behavior of each component will earn you several easy marks.

What Is Entitlement Management?

Entitlement Management is a set of Service Cloud features that lets you define, enforce, and track customer support agreements. It is made up of several related objects:

• Entitlements – Records that define the type and level of support a customer is eligible for (for example, "Gold Support – Phone and Web, 24/7"). Entitlements are related to an Account and can optionally be related to Contacts, Assets, and Service Contracts. An entitlement can have an Entitlement Process attached to it.
• Entitlement Processes – Timelines that contain all the steps (milestones) your support team must complete to resolve a Case or Work Order. The process defines entry criteria (when a record enters the process), exit criteria (when it leaves), business hours, and the milestones that apply.
• Milestones – Required, time-dependent steps in a support process, such as First Response, Case Escalated, or Resolution Time. Each milestone has a time trigger (the number of minutes allowed to complete it) and can have actions that fire on warning, violation, or success.
• Service Contracts – Agreements between your company and customers for a type of customer support, such as a paid support plan or a warranty. Service Contracts can contain Contract Line Items (the specific products or services covered).
• Entitlement Templates – Predefined entitlement terms that you attach to Products. When a Product is added to an Asset, an Entitlement is automatically created from the template, which is ideal for product-based warranties.

The Three Entitlement Models

The exam often expects you to pick the correct model for a business scenario:

1. Entitlements Only – Use when you simply need to verify what support a customer is entitled to and track milestones. No contract terms or renewals are tracked.
2. Entitlements with Service Contracts – Use when customers buy support plans with start and end dates, renewals, and terms that must be tracked in Salesforce. Entitlements are linked to the Service Contract.
3. Entitlements with Service Contracts and Contract Line Items – Use when support coverage varies by product within a single contract (for example, a contract that covers three different products with different warranty lengths). This requires Products and Price Books.

How Entitlement Processes Work

Step 1 – Enable Entitlement Management. In Setup, go to Entitlement Settings and enable Entitlement Management. Here you also choose options such as enabling Entitlement Versioning (strongly recommended), enabling Milestone Feed Items, enabling Milestone Stopped Time (so agents can pause the clock using the Stopped checkbox on the Case), and selecting whether entitlements can be looked up from Contacts, Accounts, or Assets on the Case.

Step 2 – Create Milestones. Milestones are created independently in Setup (Entitlement Management > Milestones) with a name, description, and a Recurrence Type:
• No Recurrence – The milestone occurs only once per record (for example, First Response).
• Independent – The milestone can occur multiple times whenever its criteria are met, and each occurrence is tracked separately (for example, every time a customer replies, a new response clock starts, even if an earlier one is still open).
• Sequential – The milestone can occur multiple times, but only after the previous occurrence is completed. The next one starts when the criteria are met again.

Step 3 – Create the Entitlement Process. Choose the process type (Case or Work Order), give it a name, and define:
• Entry Criteria – Conditions a record must meet to enter the process (for example, Case Status not equal to Closed). If no criteria are defined, all records with an entitlement using this process enter it.
• Exit Criteria – Conditions that cause the record to leave the process (commonly Case Status equals Closed). Once a record exits, milestones stop tracking.
• Business Hours – Optionally apply business hours at the process level so milestone countdowns only run during supported hours. Business hours can be set at the entitlement process, at the individual milestone, or inherited from the Case; the milestone-level setting takes precedence over the process-level setting.

Step 4 – Add Milestones to the Process. For each milestone you add, you configure:
• Time Trigger – The number of minutes (or hours/days converted to minutes) allowed to complete the milestone. For a two-hour first response, use 120 minutes.
• Start Time – Either Entitlement Process (the clock starts when the Case enters the process) or Milestone Criteria (the clock starts when the milestone's own criteria are met).
• Criteria – Filter conditions determining which records this milestone applies to. This is how you give different SLAs to different priorities: add the same "First Response" milestone three times with criteria Priority = High (60 minutes), Medium (240 minutes), and Low (480 minutes).
• Order – The sequence used when multiple milestones have overlapping criteria.
• Business Hours – Optional milestone-specific hours.

Step 5 – Add Milestone Actions. Each milestone supports three types of actions, each using time-dependent triggers measured relative to the milestone deadline:
• Warning Actions – Fire before the milestone is violated (for example, email the agent 15 minutes before the deadline).
• Violation Actions – Fire when the milestone is not completed in time (for example, update a custom field, send an email alert to the manager, or create a task).
• Success Actions – Fire when the milestone is completed on time.
The actions available are workflow-style actions: email alerts, field updates, tasks, and outbound messages. You can also trigger a Flow via a field update that is then evaluated by a record-triggered flow.

Step 6 – Activate the Process and Attach It to Entitlements. A process must be Active before it can be used. Create Entitlement records (manually, via data loader, or automatically through Entitlement Templates) and select the entitlement process in the Entitlement Process lookup. Then, when a Case is created with that Entitlement in its Entitlement Name field, the case enters the process and the milestones begin.

How Milestones Are Tracked and Completed

When a Case enters an entitlement process, Salesforce creates Case Milestone records for each applicable milestone, each with a Target Date, Completion Date, and status of Open, Completed, or Violated. Agents see this in the Milestone Tracker Lightning component (or the Case Milestones related list), which shows a countdown and highlights milestones that are approaching or past their deadline.

Milestones are completed in one of two ways:
• Manually – The agent marks the milestone complete in the Milestone Tracker.
• Automatically – An Apex trigger or a Flow updates the Case Milestone's Completion Date when a business event occurs (for example, when an outbound email is sent, the First Response milestone is completed). Automating completion is a best practice because it removes reliance on agents remembering to click.

The Stopped checkbox on the Case (when Milestone Stopped Time is enabled) pauses the milestone countdown, which is useful when waiting on the customer. The time while stopped is recorded in the Stopped Since and Stopped Time fields.

Entitlement Process Versioning

Once an entitlement process has been activated and applied to records, you cannot edit its milestones or criteria directly. Instead, with Entitlement Versioning enabled, you create a new version of the process, make your changes, activate the new version, and then choose which entitlements and in-progress cases should be updated to the new version. This preserves historical SLA accuracy for existing records. Expect a question that asks how to change an active process; the answer is "create a new version."

Permissions and Visibility

Administrators need the Manage Entitlements permission to configure Entitlement Management. Support users need at least Read access on Entitlements (and Service Contracts if used) and must have the Entitlement Name field on the Case page layout. The Entitlements related list should be added to Account, Contact, and Asset layouts so agents can verify coverage before creating a case. Entitlement Management is available in Service Cloud (Enterprise, Performance, Unlimited, and Developer editions).

Exam Tips: Answering Questions on Entitlement Processes and Milestones

1. Identify the keywords. Words such as SLA, response time, resolution time, support level, warranty, and track whether agents met deadlines point to Entitlement Management. If the scenario only talks about reassigning a case after a period of inactivity, that is an Escalation Rule, not a milestone.

2. Match time requirements to milestones, not escalation rules. "Cases must receive a first response within one hour" equals a milestone with a 60-minute time trigger. "Notify the manager if that doesn't happen" equals a violation action. "Warn the agent 10 minutes before" equals a warning action.

3. Different SLAs per customer tier equals different Entitlements or Entitlement Processes. Gold and Silver customers would typically have separate entitlement processes (or separate entitlements pointing to different processes). Different SLAs per case attribute, such as Priority, within the same tier equals the same milestone added multiple times with different criteria and time triggers.

4. Know when the clock starts. If the deadline should start when the case is created, choose Entitlement Process as the start time. If it should start when a specific condition becomes true (for example, Status changes to Escalated), choose Milestone Criteria.

5. Recurrence types are a favourite. One-time deadline equals No Recurrence. A response clock that restarts every time the customer replies, with each tracked separately, equals Independent. A clock that can repeat but only after the previous occurrence is completed equals Sequential.

6. Business hours questions. If the SLA should only count during support hours (for example, 8 a.m. to 6 p.m. weekdays), apply Business Hours to the entitlement process or the milestone. Remember milestone-level business hours override process-level hours.

7. Choosing the entitlement model. Just verifying support eligibility equals Entitlements only. Tracking contract terms, dates, and renewals equals Entitlements with Service Contracts. Coverage that differs per product within one contract equals Entitlements with Service Contracts and Contract Line Items. Automatically creating entitlements when a product or asset is sold equals Entitlement Templates.

8. Modifying an active process. If a process is already in use and needs changes, the correct answer is to enable Entitlement Versioning and create a new version, then apply it to selected entitlements and cases.

9. Pausing the clock. When the scenario says the deadline should not count while waiting on the customer, the answer involves enabling Milestone Stopped Time and using the Stopped checkbox on the Case.

10. Automating completion. If the question asks how to complete a milestone automatically when an email is sent or a field changes, the answer is Apex or a Flow that updates the Case Milestone's Completion Date, not a workflow rule on the Case.

11. Setup order matters. If asked about sequence: enable Entitlement Management, create Milestones, create the Entitlement Process and add milestones and actions, activate the process, create Entitlements and link them to the process, and then add the Entitlement lookup to the Case layout.

12. Eliminate distractors. Options that mention Omni-Channel, Case Assignment Rules, Case Teams, or Knowledge are usually wrong for SLA-tracking scenarios. Options mentioning Escalation Rules are wrong when the requirement is to measure or report on deadline compliance rather than simply reassign a case.

Quick Reference Summary

• Entitlement equals what the customer is entitled to.
• Entitlement Process equals the timeline of required steps.
• Milestone equals a time-bound step with warning, violation, and success actions.
• Service Contract and Contract Line Items equal paid agreement terms and per-product coverage.
• Entitlement Template equals auto-created entitlements from Products.
• Versioning equals how you change an active process.
• Milestone Tracker equals where agents see countdowns and mark completion.

Master these relationships and the scenario-to-feature mapping above, and Entitlement Process and Milestone questions on the Advanced Administrator exam will become some of the most predictable points you can earn.