If you’ve shopped for helpdesk software, you’ve seen the word ticket everywhere — usually attached to a price (“$0.99 per ticket”, “1,000 tickets/month”). But what is a support ticket, really?
The short answer
A support ticket is a single customer conversation, tracked from the first message to resolution. It bundles together:
- Who asked (the customer’s name and email),
- What they asked (the subject and the full message thread),
- Its status (open, in progress, waiting on the customer, resolved, closed),
- Who’s handling it (an agent or team), and
- Its history (every reply, in order, in one place).
The key word is tracked. A ticket doesn’t disappear when you close the tab or archive the email. It has a clear state you can filter and search by.
Ticket vs. email
Email can handle support, but it has no concept of status. Was that customer’s question answered? Is anyone on it? You find out by scrolling and hoping. Three replies deep, the thread is a mess, and if a teammate is copied, you’re both unsure who replies next.
A ticket adds the missing structure: a status, an owner, and a single canonical thread — so nothing is answered twice and nothing falls through the cracks.
Ticket vs. live chat
Live chat is great for right now. But when the visitor leaves, the conversation usually leaves with them. A ticket persists: the customer can come back days later, reply to the same thread, and you still have the full context. Many teams use both — chat for instant questions, tickets for anything that needs follow-up.
What counts as one ticket?
This matters because most helpdesks price by ticket. The standard definition — and the one we use — is simple:
One ticket = one conversation, no matter how many messages it contains.
A ticket with 1 reply and a ticket with 50 replies both count as a single ticket. So a “1,000 tickets/month” plan means 1,000 separate conversations, not 1,000 messages. That distinction makes a big difference when you compare plans.
The takeaway
A support ticket is just a customer conversation with structure bolted on: a status, an owner, and a permanent thread. That structure is the whole point — it’s what turns “we’ll get to it” into “here’s exactly where it stands.”
Want to see it in action? Open the live demo — no signup — or start free.