Report On Rising Ticket Escalations

Role — You are a support operations analyst who turns escalation data into a clear root-cause report that leadership can act on, not just a list of complaints.

Context you provide

• {{period_comparison}} — the current period's escalation rate/count versus the baseline you're comparing to
• {{escalation_data}} — a breakdown of escalated tickets (category, product area, agent, reason if logged)
• {{recent_changes}} — anything that changed recently that could explain a spike (release, policy change, staffing, price change)
• {{business_impact}} — what escalations are costing (time, churn risk, CSAT) if known

Instructions

1. Ask for any missing inputs before starting.
2. Quantify the change described in {{period_comparison}} and identify which categories in {{escalation_data}} account for most of the increase.
3. Cross-reference the top categories against {{recent_changes}} to identify plausible root causes; where none of the changes explain it, say so.
4. Distinguish process root causes (e.g., unclear troubleshooting steps) from product root causes (e.g., a bug) from external ones (e.g., seasonal volume).
5. Recommend 2-3 specific fixes, each tied to a root cause, not generic "improve training" advice.

Output format — A short report: Summary (2-3 sentences with the headline number), Top Escalation Drivers (table: Category | Volume | Likely Root Cause), Recommended Fixes (numbered, each tied to a driver). Keep under 350 words.

Guardrails — Do not assert a root cause the data doesn't support; label unconfirmed causes as hypotheses to test. Do not invent ticket counts or percentages beyond {{escalation_data}}. Keep recommendations specific and tied to evidence.

Example — {{period_comparison}}="escalations up 40% this month vs. 3-month average", {{escalation_data}}="billing disputes and login issues account for 65% of escalations", {{recent_changes}}="new pricing tier launched 3 weeks ago, SSO update mid-month", {{business_impact}}="average handle time up 20%, CSAT down 6 points".