A support queue audited to the root: 1,645 tickets, six systemic fixes

Problem

The operations support queue had run since inception with no audit. Tickets came in from three different places, Asana, Slack, and HubSpot, and got closed one at a time as they arrived. Nobody had gone back to ask what kept showing up, so the same problems kept costing the same hours over and over.

What I built

• Pulled every ticket from February 9 to September 8, 2026: 1,645 total, 1,600 closed, 45 still open.
• Categorized each one by type, priority, and root cause instead of just closed or open.
• Grouped the categories into patterns and traced each recurring class back to what actually caused it, not just what the ticket described.
• Wrote up six systemic fixes from those patterns and put them on the engineering build board instead of answering the next instance of the same ticket by hand.

Result

Six systemic fixes are now queued on the build board, each one tied to a specific root cause instead of a vague complaint. I want to be honest about what this is: the audit produced the fixes. It did not, by itself, move ticket volume. That's the measurement to take once the fixes ship.

What it shows

Auditing to root cause instead of just clearing the queue. Closing 1,600 tickets one by one teaches a team nothing about why they keep coming. Categorizing all 1,645 does.