What a ticketing system is and when you need one

A ticket is one customer request, kept as a single record with everything said about it. When a customer emails to say they were charged twice, the ticketing system files the email as, say, ticket 1042, marks it New and puts it in the queue your team works from. Whoever takes it becomes its owner, and its status changes as the work moves on, until it’s solved.

A helpdesk is a ticketing system with the rest of a support team’s kit around it, such as a help centre, live chat, saved replies and reports, and most people use the two words for the same thing. Vendors also say help desk software, support ticket system or ticketing software, and not every tool says ticket. Help Scout calls each request a conversation.

For a founder who answers support alone, a ticketing system solves a problem you don’t have yet, which is two people answering the same customer. Deacon is an AI customer support agent that answers your customers on your site in seconds, from your own docs, and sends you only the questions that need you. It isn’t a ticketing system, and it has a free plan.

What a ticket holds

Most ticketing systems give every ticket the same handful of fields. These are among the standard ones in Zendesk’s guide to ticket fields, read on 23 September 2026.

The whole thread stays in the ticket, the customer’s messages and your replies, along with private notes your team leaves for each other.

The type does real work when many customers hit the same fault. Say ten customers report the same outage. You mark one ticket as the problem and link the other nine to it as incidents. When you solve the problem ticket, Zendesk’s guide to problem and incident tickets says every linked incident is set to solved and gets the comment you solved it with, so ten customers hear back from one fix.

How a ticket moves from New to Closed

Statuses are how a queue knows what needs doing next. This is one ticket’s life in Zendesk, following the rules in its guide to the ticket lifecycle.

1. Monday, 09:12. A customer emails to say they were charged twice. Ticket 1042 is created as New, which means nobody has acted on it yet.
2. 09:40. You assign it to yourself, and it changes to Open by itself.
3. 09:45. You ask which invoices they mean and set it to Pending, which means you’re waiting on the customer.
4. 14:05. They reply with the invoice numbers, and the ticket goes back to Open.
5. 14:30. You refund the second charge, reply, and set it to Solved.
6. Friday afternoon. Zendesk’s default automation closes the ticket four days after it was solved. An admin can change that wait, and with the automations off a ticket still closes 28 days after it was solved.
7. The following Tuesday. The customer writes back with one more question. A closed ticket can’t be reopened, so Zendesk creates a follow-up ticket with a new number that points back to 1042.

Had they written back on Thursday, while 1042 was still Solved, it would have reopened. Teams watch how often that happens, because a ticket that comes back after it was solved usually means the first reply didn’t settle it.

If you solved 120 tickets in March and customers reopened 9 of them, your reopen rate was 7.5%. Zendesk’s reports count reopened tickets as those “reopened after being solved”. A reply that arrives after the ticket has closed becomes a follow-up, so it adds to your ticket volume as a new ticket rather than counting as a reopen. A low reopen rate goes with good first contact resolution.

Ticket statuses in Zendesk, Help Scout and Zoho Desk

Each ticketing system names the stages differently. These are the default statuses in three of them, from their own guides, read on 23 September 2026.

In all three, a customer’s reply moves a waiting request back to a status that needs action. Help Scout goes further and makes a closed conversation Active again, where Zendesk creates a follow-up ticket instead. Zoho Desk freezes the clock on a ticket that’s On hold, so time spent waiting on the customer doesn’t count against the reply times you’ve promised.

Ticketing system vs helpdesk, shared inbox and service desk

The words overlap, and vendors use them loosely. This is the difference that matters when you choose.

Our guide to customer support tools compares what helpdesks and shared inboxes cost, including their free plans, and when each is the wrong buy.

IT ticketing systems

Many searches for a ticketing system are about the other kind. The pages that rank for “ticketing system” come mostly from IT service management vendors such as ServiceNow, SolarWinds and SysAid, whose tools take requests from a company’s own staff, like a laptop that won’t start or a new starter who needs accounts.

IT teams that follow ITIL, a widely used framework for running IT services, split those tickets in two. An incident is “an unplanned interruption to an IT service or reduction in the quality of an IT service”. A service request is a routine ask, such as a password reset or access to an app, as Freshworks’ summary of the ITIL terms puts it. A customer ticketing system does the same filing for the people who pay you, and that’s the kind this page is about.

When a small team needs a ticketing system

A ticketing system earns its keep when support is shared. These are the signs.

• Two of you have answered the same customer, or each thought the other had.
• You promise reply times and need to see which requests are about to miss them.
• Customers reach you by email, chat and phone, and you want one queue.
• You need figures such as first response time and average resolution time without counting by hand.

If you’re the only one answering, an email inbox with a label for each kind of question does most of the same job. The bigger cost is the same questions arriving every week, and a ticketing system files each one again without answering any of them. That’s the problem to fix first, and our guide to reducing support tickets shows how to count those questions. Much of the fix is customer self-service, answers customers can reach without writing to you.

If you want a ticketing system anyway, it needn’t cost anything. osTicket and FreeScout are open source and free to run on your own server, and FreeScout sells add-on modules on top.

Where Deacon fits, if you’d rather not run tickets

Deacon isn’t a ticketing system. It has no ticket numbers, owners, due dates or routing, no shared inbox, and it doesn’t read your support email. It works earlier, on your site, and answers the questions that would otherwise become tickets.

Your customers ask in their own words and get an answer in seconds, at any hour and in their own language, from your docs. When your docs don’t cover a question, Deacon says it doesn’t know instead of guessing and asks for the visitor’s email. When they leave it or ask for a person, the owners on your team get an email. You reply from Deacon’s dashboard, and if they still have the chat open, your words appear there under your first name. Human handoff follows one conversation from the question to your reply.

It gets better as you answer, which a ticket queue never does. Every question your docs didn’t cover has an Answer this button, and what you write becomes part of what Deacon knows, so it can answer the next person who asks. Save & check shows you the reply Deacon now gives and how many other open questions your answer covers. The more you answer, the less it needs you.

It also shows you what customers need, where a queue only shows you what’s next. Every conversation is saved and searchable by what visitors asked, and a filter picks out the ones tagged Unanswered or Wants a person, with a count on each. Topics group similar questions, count the people who asked and label most groups, for example as a how-to, a bug report or a feature ask. You see what customers are stuck on and what they want you to build next.

If you already run a helpdesk, Deacon has no integration with it, so a handoff comes to Deacon’s dashboard and your email rather than into your queue. If you don’t run one, you may not need one yet. Deacon goes on your site with one script tag, and the free plan needs no card and has no end date.