Question 1
A global e-commerce company, Adventure Works, is configuring Dynamics 365 Customer Service to manage customer inquiries from their online portal. They have a three-tiered support structure: Tier 1, Tier 2, and Tier 3. A new requirement states that if a Tier 1 agent cannot resolve a case within two business hours and the case priority is 'High', the case must be automatically escalated to a Tier 2 queue. The escalation process must also update a custom field on the case record named 'Escalation Timestamp' with the current date and time. Which component is the most appropriate and efficient for implementing this specific time-based escalation logic?
Answer and explanation
Correct answer: B
SLAs are the native and intended feature for time-based service management in Dynamics 365. An SLA KPI can be configured to track the 'First Response By' or a custom metric. Setting a failure time of two business hours and defining failure actions (like rerouting to a queue and calling a flow/workflow to update a field) is the most robust, maintainable, and correct approach. Real-time workflows cannot have wait conditions, and background workflows are less precise for time-critical SLAs. Business rules cannot handle time-based triggers or reassignments.