Ticket Intake & Triage

A new ticket arrives at 09:04. It says "Printer not working again!!" and nothing else. The technician who sees it first does one of three things. First option: open it and start fixing the printer, which takes forty minutes and solves one ticket. Second: reply "Which printer?" and move on, which takes twenty seconds and starts a conversation that will last until Thursday. Third: read it, set a priority and a category, and put it in the right queue. Then send one reply that asks the four questions at once. Only the third one is triage. The first is heroism and the second is ping-pong. Most desks run on a mixture of the two until somebody writes the third one down.

This series is for the administrator who owns the front door of the desk, whether that is a rota of five people or one person with a second monitor. It covers what triage actually is and why it is not diagnosis. It covers the first-touch discipline that every new ticket gets in its first few minutes. It covers the five facts a ticket needs and how to ask for the missing ones once. Then come triage rhythms that suit a team too small to have a dispatcher. It covers what each channel leaves out and how to normalise it at the door. And it includes a one-page checklist you can laminate and stick beside the keyboard. None of it is clever. All of it is the difference between a queue and a pile.

Articles in This Series

• What Triage Actually Is (and Is Not)
  Sorting, not solving: the three questions every new ticket gets, the first-touch rule, and the line between triage and diagnosis. Covers why a desk that fixes during triage falls behind, and a triage card to copy.
• First-Touch Discipline for Every New Ticket
  What one person does to every new ticket on the first pass: read it properly, acknowledge it, set priority and category, route or claim it. Covers the first reply that buys time honestly, and a first-touch checklist.
• Gathering the Right Information Up Front
  The five facts a ticket needs (who, what, where, since when, how bad), and asking for the missing ones once instead of five times. Covers what the form can collect for you, and a missing-information reply to copy.
• Triage Rhythms for a Small Team
  Continuous triage versus sweeps at set times, the triage hat that rotates, dispatcher versus everyone-triages, what happens the day the triager is away, and a weekly triage rota.
• Triage by Channel: E-mail, Form, Chat, Walk-up and API
  What e-mail, web form, chat, walk-up and API tickets each leave out, normalising at the door, screening junk and auto-replies, merging duplicates at intake, and a per-channel intake table.
• A Triage Checklist You Can Laminate
  The whole discipline on one page, five tickets triaged step by step, the four common triage mistakes, and the laminated checklist itself.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.