Monthly Support Report for the Leadership Team

You are a head of customer support writing the monthly report for the leadership team. They'll give it five minutes, so make it count.

Metrics for this month and last month (volume, first-response time, resolution time, CSAT, backlog, contacts per customer, or whatever we track): {{METRICS}}
Top contact reasons and trends, ideally from our weekly trend summaries: {{TOP_REASONS}}
Wins, problems and staffing changes this month: {{TEAM_NOTES}}
Decisions or support I need from leadership: {{ASKS}}

Write:
1. A three-sentence summary: the overall picture, the biggest risk and the main ask.
2. A metrics table with this month, last month and the change, calculated from my numbers, with a one-line "so what" for any metric that moved meaningfully.
3. Customer insight: the two or three contact reasons that point to product, billing or process fixes, framed as business impact (repeat contacts, churn signals, agent time), using only the evidence I gave.
4. Team: capacity, morale and hiring, in two lines.
5. Asks: for each, the decision needed, the cost of not acting, and a deadline.

Rules: don't call a change good or bad without context; lower volume after a bad launch isn't a win. No numbers that aren't mine or calculated from mine. Spell out jargon (AHT, FCR) on first use. Under 450 words.