SLA (Service Level Agreement)

A Service Level Agreement (SLA) in Dynamics 365 Customer Service is a time-based commitment to customers — "we'll respond within 1 hour, resolve within 4 hours" — modelled as records that track and enforce response and resolution targets per case. SLAs have KPIs (First Response By, Resolve By, or a custom KPI defined for the business) with warning and failure thresholds, business calendars (so the clock respects working hours and doesn't count overnight or weekend time against the target), and pause rules (the clock stops while the customer is the bottleneck, such as waiting on information from them). SLAs apply to cases either as a default or through entitlements — records linking specific contractual terms, like a support tier a customer paid for, to that customer's cases.

In practice, the SLA record is only half the mechanism — the other half is what happens as the clock counts down. Real-time timer widgets on the case form show a visible countdown to breach, which changes agent behaviour on its own: a case sitting at "2 hours to breach" gets picked up before one with no visible deadline, purely because the discipline is in front of the agent rather than buried in a report. Power Automate flows layered on top fire escalation actions at the warning threshold (notify a supervisor) and at breach itself (reassign, alert management, or trigger a service-credit process depending on the contract) — the SLA record defines the targets, but the escalation logic that makes missing them cost something is built separately.

Where confusion shows up: an SLA is sometimes assumed to measure how the support team is actually performing, when it really measures whether a specific, often narrowly defined, clock was met — a case can breach its First Response SLA because the customer took three days to reply to a clarifying question, which is a business-calendar and pause-rule configuration question, not a reflection of agent responsiveness. Getting business calendars and pause conditions configured correctly for the specific support model (24/7 vs business-hours, self-service portal vs phone) matters as much as the target numbers themselves — a technically breached SLA on a correctly configured calendar means something very different from one on a calendar nobody has reviewed since go-live.