AI Ticket Triage: Sort Support Email by What Must Happen
Most ticket triage sorts by topic: shipping, warranty, billing. That tells you who might care about a ticket, not what has to happen next. In the support system from our case study, which created 59,757 tickets between June and mid-November 2026, triage sorts by the action each ticket needs. That one change decides who touches the ticket, whether a reply can go out on its own, and what reaches the warehouse.
The first split: pure reply or solution
Every ticket the AI handles lands in one of two groups:
- Pure reply. The customer needs an answer and nothing else: a status, a policy, a troubleshooting step. The reply is the whole job.
- Reply with a solution. Something has to happen in the world: money moves, a part ships, a pickup is booked, an order is cancelled.
Pure replies are archived when they are sent. Solutions go on to a person and, after approval, into the execution ledger. Keeping the split strict matters more than any clever category list: a refund hidden inside a "pure reply" is the most expensive mistake triage can make.
Why topic categories are not enough
Take one email: "My battery charger stopped working and I need the bike for work on Monday." By topic it is a warranty ticket. By action it can be three different things: a troubleshooting reply if the fault is a loose plug, a replacement charger shipped from the warehouse, or a logistics check if a replacement is already on its way. The topic label is the same in all three cases; the owner, the approval step and the cost are not. Sorting by action puts the ticket in front of the person who has to do something about it.
The second split: what kind of action
Solutions are sorted into the jobs the operations team actually does:
- partial refund or replacement part;
- return pickup;
- logistics check with the carrier;
- cancellation before delivery;
- other, which in practice means order or address changes.
Each category maps to one owner and one execution list, and each item carries the person who raised it, so everyone can filter to their own. An AI-raised item is labelled as the AI's.
Approval before execution
When an agent approves a solution, it goes straight to the execution list and a short card goes to the team's group chat. When the AI handled a ticket on its own, the reply can go out, but the solution waits in an AI review queue sorted by the same categories. A reviewer approves or corrects it, and only then does it reach execution. Whatever is recorded uses the version a person confirmed, never the AI's first proposal.
Do not let triage block the work
Two rules kept triage from becoming a bottleneck:
- Closing a ticket is an end state, not a gate. Recording, review and execution happen when a decision is made, whether or not the ticket is closed.
- Every decision is recorded. A ticket with two decisions gets two records. An early version allowed one record per ticket and silently dropped a second reshipment, with no ledger line, no task and no card.
Sort by meaning, not by keywords
Keyword rules break on real email. Customers write "refund" when they want a replacement and "broken" when a part is missing. The triage step reads the distilled facts of the ticket, what the customer wants now and what has been done, and assigns the action category from those. Category labels and their meanings are fixed in one place, and the classifier's output format is a strict contract the rest of the system depends on.
What to measure
- How many AI-raised solutions reviewers change, by category. A high rate means the AI is missing a fact for that category.
- How many solutions reach execution without a matching ledger line. This should be zero.
- Time from approval to execution, by category.
For how replies themselves get drafted and approved, see AI email reply automation. The free plan maps your ticket types to action categories in two working days.