Ticket triage, with a scheme one person can run

A message saying nobody can log in since this morning is a bug, it’s urgent, and only you can fix it. A message asking how to export invoices is a question that can wait until the afternoon, and your docs should be what answers it.

The word comes from the French trier, to sort, and from emergency medicine, where a nurse sees everyone who comes in and decides who is treated first. Most guides to ticket triage are written for IT service desks, managed service providers and support teams big enough to have tiers of staff and routing rules between them. When you answer support yourself, the answer to “who” is nearly always you, so triage comes down to the order you work in and the questions you can stop answering by hand.

Deacon is an AI customer support agent that does the first sort for you. It answers your customers on your site in seconds, from your own docs, and lists what’s left in the order to deal with it. It has a free plan. The Gmail and Zendesk help pages quoted below were read on 10 November 2026.

The three decisions in ticket triage

Triage means making three decisions about each message, in this order.

1. What kind of message it is. The kind tells you what you need before you can reply. A bug needs the steps to reproduce it, an account question needs the customer’s account open, and a how-to needs a link to the right page.
2. How urgent it is. Urgency comes from what the customer can’t do right now. A bug that only looks wrong can wait, and a one-line question can’t if the customer is locked out.
3. Who or what should answer it. In a team this is routing to the right person. On your own there are four answers, which are you now, you later, a page in your docs, or a list you read when you plan what to build.

Help desks record the second decision as a priority. In Zendesk it’s a field with four values, Low, Normal, High and Urgent, and an admin can’t add to them or rename them, only cut them down to Normal and High. Teams then promise a reply time for each priority in a service level agreement.

A triage scheme for one person

Four labels and one rule are enough while you answer support alone. Every message gets one label.

Urgency gets one rule. A message is urgent when the customer can’t do what they pay you for, or their money is wrong. Urgent messages go first, today, whatever their label. Everything else is answered in batches, one label at a time in the order of the table, oldest first within each. Sort at set times, such as when you start work and again after lunch, rather than each time a message lands, so support doesn’t break up the rest of your day.

Four kinds of message trip people up.

• “Can it export to PDF?” is a Question, and “Please add PDF export” is an Idea. Someone asking whether the product does something is often deciding whether to buy, and your docs should tell them.
• A complaint that the product is slow is Broken if it got slower, and an Idea if it has always been that way.
• A message with two asks gets the label of the more urgent one.
• Three reports of the same breakage within an hour are an outage. Stop sorting, fix it or post a note where customers will see it, then send all of them one reply.

When a second person starts answering, the third decision comes back. Keep the four labels and give each one an owner, such as Broken to whoever can ship the fix and Account to whoever can issue a refund.

Setting the scheme up in Gmail

If you answer support from Gmail, its labels and filters are enough to run this.

1. Make the four labels. On the left, next to Labels, click Create new label, type Broken and click Create, then do the same for Account, Question and Idea. To give one a colour, point at it, click More, then Label color (Google’s steps).
2. Let filters pre-sort the obvious ones. In the search box, click Show search options, type the words, click Create filter, choose the label, then click Create filter again (Google’s steps). Gmail’s search matches any of several words with OR and an exact phrase in double quotes, so refund OR invoice OR receipt OR charged OR cancel catches most Account messages, and error OR broken OR "not working" OR "can't log in" catches most Broken ones.
3. Check the filters’ guesses each morning. A filter only reads words, so “how do I cancel an invite?” lands in Account until you move it. Google’s filter page also says a reply to a filtered message is filtered only if it matches the same search, so a customer’s follow-up can arrive unlabelled.
4. Star each urgent message as you read it. Searching is:starred lists them, and you work that list first. Then click each label on the left in turn and work through its batch.

In a help desk, the labels become tags or a custom field and the rule becomes the priority field. Cut Zendesk’s down to Normal and High, as above, and mark the rule’s messages High.

One morning’s 20 messages, sorted

Say you run a form builder and open your inbox at 9am to find 20 new messages. Sorted with the scheme, they come out like this.

Work through them in this order.

1. The 3 sign-in reports go first. They’re one bug, and last night’s release is the obvious suspect. Roll it back or fix it, then send the 3 customers one reply.
2. The double charge is next, because the customer’s money is wrong. Refund it and tell them.
3. The Safari date picker is the rest of the Broken batch. Reproduce it and tell the customer when it’ll be fixed.
4. The Account batch is the yearly refund, which is your call under your own refund policy, and the VAT invoice.
5. The Question batch is 11 messages and 5 replies. Write the invite answer once and send it 4 times.
6. The 2 Ideas go on your list in the customers’ own words, with a thank-you to each.

