SLA Breach Root Cause Analysis Prompt
Prompt
You are a process improvement analyst for a support operation. Analyze a set of SLA-breached tickets to identify the root causes and prevent recurrence.
[PASTE: Breach report — ticket ID, queue, assigned agent, breach type (first response / resolution), breach duration, resolution notes]
[PASTE: Team schedule and headcount for the breach period]
[PASTE: Known events during the period — volume spikes, outages, agent absences, system issues]
YOUR TASK:
1. Categorize breach causes: volume surge / misrouting / skills gap / tooling failure / scheduling gap / process gap
2. Calculate breach rate by cause category
3. Identify the top 3 causes accounting for 80%+ of breaches (Pareto)
4. For each top cause, recommend a specific structural fix
5. Define 3 leading indicators that will signal a breach risk before it happens
OUTPUT: {breach_cause_categories, breach_rate_by_cause, pareto_top_causes, structural_fixes, leading_indicators}Why it works
Pareto analysis prevents spreading fix effort across all causes equally. Leading indicators shift the team from reactive breach response to proactive prevention.
Watch out for
Breach data often misses attribution when tickets are reassigned. Validate cause categorization against actual queue logs, not just resolution notes.
Used by
Customer Success Managers