Backlog & Aging Dashboard
Build an internal dashboard that breaks your open support backlog down by age, queue, priority, and owner, surfaces the tickets that have been stuck the longest, and lets a manager approve clean-up batches before anything is recorded.
A team-only dashboard that loads your open tickets, renders aging buckets and breakdowns by queue/priority/owner, spotlights the longest-stuck tickets, and lets a manager approve clean-up actions (close stale, reassign abandoned) that are logged to an audit trail and exported as an aging report.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- An export or feed of your open tickets (CSV or Google Sheet) with created-at, last-activity, queue, priority, and owner
The problem this kills
Your support backlog never lives in one honest view. The big queues get watched; the long tail rots. Tickets that were "waiting on the customer" three weeks ago are quietly aging into months. A reorg or a vacation leaves a stack of tickets owned by someone who's gone. And when you finally try to clean up, you're eyeballing a giant export in a spreadsheet, sorting by date, and hoping you don't accidentally close something that's actually active.
The trap most dashboards fall into: they age tickets by creation date, so a ticket someone replied to yesterday still screams "180 days old" and everything looks like a fire. You lose trust in the numbers, so you stop looking.
You need a single screen that ages tickets by last meaningful activity, breaks the backlog down the way your team actually works, points at the genuinely stuck items, and lets a manager clean up safely - with a record of what was done and why.
What you'll build
A small, team-only web app that:
- Loads your open tickets from a CSV export, a Google Sheet, or a live feed.
- Computes each ticket's age from last meaningful activity, not just when it was created.
- Renders aging buckets (e.g. 0-2 days, 3-7, 8-14, 15-30, 30-60, 60+) and breakdowns by queue, priority, and owner.
- Surfaces a "Stuck the longest" list so the long tail can't hide.
- Lets the tool propose a clean-up batch (close stale, reassign abandoned tickets) - which a manager must approve before anything is recorded.
- Logs every approved action to an audit trail and exports a clean aging report in the exact columns your system expects.
What's inside the Implementation Plan
- A copy-paste runbook you hand to an AI coding agent (Claude Code) - it builds the whole thing with you, step by step.
- It opens by interviewing you about your business - your queues, your priority labels, what counts as "meaningful activity" in your tools, your typical and peak ticket volumes, and your real clean-up rules. The tool is tailored to how you work, not dropped on you as a generic template.
- A data model and aging logic shaped by your answers, not a one-size-fits-all guess.
- The full governance build (login, per-org isolation, approval gate, audit trail, duplicate guards) wired in from the start.
- A "No API yet?" fallback so you can build and use the whole thing this weekend, even with zero integration to your helpdesk.
The governance it includes (this is the point)
- Login so only your team can open the dashboard.
- Row-level security so each organization only ever sees its own tickets.
- A complete audit trail - who proposed a clean-up, who approved it, what changed, and when.
- A hard human-in-the-loop approval gate - the tool drafts the clean-up batch, a manager reviews and approves, and only then is anything recorded. No silent mass-closing.
- Duplicate guards keyed on ticket ID so the same ticket can't be loaded or actioned twice.
Who it's for
Support managers and operations leads who need to clear a backlog and keep it from building back up - especially anyone staring at a spreadsheet of open tickets wondering which ones are truly stale and which are just badly dated. No developer required.
You've got this - paste the first prompt and let the agent interview you.