Sorting the inbox by urgency, topic and owner before anyone replies — because arrival order is the worst possible order.
Ticket triage. Ticket triage is sorting incoming support conversations before anyone replies — deciding each conversation’s urgency, its topic, and who should own it, so the most important work is handled first. The term comes from emergency medicine, where patients are treated by need rather than by order of arrival.
Triage answers three questions per conversation: how urgent is this, what is it about, and whose is it. The answers become a priority tag, an intent or topic tag, and an assignment — and the queue re-sorts on all three. Teams run it three ways: a rota’d human sweeping new arrivals, rule-based routing on keywords and senders, or AI classification that reads each message and tags urgency and intent on arrival, the approach behind triage and routing in inrelay.
The under-appreciated design choice is that triage is a separate activity from answering. When the same person decides what to work on and works on it, the deciding quietly disappears — everyone answers whatever is on top or whatever looks easy. Separating the sort from the solve, even by minutes, is what makes the priorities real.
An untriaged inbox is ordered by arrival time, and arrival time is information-free: the churn-risk cancellation notice queues behind three unsubscribe requests because it came in fourth. Every metric downstream inherits the failure — first response time for urgent conversations, SLA attainment on the top tier, and the escalations that happen because the right person saw the thread two days late. Triage is cheap precisely because it is leverage: a few seconds of sorting redirects hours of work to where it matters.
Keep the scheme small enough to be applied consistently. Three or four urgency levels with written definitions — what makes something “urgent” must not depend on who is triaging — and a topic list short enough that two people tag the same message the same way. Route on ownership rules the team has agreed, so assignment is a lookup, not a negotiation.
Then measure the sort itself: time-to-triage — how long a new conversation waits before it has tags and an owner — separately from time-to-response. A team can have fast answers and slow triage, and the slow triage is invisible in every response metric until an urgent conversation spends a day untagged in the pile.
Give your customers faster answers and your team their evenings back.
Desktop and mobile. Free for solo.