SaaS & Customer Support// topic
Ticket and shared-inbox triage
In short
The first thing any support AI should do and the lowest-risk place to start: reading every inbound ticket, email and chat, deciding what it is about, how urgent it is and who owns it — before a customer ever sees a word the model wrote.
9 pages
diagnostics
- A mail loop is manufacturing tickets between your system and theirsRunaway ticket volume from a single counterparty is rarely spam. It is two automated systems answering each other, and the fix is a header rule your responder should already have been applying.diagnostic11 min
- Customer replies are opening new tickets instead of threadingOpen the raw source of one orphaned reply. Whether the References chain contains your outbound Message-ID decides whether this is a matching bug, a stripped-header problem, or an identity problem.diagnostic9 min
- One intent label is absorbing most of your ticketsA collapsed label distribution has four possible causes and only one of them is a model problem. Two histograms, thirty days apart in five minutes of SQL, tell you which.diagnostic9 min
- The same ticket keeps getting reassigned between two teamsCount assignment changes per ticket for one week. A handful of tickets with many hops is a rules conflict; many tickets with exactly two hops is a boundary problem in the taxonomy.diagnostic9 min
- Your SLA is breaching on tickets that arrived outside working hoursOvernight breach reports are almost always a schedule problem rather than a staffing problem. One chart — breach rate by hour of arrival, in the schedule's own timezone — tells you which, and the rest of the afternoon is configuration.diagnostic11 min
definitions
- First-reply SLA timer: start, pause and breach are three different eventsA first-reply SLA is three settings, not one, and most breach reports that look like a staffing problem are one of the three configured differently from how the team believes.definition6 min
- Intent taxonomy: the label set a support router can act onAn intent is not a description of a ticket. It is the instruction a router acts on, which means a label no queue, macro or automation consumes is not a label at all.definition6 min
- Requester, end user and organisation: the records a ticket hangs offA ticket points at several identity records, not one. Entitlement belongs to the company record, tone belongs to the person, and mixing them is how the wrong customer gets premium routing.definition6 min
- Suspended ticket queue: what lands there, and why real customers do tooSuspension is a triage decision your helpdesk makes before your rules, your macros and your model see the message — and the only triage decision whose mistakes leave no trace.definition6 min
Other topics in SaaS & Customer Support
See allDrafted replies and agent assistThe stage where a model writes and a human still sends — how a reply is drafted in your team's voice, cited back to something real, and how the agent's edits become the best evaluation data you will ever get.5 pagesBuild, buy, or extend what you already pay forYour helpdesk vendor already sells an AI add-on, usually priced per resolution — an honest read on when that is the right answer, when a custom layer earns its keep, and how the two coexist.2 pages
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation