Ticketing System

Definition

A ticketing system is the software that records every unit of work the service desk does – requests, incidents, alerts, project tasks – as a ticket with a requester, a client, a priority, a status, time entries, and a history of everything done. For most MSPs it is the ticket module of the PSA, not a standalone product; the PSA's contracts, billing, and reporting hang off the tickets.

Why it matters to an MSP

The ticketing system is the only source of truth about what your business does. Utilization, first-call resolution, tickets per endpoint per month, which client consumes three times the hours its MRR justifies, whether a technician is drowning – all of it comes from tickets, and only if the tickets are complete. The rule that runs a healthy desk is "if it is not in a ticket, it did not happen." A desk that captures 80% of its work reports on a business that does not exist, and every decision made on that report is wrong by an unknown amount.

What it must capture for the reporting to work: client and contact; a type and category you can trend on; priority set by a rule rather than a mood; a status that means something (new, in progress, waiting on client, waiting on vendor, resolved); time entries with notes a colleague could pick up from; and a link to the configuration item involved. RMM alerts should create tickets automatically, and support email should never be answered outside one.

The system also enforces your process. SLA timers, escalation rules, and client-facing status updates all run from ticket fields. Setting those up is the subject of ticket management process; the tool matters far less than the discipline around it.

Related terms: PSA, RMM, Escalation, First Call Resolution