# Ticketing System: What It Is and How to Choose One

> A ticketing system tracks each customer request from first message to resolution. How support tickets work, key features and what to look for.

Leonard Loo · CEO & Co-Founder, Volty

Updated Nov 8, 2026

7 min read

A ticketing system is software that turns every customer request into a tracked record with an owner, a status and a deadline, so nothing gets lost between people. A customer writes in by email, WhatsApp, Instagram or web chat, the system opens a ticket, someone is assigned, and the ticket stays open until the request is resolved.

That is the whole idea. The detail that decides whether a ticketing system helps or gets in the way is how much structure it adds, and whether your customers still feel they are chatting with a person instead of filing a form.

## What a support ticket is

A support ticket is the record of one customer request, from the first message to the last. It usually carries these fields:

| Field | What it holds | Why it matters |
| --- | --- | --- |
| Customer | Name, phone number, email, past tickets | The agent sees the history before replying |
| Channel | Email, WhatsApp, Instagram, Messenger, web chat | Decides the reply format and the rules, such as WhatsApp's 24-hour window |
| Owner | The person or team responsible | One named person means no request is answered twice or not at all |
| Status | Open, waiting, snoozed, resolved | Shows what needs action today |
| Priority and labels | Urgent, billing, delivery, returns | Lets you sort the queue and route by topic |
| Due time | The deadline for the first reply | Turns "reply fast" into something you can measure |
| Message history | Every message and internal note | A new owner can pick up without asking the customer to repeat anything |

## How a ticket moves from open to resolved

- A message arrives and the system opens a ticket, or adds the message to the customer's open one.
- A rule assigns it. Rules usually match on topic, language, channel, customer segment or office hours, and share out the rest in turn.
- The owner replies, adds internal notes, asks a teammate or pulls in information from an order or booking system.
- The ticket pauses while the customer answers or while an outside party responds. A snooze brings it back at a set time.
- A slow or sensitive ticket moves to a senior teammate or a manager.
- The owner closes it. If the customer writes again, the ticket reopens or a new one starts, depending on your settings.

## Ticketing for email compared with ticketing for chat

Ticketing systems began with email. An email has a subject line and a clear start and end, so one email thread becomes one ticket. Chat is different. A customer on WhatsApp sends five short messages over two days, about two different things, and never writes a subject.

Chat-first teams usually pick one of two models:

- One ongoing conversation per customer, with a status that flips between open and resolved. Support teams like it because the history is in one place and the customer never gets a ticket number to quote.
- A new ticket for each issue, which keeps reporting clean but asks the agent to split a long chat by topic.

Neither model is wrong. The first reads better to customers and the second reads better in reports. What matters is that the system tells you who owns the chat right now and when a reply is due.

## Features worth having

### Assignment and routing

Rules that send a ticket to the right person, plus a way to share the remainder fairly. A limit on open tickets per person stops one agent from being buried while another is idle. If your team is larger than a handful of people, read about how assignment rules work in Volty.

### A queue with visible waiting

When every agent is busy, a queue keeps tickets in order and hands the next one to whoever frees up first. Customers should see their place in the line, and managers should be alerted when a ticket waits too long.

### Service level targets

A service level agreement, or SLA, is a promise about timing, most often a first reply within a set number of minutes or hours. The system should count it in your business hours and keep a single list of tickets that are due and overdue.

### Internal notes and mentions

Agents need a place to talk about a ticket that the customer cannot see, and a way to bring a colleague in with a mention.

### Canned responses

Saved replies for questions you answer ten times a day. They save typing, and they keep wording consistent between agents.

### Filters and bulk actions

Search by customer, label, owner or status, save the filters your team uses every day, and act on many tickets at once, such as resolving all tickets labeled "delivered".

### Reporting

The numbers worth watching are first reply time, resolution time, open tickets per agent and the count of overdue tickets. They show whether the team is keeping up before customers complain.

### Channel coverage

Tickets are only useful if every channel feeds them. If email lands in a ticketing tool and WhatsApp stays on a phone, you have two systems and a gap between them.

## Statuses and what each one tells you

| Status | Meaning | Next action |
| --- | --- | --- |
| Open | The customer is waiting on you | Reply before the due time |
| Waiting on customer | You asked a question and need the answer | Nothing, unless a reminder is due |
| Snoozed | Parked until a set time, such as stock arriving on Friday | The ticket returns to the open list by itself |
| Resolved | The request is finished | Nothing; a new message reopens or starts a fresh ticket |

Keep the list short. Five statuses that nobody can tell apart help less than three that everyone uses the same way.

## Mistakes that make a ticketing system useless

- Tickets with no owner. A queue everyone can see and nobody owns is the old shared mailbox with extra steps.
- Priority levels with no meaning. If everything is urgent, nothing is.
- Closing tickets to hit a number. Resolution time falls and repeat contacts rise.
- Running chat outside the system. A message answered on a personal phone leaves no trace and no deadline.
- Never reading the reports. A first reply time that creeps up by a few minutes each month is easy to miss until customers notice.

## What a small team needs compared with a large one

| Team size | Start with | Add later |
| --- | --- | --- |
| 1 to 3 people | One shared inbox, an owner on every chat, canned responses | Reply deadlines, a daily list of what is waiting |
| 4 to 15 people | Routing rules, open-ticket limits, reply deadlines, saved filters | Separate inboxes per team, manager alerts, dashboards |
| 16 or more | Queues, escalation paths, per-person reply speed, roles and permissions | Custom reports, integrations with CRM and order systems |

## How AI changes ticketing

An AI agent changes who handles the first touch. Instead of every message becoming a ticket for a person, the agent answers the repeat questions from your own knowledge base and opens work for a human only when a person is needed: a refund, an upset customer, a large order. The ticket then arrives with the conversation already summarized and the customer's details collected.

