Entitlements in Customer Service

Entitlements in Dynamics 365 Customer Service represent what a customer is entitled to — the contractual scope of their service relationship. They're how support organisations enforce contract terms automatically: this customer paid for 24/7 support; this customer gets only email; this customer has 10 incidents remaining on their contract; this customer's premium SLA expires next month.

The model. An entitlement record carries:

• Customer — the account or contact who has the entitlement.
• Products — which products the entitlement covers (e.g. only premium-tier software, not consumer-tier).
• Start and end dates — the validity period.
• Channels — which channels are covered (phone, email, chat, SMS).
• Entitlement terms — what's purchased: number of incidents, support hours, or coverage type (per-incident, per-period, unlimited).
• Restricted contacts — optional list of specific named contacts authorised to use this entitlement.
• SLA — the SLA that applies to cases under this entitlement.
• Status — Draft, Active, Cancelled, Expired, Renewed.

Allocation types.

• Per-incident — a number of cases the customer can open.
• Per-period (hours) — total support hours per period.
• Per-period (incidents) — total cases per period.
• Unlimited — no quantity restriction.

Allocations decrement as cases consume them; once exhausted, new cases either block or require explicit override.

Case association. When a case is created, the system matches it to the most applicable entitlement based on customer, product, channel, and current date. The active entitlement is recorded on the case, drives the SLA assignment, and decrements the remaining allocation.

Manual override. Agents can override the entitlement on a case if business rules warrant — e.g. accept an over-quota case as a customer-satisfaction gesture. Overrides are logged for audit.

Multi-entitlement scenarios. A customer can have multiple active entitlements (different products, different terms). The matching logic picks the most specific one for each case; ties default to oldest start date or to a configured priority.

Lifecycle and renewal. Entitlements have a renewal date. Power Automate flows can trigger renewal workflows N days before expiry — notify the account manager, generate a renewal opportunity in Sales, propose new terms. Mature support orgs treat entitlement renewal as a sales motion, not an administrative one.

Reporting. Entitlement reporting answers:

• Which customers are near depletion (sales upsell trigger).
• Which entitlements are about to expire (renewal motion).
• Average utilisation per customer / per tier (pricing analysis).
• High-touch customers (potential health-of-account signal).

Integration with Sales. Entitlements often originate as contracts in Dynamics 365 Sales — closed-won opportunities for support contracts create the corresponding entitlement records in Customer Service. Power Automate flows or built-in integrations handle the handoff.

Common patterns.

• Tiered support — Bronze (basic email, 30 incidents/year), Silver (phone + email, 100/year, 4-hour SLA), Gold (24/7 omnichannel, unlimited incidents, 1-hour SLA, named CSM).
• OEM-style — entitlement scoped per product, per channel, with strict tracking for warranty-period cases.
• Pay-per-incident — entitlements track a balance that the customer tops up; once depleted, cases either block or charge.

Limits. Sophisticated subscription billing with mid-period entitlement changes, prorations, and bundled-product allocations may need a specialist tool — Dynamics 365's Subscription Billing on F&O, or a dedicated subscription-management platform integrated with Customer Service.

Operational reality. Entitlements are operational discipline. Configured well, they enforce contractual terms invisibly and surface upsell / renewal moments. Ignored, they're forgotten records that don't reflect actual service delivery.