Entitlements and Service Contracts

Why Entitlements and Service Contracts Matter

In any organization that sells support agreements, warranties, or service-level agreements (SLAs), the service team must know exactly what level of support each customer is owed and whether the team is meeting its commitments. Without a structured way to track this, agents may provide premium support to customers who have not paid for it, miss contractual response deadlines, or fail to escalate at-risk cases. Salesforce Entitlement Management solves this problem by letting you define, track, and enforce support commitments directly inside Service Cloud.

For the Salesforce Advanced Administrator exam, Entitlement Management falls under the Advanced Cloud Applications domain, which tests your knowledge of Sales Cloud and Service Cloud features. You are expected to understand the components of Entitlement Management, how they relate to one another, how to set them up, and which model fits a given business scenario. This topic frequently appears in scenario-based questions, so a solid conceptual understanding is essential.

What Is Entitlement Management?

Entitlement Management is a suite of features in Service Cloud that helps support teams deliver the correct level of service to customers. It answers two core questions:

1. Is this customer entitled to support? (and to what kind of support)
2. Are we meeting the service levels we promised?

Entitlement Management has four main building blocks:

1. Entitlements
An entitlement is a unit of customer support, such as "phone support," "web support," or "premium 24/7 support." Entitlements are typically associated with an account, a contact, an asset, or a service contract. When an agent creates a case, they can select the entitlement that applies, which lets Salesforce verify the customer is eligible and apply the correct SLA process. Key entitlement fields include Start Date, End Date, Status (Active, Expired, Inactive), Type, and the optional Entitlement Process. Entitlements can also have a per-incident counter (Cases Per Entitlement and Remaining Cases) to limit how many cases a customer can log.

2. Service Contracts
A service contract represents the actual agreement between your company and the customer, such as a warranty, subscription, or maintenance agreement. Service contracts are the "paper" behind the entitlements. One service contract can include many entitlements. Service contracts can also contain Contract Line Items, which are the specific products covered by the contract (for example, a contract covering 50 laptops and 10 printers). Contract line items link to products in your price book and can themselves be linked to entitlements, allowing support to be tracked down to the product level.

3. Entitlement Processes
An entitlement process is a timeline that defines the steps (milestones) your support team must complete to resolve a case or work order. It specifies when the process starts and ends, which business hours apply, and what happens if a milestone is missed. There are two types of entitlement processes: Case and Work Order. An entitlement process is attached to an entitlement, and when a case is linked to that entitlement, the process runs against the case.

4. Milestones
Milestones are the required steps within an entitlement process, such as "First Response" within 2 hours or "Resolution" within 24 hours. Each milestone has a target time, and you can attach success actions, warning actions, and violation actions that fire automatically. These actions are workflow-style actions: create a task, send an email alert, update a field, or send an outbound message. Milestones can be recurring (for example, a "Customer Response" milestone that repeats each time the customer replies). Milestone types include No Recurrence, Independent, and Sequential.

How It All Fits Together

Think of the hierarchy this way:

Account → has a Service Contract → which has Contract Line Items (products) → covered by Entitlements → governed by an Entitlement Process → made up of Milestones → applied to Cases (or Work Orders).

When an agent creates a case and selects an entitlement that has an entitlement process attached, Salesforce starts tracking the milestones. The case detail page shows a milestone tracker (a countdown clock) so agents can see how much time remains before each milestone is violated. If a milestone is missed, the violation actions run automatically, for example notifying a manager or reassigning the case.

Entitlement Models

Salesforce supports three entitlement models, and choosing the right one is a classic exam question:

Entitlements Only – Use when you want to verify eligibility and apply SLAs but do not need to track the contracts or specific products. Simplest to set up. Entitlements are linked directly to accounts, contacts, or assets.

Service Contracts with Entitlements – Use when you need to track the contractual agreement itself (dates, terms, renewals) along with the entitlements it provides. Entitlements are associated with service contracts.

Service Contracts with Contract Line Items and Entitlements – Use when support coverage varies by product. Entitlements are linked to contract line items, which are linked to products. This is the most detailed model and is appropriate when a customer buys different products with different support levels under one contract.

Key Setup Steps

1. Enable Entitlement Management in Setup under Entitlement Settings. Here you also choose whether to enable entitlement versioning, select which entitlement lookup to use on cases, and optionally enable milestone feed items.
2. Define Business Hours (and optionally Holidays). Milestone timers respect business hours so a 4-hour milestone does not count overnight if your support team is closed. Business hours can be set on the entitlement process, the entitlement, the case, or the org default; Salesforce uses the most specific one available in that order.
3. Create Milestones (Setup > Milestones).
4. Create an Entitlement Process, set entry and exit criteria (for example, start when case is created, exit when case is closed), and add milestones with their time triggers and criteria.
5. Add success, warning, and violation actions to milestones.
6. Activate the entitlement process.
7. Create Entitlement Templates if you want entitlements to be automatically created when products are added to assets.
8. Grant users access through object permissions (Entitlements, Service Contracts, Contract Line Items), add related lists to page layouts, and expose the fields and milestone tracker on the case layout.
9. Optionally set up Entitlement Versioning to update active entitlement processes without disrupting cases already in progress.

Important Details to Remember

• The Milestone Tracker component on the case page shows agents time remaining; milestones become "completed" when the Completion Date is populated, which is typically done by automation (such as a flow that sets the milestone complete when the case status changes) or manually by the agent.
• Stopped time: You can enable the "Is Stopped" field on cases so that when a case is waiting on the customer, the milestone clock pauses.
• Entitlement versioning lets you create new versions of an entitlement process and choose whether existing entitlements use the new version.
• Entitlement Templates are linked to products and automatically generate entitlements when an asset for that product is created.
• Service contracts and entitlements are separate from the standard Contract object used in Sales Cloud. Do not confuse the two on the exam.
• The Entitlement Name lookup on the case is how the process gets applied. You can also auto-populate it using flows or via Email-to-Case and Web-to-Case rules based on the account or asset.
• Milestone actions use the same action types as workflow rules (Email Alert, Field Update, Task, Outbound Message).
• Milestones can be made sequential (next one starts when the previous completes) or independent (start based on their own criteria).
• Milestones are also available for Work Orders (Field Service), using a Work Order entitlement process.

Exam Tips: Answering Questions on Entitlements and Service Contracts

Tip 1: Match the scenario to the right model. If the question mentions only verifying eligibility and SLAs, choose Entitlements Only. If it mentions tracking warranties, agreements, renewals, or contract dates, you need Service Contracts. If it mentions different support levels for different products under one agreement, you need Contract Line Items.

Tip 2: Know the vocabulary precisely. Exam questions often test whether you can distinguish Entitlement (the unit of support), Service Contract (the agreement), Entitlement Process (the timeline), and Milestone (the step). If a question asks how to enforce a "first response within 1 hour," the answer involves a milestone inside an entitlement process, not a workflow rule or validation rule.

Tip 3: Remember that automation lives on milestones. When asked how to notify a manager when a support deadline is about to be missed, the answer is a warning action on the milestone. When the deadline has already been missed, it is a violation action. When the step is completed on time, it is a success action.

Tip 4: Business hours affect timing. If a scenario describes SLA clocks that should not run at night or on weekends, the correct answer involves assigning Business Hours (and Holidays) to the entitlement process or entitlement. Know the order of precedence: entitlement process milestone business hours, entitlement business hours, case business hours, then org default.

Tip 5: Watch for the "existing cases" wrinkle. If a question asks how to change an entitlement process that is already active and in use on open cases, the answer is Entitlement Versioning. Simply editing an active process is not permitted without versioning.

Tip 6: Setup prerequisites. Questions may ask what must be done before users can work with entitlements. Remember: enable Entitlement Management, set object permissions on the profile or permission set, add fields and related lists to page layouts, and add the milestone tracker component to the case record page.

Tip 7: Don't confuse objects. Service Contract is not the Sales Cloud Contract object. Entitlements are not Cases. Contract Line Items are not Opportunity Products, although they do reference Products and Price Books.

Tip 8: Entitlement Templates and Assets. If a scenario describes automatically creating support entitlements whenever a customer buys a product, the answer is Entitlement Templates attached to the Product, which generate entitlements when an Asset is created.

Tip 9: Eliminate distractors. Wrong answers often suggest using Escalation Rules, Workflow Rules, or Validation Rules to enforce SLAs. While escalation rules can escalate cases based on age, only Entitlement Management provides per-customer SLA tracking with milestones. If the question includes customer-specific support levels, Entitlement Management is almost always the correct direction.

Tip 10: Read for the user's role. Questions may describe what an agent sees (milestone tracker, countdown) versus what an administrator configures (processes, milestones, actions). Make sure your answer addresses the correct perspective.

Sample Question Walkthrough

Universal Containers sells hardware with a one-year warranty. Some customers purchase a Premium Support add-on for specific products that guarantees a 2-hour first response, while standard customers receive a 24-hour response. Support managers want to be alerted if a first response is at risk of being late. What should the administrator configure?

Analysis: Support varies by product under a warranty agreement, so you need Service Contracts with Contract Line Items and Entitlements. The 2-hour and 24-hour response requirements are milestones in two different entitlement processes (or one process with criteria-based milestones). The at-risk alert is a warning action on the First Response milestone that sends an email alert to the manager. Any answer suggesting escalation rules alone or workflow rules alone would be incorrect.

Summary

Entitlement Management lets Service Cloud organizations define what support customers are owed and automatically enforce service levels. Entitlements define the support, service contracts define the agreement, contract line items define the covered products, entitlement processes define the timeline, and milestones define the measurable steps with automated success, warning, and violation actions. For the exam, focus on choosing the correct entitlement model for a scenario, understanding how milestones and business hours drive SLA timing, knowing where automation is configured, and recognizing when entitlement versioning or entitlement templates are the right answer. Master these relationships and you will handle Entitlements and Service Contracts questions with confidence.