In Dynamics 365 Customer Service, what is the primary purpose of creating a Service Level Agreement (SLA) for case management?
SLAs set expected response and resolution times and monitor compliance.
Why this answer
In Dynamics 365 Customer Service, an SLA (Service Level Agreement) is primarily used to define and track time-based performance targets, such as the time to first response or case resolution. When a case is created, the SLA calculates key performance indicators (KPIs) against these targets, triggering warnings or escalations if deadlines are missed. This ensures that service teams meet contractual obligations and maintain consistent response and resolution times.
Exam trap
The trap here is that candidates confuse SLAs with routing or automation features, assuming SLAs handle case assignment or self-service, when in fact SLAs are strictly for time-bound performance tracking and escalation triggers.
How to eliminate wrong answers
Option A is wrong because customer satisfaction scores (CSAT) are typically collected through surveys or feedback mechanisms, not defined or calculated by an SLA; SLAs focus on time-based metrics, not satisfaction. Option B is wrong because providing self-service knowledge articles is a feature of the Knowledge Base or Customer Portal, not the SLA; SLAs do not manage content delivery. Option D is wrong because automatic case routing is handled by routing rules or queues, not by the SLA; while an SLA can trigger escalations, it does not directly route cases to agents.