---
schema: 9
type: app
id: 22
title: Weekly ticket summary
description: Drop last week's help desk export into Claude and get the themes, counts and urgent tickets your team should read first.
created: 2026-10-27
updated: 2026-11-01
sources:
  - note:258
attributes:
  role: support
  repo: h1902y/weekly-ticket-summary
  piece: weekly-ticket-summary
  pillar: ai-agents
  channels: [website]
  status: published
  version: 1.2.6
  released: "2026-10-31"
  format: [claude-plugin, cf-lite]
published:
  - website 2026-10-29 https://h1902y.com/library/weekly-ticket-summary
---

## What it does

Every week someone on the support team reads through last week's tickets to answer two questions: what keeps coming up, and who needs a reply today. This app does that first pass.

You give it last week's ticket export. It groups the tickets by theme, counts each one, quotes one real ticket per theme, and puts urgent and overdue tickets on top with how long they've waited. Then it writes a short summary you can read out at your Monday stand-up.

A person still decides what to do. The app makes sure nobody gets missed.

**For:** support and ops leads who review a ticket queue every week. No coding.

![The summary Claude built from the sample tickets](./screen-summary.webp)

## Steps

1. **Export last week's tickets** from your help desk as a CSV. Keep the message, status, priority and "hours open" (or created date) columns. No export handy? Use the [sample tickets](./sample-tickets.csv).
2. **Open a new chat in Claude** and attach the file.
3. **Paste the prompt** below and send it.
4. **Read "Reply to these first"** before anything else, and check two of the quotes against the file.
5. **Next week:** drop the new export into the same chat and ask again, or install the skill from **Where do you want it?** and just say "weekly ticket summary". You get the same shape every week.

## The spec

- **Input:** one week of tickets as a CSV export from any help desk (Zendesk, Freshdesk, Help Scout, Intercom or a spreadsheet). Try it first with the [sample tickets](./sample-tickets.csv): 40 made-up tickets from a made-up company.
- **Output:** three parts, in the same shape every week: *Reply to these first*, *Themes* (count, share and one quote each) and a 3–5 sentence *Summary*.
- **Rules:**
  - urgent means high priority, past its target time, or an angry or repeat customer;
  - every count matches the file, and every quote is word for word;
  - missing columns are named, never made up.
- **Done when:** you can read the summary in two minutes, and every urgent ticket in the file is on the list.

## The prompt

```text
Build me a small app from this ticket export. Group the tickets by theme, count each theme and quote one real ticket for each. Put the urgent and overdue ones on top, with how long each has been waiting. Write a short summary my team can read.
```

This is the prompt from the video. The skill below is the app: a script does every count and sort and checks Claude's answers against the export, and Claude does the finding and drafting (which customers are angry or repeat, the themes, the quotes and the summary), so the result keeps the same shape every week.

## Example output

What the skill gave back for the sample tickets (the urgent list is cut to five of ten):

**Weekly ticket summary: 40 tickets**

**Reply to these first (10)**

| Ticket | Customer | Problem | Waiting | Why |
|---|---|---|---|---|
| TB-4212 | Northgate Plumbing Supply | Promised refund still missing | 7.9 d | High priority; 166 h past 24 h SLA; third time asking; says cancelling if not fixed today |
| TB-4221 | Riverstone Hardware | Sync still broken after ticket closed as fixed | 4.2 d | High priority; 76 h past 24 h SLA; repeat contact, angry |
| TB-4218 | Ironwood Fitness | Paid invoices show unpaid, month-end close blocked | 3.3 d | High priority; 56 h past 24 h SLA |
| TB-4238 | Ironwood Fitness | Update changed amounts on 12 sent invoices | 8 h | Urgent priority; 4 h past 4 h SLA; angry |
| TB-4230 | Northgate Plumbing Supply | Whole team locked out, payroll to run | 5 h | Urgent priority; 1 h past 4 h SLA |

**Themes**

| Theme | Tickets | Share | Example |
|---|---|---|---|
| Bank and payment sync | 8 | 20% | "Paid invoices still show as unpaid. Our books are wrong and month-end close is blocked." (TB-4218) |
| Billing and refunds | 7 | 17.5% | "Refund promised two weeks ago, nothing." (TB-4212) |
| Invoice errors | 7 | 17.5% | "Your update changed amounts on 12 sent invoices." (TB-4238) |
| Login and access | 5 | 12.5% | "Nobody on our team can log in since this morning." (TB-4230) |
| Feature requests | 5 | 12.5% | "Updating 200 clients one by one." (TB-4243) |
| Exports | 4 | 10% | "Full-year export fails after a minute." (TB-4226) |
| Mobile app | 4 | 10% | "App closes when I snap a receipt." (TB-4244) |

**Summary**

Sync was the biggest theme with 8 of 40 tickets (20%), and it holds 4 of the 10 urgent ones, including Riverstone Hardware writing back after their ticket was closed as fixed. Northgate Plumbing Supply's third refund request has waited 7.9 days against a 24-hour SLA, and they say they will cancel if it isn't fixed today. Three Urgent tickets came in within the last 8 hours, and two are already past their 4-hour SLA. Ten tickets need a reply today, seven of them already past SLA.

*40 rows read, 0 skipped, no columns missing.*

And the app Claude built from the prompt in the video, urgent tickets first:

![Urgent and overdue tickets, sorted, with how long each has waited](./screen-urgent.webp)

## What we changed

Version 1.2.6: the report is the same. Every number the AI writes must now match what it sits beside: a summary saying 9 tickets are urgent when the app counts 10 is sent back. Reply drafts are checked for one per open urgent ticket, and every missing one is listed. A theme's quote can be a short message in full.

## Install the skill

A skill is a saved set of instructions Claude uses whenever the task comes up, so you don't paste the prompt every week.

**In Claude (web or desktop app):**

1. Go to **Customize > Plugins**, choose **Add > Add marketplace** and enter `h1902y/awesome-personal-apps`.
2. Choose **Add** on Weekly ticket summary. Turn on **Sync automatically** for the marketplace so new versions arrive by themselves.
3. Start a new chat, attach your export and say "weekly ticket summary".

Skills need **Code execution** turned on in **Settings > Capabilities**. On a Team or Enterprise plan, an Owner may need to allow adding marketplaces first.

**In Claude Code:**

```text
/plugin marketplace add h1902y/awesome-personal-apps
/plugin install weekly-ticket-summary@personal-apps
```

Then confirm **Install**. To get new versions automatically: run `/plugin`, open **Marketplaces > personal-apps** and choose **Enable auto-update**.

**What it runs and keeps:** one Python script, which does the counting and checks. In Claude Code it keeps its data on your computer, in `~/.h1902y/weekly-ticket-summary/` (or the plugin's `$CLAUDE_PLUGIN_DATA` folder); in the Claude app, in that chat's code sandbox. The script sends nothing; Claude still reads your export in the chat, as with any file you share.

The skill, prompt and sample data are also on GitHub: [h1902y/weekly-ticket-summary](https://github.com/h1902y/weekly-ticket-summary).

## Make it an app

Want a page you can drop next week's file into? In the same chat, ask Claude: "Turn this into an app where I can upload next week's export and get the same three sections." Claude builds it as an artifact you can open again next week.

Before you upload a real export, check your company's rules on AI tools and customer data.

Want to build your own, for your own task? Live workshop: [h1902y.com/workshop](https://h1902y.com/workshop).
