Last week we gave cases a countdown clock. This week, a client question that follows almost immediately: “Our gold customers bought twenty supported cases a year with faster response times. Our standard customers get eight, best effort. Where does Dynamics keep track of THAT?” The honest answer in most organizations is: in a PDF, in the account manager’s head, and in an awkward email thread every time someone asks. The system answer is entitlements, and they are the missing half of the SLA story.
In this post we will create an entitlement end to end in Dynamics 365 Customer Service: the support allocation, the SLA that rides along with it, activation, and what agents actually see on the case. If the SLA is the promise with a clock, the entitlement is the receipt that says who bought which promise.
Why the Usual Approaches Fall Short
Teams without entitlements track support contracts the way they track gym memberships they meant to cancel — vaguely. The contract PDF lives in SharePoint. The case count lives in a spreadsheet someone updates on Fridays. And the premium SLA lives in the team’s collective memory: “Contoso is gold, be quick with those.”
The failure mode is predictable. A customer with four remaining supported cases opens their fifth, nobody notices until the invoice conversation, and now your account manager is negotiating retroactively — the weakest position in commercial life. Or the reverse: a gold customer quietly gets standard treatment because the agent had no way to know better. Memory is not a service tier.
An entitlement fixes this by making the contract machine-readable: how much support, for which customer, over which period, through which channels, against which SLA. Dataverse counts so nobody has to.
Prerequisites
- Dynamics 365 Customer Service and access to the Copilot Service admin center.
- An active SLA if you want the entitlement to carry one — we will reuse the Standard Case SLA from last week’s SLA walkthrough.
- A sandbox. Mine is my demo environment; yours should not be production.
Step 1 — Read the Contract Before You Touch the Form
Every field on the entitlement form answers a question the contract already answers, so start there. What did the customer buy — a number of cases, or a number of hours? When a case is opened but later cancelled, should it still count? Does the deal cover every product and every contact at the account, or a named few? Write those answers down first. An entitlement is data entry only if someone has already done the thinking; otherwise it is guesswork with a Save button.
Step 2 — Create the Entitlement
In the Copilot Service admin center, go to Service terms, and under Entitlements select Manage, then New. The form is short and every line matters:
- Name: name it for the customer and the tier — I am using Contoso Ltd – Gold Support.
- Primary Customer: the account that signed the contract.
- Start Date / End Date: the contract period. Entitlements with a future start date sit politely in Waiting status and activate themselves on the day.
- Restrict based on entitlement terms: if Yes, agents cannot create cases against this entitlement once the terms hit zero. Powerful, and blunt — more on this below.
- SLA: the promise that travels with the tier. Gold gets the two-hour clock.
- Allocation Type: Number of cases or number of hours.
- Decrease Remaining On: Case Resolution is the generous reading (a cancelled case gives the credit back); Case Creation is the strict one. Match the contract, not your mood.
- Total Terms: what they bought. Twenty, for our gold tier.
Step 3 — The Sections That Appear After You Save
Save the record and three subgrids light up. Entitlement Channel lets you split the allocation by channel — say, fifteen cases by email but only five by phone — and Dataverse keeps a separate remaining count per channel. Products restricts the entitlement to specific products; leave it empty and everything is covered. Contacts restricts who at the customer may use it; leave it empty and anyone at the account qualifies. The pattern across all three is the same: empty means everything, filled means only these. Decide on purpose, because agents will trust whatever the system enforces.
Step 4 — Activate It
A draft entitlement is a note to self. Select Activate on the command bar and the record becomes read-only, the Remaining Terms counter arms itself, and the entitlement starts appearing in lookups on cases for that customer. Like SLA items, an active entitlement is locked — to change it you deactivate first, which is mildly annoying and entirely correct, because a support contract should not be editable mid-flight without ceremony.
Step 5 — Put It on a Case
Open a case for that customer and set the Entitlement field — the lookup only offers active entitlements belonging to the case’s customer, which is exactly the guardrail you want. The moment it is set, the entitlement’s SLA governs the case, and when the case resolves, the remaining terms tick down by one. Set the entitlement as default on its command bar and new cases for that customer pick it up automatically — worth doing for any customer with exactly one active contract, which is most of them.
⚠️ Important: think twice before setting Restrict based on entitlement terms to Yes. It hard-blocks case creation when the allocation runs out — which sounds like governance until a production-down customer calls on a Friday and the system refuses to open a ticket. Most teams do better with No, plus a view of entitlements sorted by remaining terms so the renewal conversation happens before the counter hits zero. A blocked case is not a collected invoice.
Limitations and Good Habits
- Use entitlement templates for standard tiers. If gold, silver, and bronze look the same for every customer, define them once under Entitlement templates and stamp out copies — hand-typing tiers invites hand-typed mistakes.
- Renew, don’t resurrect. When a contract rolls over, use Renew on the expired record — it drafts a fresh copy and keeps the history honest, instead of quietly stretching last year’s dates.
- The counter only counts what agents record. If cases sneak in without the entitlement set, remaining terms lie. Defaults and auto-application close most of that gap; a weekly view of entitlement-less cases for entitled customers closes the rest.
- One customer, many entitlements is fine — different products, different periods. The case lookup shows all active ones, and the agent picks. Just name them so the choice is obvious in a hurry.
Closing Thought
An entitlement is the wristband at the venue: it does not make the music better, it just proves what you paid for — and gets you into the fast lane you bought. Last week we built the clock; this week the receipt that decides who gets which clock. Model the contract once, activate it, and let the counter do the remembering. Your account managers will negotiate renewals from a report instead of an apology, and your agents will finally know who bought the front row.
