Weekly analytics show escalation rate jumped from 8% to 28% after a knowledge source update. What is the best immediate operational response?
Select an answer to reveal the explanation.
Short Explanation and Infographic
A sudden escalation spike after a knowledge change is a smoke alarm — check what changed, read transcripts, fix or roll back, then watch the rate fall.
Full explanation below image
Full Explanation
Operational monitoring ties metric deltas to recent releases. Knowledge regressions often increase fallback/escalate behavior.
Option A is correct.
Options B–D avoid root cause or worsen governance.
Exam tip: Change management + analytics + transcripts = production support loop.