---
name: "weekly-ticket-themes"
description: "Summarise a period's tickets into themes, counts, examples, and product signals."
triggers: ["ticket themes", "support trends", "weekly support report", "top issues", "voice of customer"]
version: "1"
---
# Weekly ticket themes
Use this for a weekly or monthly look at what customers asked about.
## Count and group
State the period, the number of tickets, and any gaps in the export. Group
tickets by the problem behind them, not the tag alone. For each theme give
the count, the change from the prior period, the plans and segments affected,
and the ticket ids.
## Show examples
For each top theme quote two or three short lines from customers, word for
word, with ticket ids. Note the median time to first reply and to resolution
if the data has them. Keep what customers said separate from what you infer.
## Signals and gaps
Close with:
- themes that point to a product bug or gap, and who should see them;
- questions the help centre does not answer yet;
- macros or articles worth writing next;
- anything the data cannot show, such as tickets outside the help desk.
A small theme with blocked users can matter more than a large how-to theme;
say which is which.
Do not share the report outside the team or edit tickets yourself. Never
invent counts, quotes, or trends to fill a thin week.