wowprompt

Weekly support ticket trends report for the product team

A one-page weekly report that turns raw ticket counts and tags into trends, top causes, and specific requests for the product team. Use it every Monday so recurring problems get fixed at the source instead of answered again and again.

A weekly support report with headline metrics, a table of top ticket drivers with week-on-week change, and three requests for the product team
The output this prompt produced, unedited.

The prompt

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

  1. Headline: one sentence on the biggest change this week
  2. Key metrics table: Metric, This week, Last week, Change
  3. Top five ticket drivers:

| Tag | Tickets | Change | Likely cause | Suggested fix | Owner team |

  1. What is new: any tag that appeared or doubled this week
  2. Customer voice: three short quotes that show the impact
  3. Requests for product: up to three, each with the ticket count it would remove
  4. 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.
support ticket reportweekly support reportticket trends analysisvoice of customer reportsupport metrics

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity