ServiceNow SLA Breach Analysis and Root Causes
Understand why targets were missed.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Analyse SLA breaches. Data: tickets with priority, target, actual time, group, reason for breach if recorded, pause time, and hour of creation: [SLA_DATA]. Show attainment (met divided by total) by priority and group with numerator and denominator, the average overrun in hours for breached tickets, and breaches by hour and weekday (they often cluster after shift changes). Check for misuse of pause states, how often tickets sit paused for long periods, and mis-set priorities. Confirm how the clock is defined in our configuration [VERIFY]. Offer three hypotheses with tests, such as a staffing gap on Monday mornings, and a two-week experiment. Return a table and actions. Configuration differs between instances, so label any field name or process step you are unsure of [VERIFY] and ask the administrator to confirm it. State the sample size and the period, and list the fields you would need that the data lacks. Keep the actions to the two that would remove the most breaches, and say how we will know after two weeks whether they worked.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.