What Is a Customer Support Ticketing System? A Plain-English Guide

When a business is small, support lives in a shared email inbox. Then the team grows, messages arrive from more places, and questions start to fall through the cracks: two people answer the same email, or nobody does. A customer support ticketing system is the tool that fixes this. Here's what it is, how it works and what to look for.

What is a ticketing system?

A ticketing system turns every customer request into a ticket: a single record that holds the customer's message, every reply, internal notes, who is responsible and what state it's in. Instead of searching through inboxes, your team works from one shared queue where every request is visible, assigned and tracked until it's solved.

Requests can come from many places, and a good system brings them all into the same queue:

• Email to your support address
• Web forms and your help center's "contact us" page
• Live chat, including offline messages left when nobody was online
• Messaging apps like WhatsApp, Instagram and Messenger
• Phone calls logged by an agent

How a ticket moves from new to solved

Most systems use a handful of statuses:

1. New: the request has arrived and nobody has picked it up.
2. Open: an agent owns it and is working on it.
3. Pending: you're waiting on the customer, for example for an order number or a photo.
4. Solved: the problem is fixed. If the customer replies, the ticket reopens.
5. Closed: after a few quiet days, solved tickets close automatically.

The statuses matter because they let you see, at a glance, what needs attention now and what's waiting on someone else.

Why not just use a shared inbox?

A shared email inbox works for a while, but it can't tell you:

• Who owns each conversation. Without assignment, everyone assumes someone else has it.
• How long customers have been waiting. There's no clock, so slow replies go unnoticed.
• What's been said before. Context is scattered across forwarded threads and private inboxes.
• How you're doing. No response times, no satisfaction ratings, no trends.

A ticketing system answers all four.

Features that matter

You don't need every feature on the market. These are the ones that make a difference to a small or growing team:

• Automatic assignment and routing. New tickets go to the right person or group without anyone sorting them by hand.
• Priorities and SLAs. Set first-reply and resolution targets per priority, and get warned before one is missed. Our guide to support SLAs for small teams explains how to choose targets.
• Triggers and automations. Tag, route or reply automatically when a ticket arrives, and close tickets that have gone quiet.
• Macros and saved replies. One click to reply, change the status and add tags. Start with these 12 canned responses.
• Internal notes. Discuss a ticket with colleagues without the customer seeing it.
• A help center and customer portal. Customers find answers themselves, and track their own requests when they do need you. See how to build a self-service help center.
• Reports and satisfaction surveys. Response times, resolution times and a simple "How did we do?" after each ticket. More in our guide to CSAT surveys.

Tickets and live chat: better together

Chat and tickets aren't competitors. Chat is for quick questions answered while the customer waits; tickets are for anything that takes longer. The best setups let an agent turn a chat into a ticket with one click, and turn offline chat messages into tickets automatically, so nothing started in chat gets lost.

When is a small team ready for a ticketing system?

You probably need one if any of these sound familiar:

• More than one person answers customers.
• You've lost or forgotten a customer request in the last month.
• You get messages from more than one channel.
• You can't say how long customers usually wait for a reply.

You don't need a big budget to start. Many tools offer a free package for a single agent, so you can set up your queue before you need to pay.

Getting started

Set up a few things first: one support email forwarded into the system, two or three priorities, a first-reply target and your ten most common saved replies. Everything else can wait until you know what you need. Our help desk includes tickets, SLAs, automations, macros, a help center and satisfaction surveys in every package, including the free one. Start free.