Ticket
A ticket is the record of a customer question inside a support tool. It groups every message in that conversation under one identifier and adds what is needed to manage it: status, owner, priority, tags and the history of what has happened.
What is ticket?
A ticket is the record of a customer question inside a support tool. It groups every message in that conversation under one identifier and adds what is needed to manage it: status, owner, priority, tags and the history of what has happened.
Also: case · incident · query
A ticket is not a message
It is the whole conversation. The confusion shows up when counting volume: if your tool opens a new ticket every time the customer replies, your monthly volume is inflated and your resolution times artificially low. Before comparing figures with anybody, check what counts as a ticket in each system.
Why it matters
What changes in a SaaS
The ticket is the unit everything in support is measured in: cost, times, volume and satisfaction. If the unit is not well defined, none of those metrics can be compared across periods, let alone across companies.
Ticket in detail
Statuses
Open, in progress, waiting on customer, resolved and closed are the usual ones. The status that carries the most information is "waiting on customer", because it separates the time your team is responsible for from the time it is not — and without that separation, resolution time measures the customer calendar.
Where they come from
Email, in-product chat, web form, WhatsApp, or a call somebody logs. The tool unifies them, but the channel shapes the expectation: chat expects a reply in minutes and email in hours, even though the ticket is the same.
The ticket as a problem
Part of the industry argues the goal should be fewer tickets rather than better-managed ones. It is a healthy counterweight: every repeated ticket is a signal that something is unclear in the product or the documentation, and treating it purely as work to dispatch loses that signal.
How Intake handles it
Questions about ticket
What is the difference between a ticket, an incident and a request?
In formal service management vocabulary, an incident is something broken and a request is something asked for with nothing failing. "Ticket" is the generic term covering both, and it is what almost everybody uses in practice.
Is it better to have fewer tickets or to close them faster?
Fewer tickets, nearly always. Closing fast lowers the cost of each one; stopping them arriving eliminates it. The exception is questions that signal buying interest, which you want to arrive.
Does a chat count as a ticket?
It depends on the tool. Some create a ticket per chat conversation and others only when it gets escalated. It is the first thing to check before comparing volumes between two systems.
Related terms
A term on its own is only half understood. These come up in the same conversation.
Help desk — Help desk
A help desk is the team and the tool that receive user questions and resolve them. It centralises in one place whatever arrives by email, chat or form, turns each question into a ticket with a status and an owner, and keeps the history of what was answered.
Escalation
Escalation is handing a conversation to somebody with more knowledge or more permissions to resolve it. It can go from one support tier to another, from an automated agent to a person, or from support to engineering — and in every case whoever receives it has not seen the case until that moment.
Ticket backlog
The backlog is the set of questions open and still unresolved at a given moment. More than its size, what gets watched is its trend: if more questions come in than get closed, the backlog grows, and it grows cumulatively even when the daily difference is small.
SLA — Service level agreement
A service level agreement is the written commitment to respond within set deadlines. It fixes maximum times — usually first response and resolution — defines the hours in which they count, and normally states what happens when they are missed.
Shared inbox
A shared inbox is a mailbox the whole team can access, where every conversation has an assigned owner, a status and a history visible to everyone. It replaces forwarding emails between colleagues and the generic address one person quietly runs.
Knowledge base
A knowledge base is the organised set of articles documenting how a product works and how to resolve what gets asked often. It serves two audiences at once: customers looking up the answer themselves, and the team using it as the source for their replies.