Two settings decide how safe this is. The first is whether the agent replies on its own or drafts replies for a person to approve, ideally chosen per inbox. The second is which actions need approval before they happen. A refund should wait for a person in most businesses, even when the agent can prepare it.

## How to choose a ticketing system

- List your channels. Count where customers actually write today, email included.
- Decide who owns a chat. Write down your routing rules in plain sentences before you open any software.
- Set one reply target per inbox, such as 15 minutes during opening hours for sales and 4 hours for billing.
- Check what happens after hours. Either an AI agent answers or the customer is told when a person will reply.
- Look at pricing meters. Some tools charge per agent seat and some charge per contact or per resolved conversation. Estimate your own volume against each one.
- Test the handoff. Ask a question the AI cannot answer and watch what the human receives.

## How ticketing works in Volty

Volty is built conversation-first. Every WhatsApp, Instagram, Messenger, email and web chat message lands in one shared team inbox, and each conversation has an owner and a status of open, snoozed or resolved. You can keep separate inboxes for teams such as Sales and Support, each with its own channels, people and rules.

Routing rules send a chat to a person or share it out in turn, with a limit on open chats per person. When everyone is full, the customer gets a visible place in the queue and the next chat goes to whoever frees up first, with an alert to managers when a chat waits too long. Each inbox has a first reply target counted in your business hours, and a "Waiting on us" list shows what is due and overdue.

Volty's AI agent answers from your website, documents and knowledge base, and hands the chat to the right teammate when a person is needed, in the same conversation. At Happy Fish, a swim school, replies went from about 2 hours to instant, and staff can now handle up to 300 inquiries a day instead of 100.

Happy Fish. Read the case study

To see the queue, deadlines and routing together, take a look at the Volty team inbox. Every plan starts with a 7-day free trial; check the pricing page for current prices in your market, which can change.

## Frequently asked questions

What is a support ticket?

A support ticket is a record of one customer request. It holds who asked, what they asked, which channel it came from, who owns it, its current status and every message exchanged until it is resolved.

What is the difference between a ticketing system and a shared inbox?

A shared inbox shows every message to the whole team. A ticketing system adds structure on top: each request gets an owner, a status, a priority and a deadline. Many modern helpdesks combine the two, so a conversation in the shared inbox acts as the ticket.

What should a ticket contain?

At minimum the customer, the channel, a subject or first message, an owner, a status, a priority and the full message history. Useful extras are labels for the topic, a due time for the first reply and links to the customer's orders or deals.

Do I need a ticketing system for WhatsApp customer service?

If more than one person answers customers, yes. WhatsApp has no owners, statuses or deadlines of its own, so without one a message can sit unanswered while two people reply to another. A helpdesk that treats each WhatsApp conversation as a ticket gives you those controls.

Which metrics should I track in a ticketing system?

Start with first reply time, resolution time, open tickets per person and the number of tickets waiting past their deadline. Add customer satisfaction once the basics are steady.

## Recommended for you

WhatsApp Customer Service: How to Set It Up for a Team · WhatsApp Team Inbox: How to Share One Number · AI customer service and support: how to roll it out safely · ChatGPT for customer support: what works and what to use instead · Conversational AI for customer service: how to design it well · Customer service automation: what to automate first and how · Best AI Sales Agents in 2026: 8 Compared by Job · 7 Best WhatsApp Business API Providers in Singapore (2026) · Ecommerce Chatbot: What It Does and How to Set One Up

## Start your Sandbox Trial

Email us questions · Start your Sandbox Trial

Sign up for our 7-day trial. No credit card needed.

Future-proof your business with AI. Hear from our CEO

The Leonard and Volty Show · October 8, 2026

Meta now charges for WhatsApp replies

The Leonard and Volty Show · October 1, 2026

Too busy to hire?

The Leonard and Volty Show · September 21, 2026

From $500 chatbot jobs to agentic AI

The Leonard and Volty Show · September 10, 2026

Your AI is a new employee

The Leonard and Volty Show · September 4, 2026

Trust in the AI world

The Leonard and Volty Show · August 29, 2026

Does the AI model matter?

The Leonard and Volty Show · August 19, 2026

What are AI agents?

Meta now charges for WhatsApp replies. Here's what it means for your business, October 8, 2026

## Links

- [how assignment rules work in Volty](https://voltade.com/product/team-assignment)
- [Happy Fish](https://voltade.com/case-studies/happy-fish)
- [take a look at the Volty team inbox](https://voltade.com/product/inbox)
- [the pricing page](https://voltade.com/pricing)
- [WhatsApp Customer Service: How to Set It Up for a Team](https://voltade.com/blog/whatsapp-customer-service)
- [WhatsApp Team Inbox: How to Share One Number](https://voltade.com/blog/whatsapp-team-inbox)
- [AI customer service and support: how to roll it out safely](https://voltade.com/blog/ai-customer-service)
- [ChatGPT for customer support: what works and what to use instead](https://voltade.com/blog/chatgpt-for-customer-support)
- [Conversational AI for customer service: how to design it well](https://voltade.com/blog/conversational-ai-for-customer-service)
- [Customer service automation: what to automate first and how](https://voltade.com/blog/customer-service-automation)
- [Best AI Sales Agents in 2026: 8 Compared by Job](https://voltade.com/blog/best-ai-sales-agents)
- [7 Best WhatsApp Business API Providers in Singapore (2026)](https://voltade.com/blog/choosing-a-reliable-whatsapp-business-solution-partner)
- [Ecommerce Chatbot: What It Does and How to Set One Up](https://voltade.com/blog/ecommerce-chatbot)
