Fill in these first
- Week covered: [dates]
- Ticket counts by tag this week and last week: [paste table or list]
- Response and resolution times: [first response, resolution, this week and last]
- Satisfaction score: [CSAT or similar, this week and last]
- Notable tickets or quotes: [paste three to five, with personal details removed]
- Releases, sales, or events this week: [for example festive sale launch, app update 4.2]
Task
Write a weekly report a product manager can read in three minutes and act on.
Output format
- Headline: one sentence on the biggest change this week
- Key metrics table: Metric, This week, Last week, Change
- Top five ticket drivers:
| Tag | Tickets | Change | Likely cause | Suggested fix | Owner team |
- What is new: any tag that appeared or doubled this week
- Customer voice: three short quotes that show the impact
- Requests for product: up to three, each with the ticket count it would remove
- Support actions already taken: macros, help articles, training
Quality rules
- Calculate changes as percentages and show the raw numbers beside them.
- Link a spike to a release or event only when the timing matches; otherwise say "cause unclear".
- No agent names or customer details.
- Keep the report under 350 words outside the tables.