In arrival order, the first sign-in report was the 6th message and the double charge was the 17th. Working down the inbox, that customer would have waited behind 16 others while their money was wrong.

You can also see from the counts where the morning went. 11 of the 20 messages were questions, and 9 of those asked one of three things. Three pages in your docs, put where customers get stuck, could answer most of tomorrow’s versions before they’re sent. Our guide to reducing support tickets shows how to find those questions in your own inbox.

Triage mistakes that waste time

Working in arrival order

Oldest first feels fair, and newest first feels responsive, but both leave the double charge wherever it happened to land. Label everything first, then work the urgent ones, then the batches. The oldest message in your backlog still matters, and the batches keep it from being forgotten, because each one runs oldest first.

Treating every bug report as urgent

The label says what kind of message it is, and the rule says how urgent it is. Merge the two and the sign-in failure that locks people out queues behind a button that sits two pixels too low. The Safari date picker is a real bug, but the customer can still pick a date, so it waits for the Broken batch.

Sorting the same question every day

The 4 people who asked how to invite a teammate today will be followed by more tomorrow. Read, label and answer each one from scratch, and you pay for that question every morning. Write the answer once, as a page in your knowledge base, and keep a saved reply that links to it, so answering the next person means inserting the saved reply.

Labels you have to think about

If you hesitate over which label a message gets, you have too many. Keep a label only when it changes who answers or what you need before you can reply. Billing and refunds both need the account open, so they share the Account label.

What changes when an AI answers first

An AI agent on your site changes triage in two ways. It answers the questions your docs cover before they reach you, and it can sort each message as it arrives, so the work is waiting in order when you sit down. With an agent answering from docs that cover invites, plans and embedding, the morning above would have had a Question batch of at most the 2 one-offs, instead of 11 messages. The Broken, Account and Idea messages still reach you, and so do the questions your docs don’t cover.

Watch out for an agent that guesses. When your docs don’t cover something and it answers anyway, the customer gets a wrong answer and nothing reaches you to sort. So pick one that says when it doesn’t know, and read its list of what it couldn’t answer as part of your morning.

Help desks also sell AI triage, which labels each ticket rather than answering it. Zendesk’s intelligent triage classifies each new ticket by topic, sentiment and language on its Suite and Support Professional plans and above, and using those labels in workflows requires the Copilot add-on, whose price is in Zendesk AI pricing.

What Deacon sorts for you

Deacon answers the chat on your site from your docs, in seconds and in whatever language the visitor writes. When your docs don’t have the answer, it tells the visitor it doesn’t know instead of guessing, and the chat offers a box for their email so you can reply. Each question gets a kind as it arrives, such as a how-to, a bug report, a question about what the product can do, account and billing, or pricing.

What’s left goes on What needs you, one list that both Analytics pages show. It opens on the first job, as in “Start here: reply to the 5 people waiting.” Below that, in this order, come People waiting for a reply, Problems in your product, Account and billing, What Deacon didn’t know, and Setup, which flags things like your plan’s answers running out. Your four labels land in it like this.

Topics take care of the question you’d otherwise sort every morning. The 4 people who asked how to invite a teammate become one topic, with a count of 4 people and the type how-to. The seven types are bug report, feature ask, how-to, pricing, account and billing, wants a person and feedback. A topic is listed once two people have asked, and one you mark done comes back by itself if more people ask.

Each question under What Deacon didn’t know is a click from Answer this. Write the reply as you would to the customer, or as rough notes, and Deacon files it in your help document, or in your Instructions if it’s about how Deacon should behave. Then it asks itself the question again and shows you what it now says, and for an answer in your help document it lists the similar open questions your answer also covers. Each answer becomes part of what Deacon knows, so your Question batch gets smaller the more you answer. If you fix bugs with a coding agent, Deacon’s MCP server lets it read the same list with get_needs_you and open the chat behind a bug report with get_conversation.

Deacon doesn’t mark anything urgent, so the rule stays yours. What needs you sorts by kind, which puts a double charge under Account and billing beside a request for a VAT invoice. Deacon has no ticketing and no assigning between teammates, and it can’t see your email inbox, so support that arrives by email still needs the labels above. If a co-founder helps with support, either of you can reply in any conversation, and pricing shows how many seats each plan has.

Chatbot analytics goes through What needs you and Topics in more detail. The free plan needs no card, so you can add Deacon to your site today and see tomorrow’s list sorted for you.