Ticketing System for Customer Support: What It Must Do
A ticketing system turns each customer matter into one record, a ticket, that holds every message about it, shows who is responsible, and shows what state it is in. Without one, a support team works from a shared mailbox, where two people answer the same email and a third matter is answered by nobody.
We built a ticket workbench for a support operation that AI and people run together. In the 30 days to 19 November 2026, it opened 8,608 tickets. This page covers what any ticketing system has to do, and what has to change when AI is part of the team.
What every ticketing system must do
- One matter, one ticket. A customer's follow-up email joins the existing ticket. It does not open a second one.
- Every channel in one place. Email, chat and web forms arrive in the same queue.
- An owner. Each ticket belongs to a named person.
- A status. Waiting for us, waiting for the customer, closed.
- The history. Everything said and done, in order, on one screen.
- The customer's order beside the conversation. An agent should not open a second system to see what was bought.
Where tickets come from
Of the 8,608 tickets in our 30 days: 6,113 were opened by a customer email, 1,694 by the chat AI when a chat request needed a person, and 738 by notices the system sent to customers about their orders. The remaining 63 were opened by hand or recovered from the spam folder.
The second number is specific to working with AI. The chat AI answers questions itself and creates a ticket only when a person has to act, with the facts already written in.
Merging and splitting correctly
Merging by subject line or sender alone goes wrong. Two rules we rely on:
- An email is added to a ticket when it belongs to the same thread.
- When a ticket was closed and the customer writes again, that is a new round on the same matter, with its own handling and its own record.
Automated mail is filtered before it becomes a ticket. How mail is sorted is in AI ticket triage.
What changes when AI drafts the replies
A classic ticket screen is built for typing. When AI has already gathered the facts and written a draft, the agent's job is to check and decide, and the screen should be built for that:
- Facts first. The order, the tracking status and a short summary of the thread, above the draft.
- The proposed solution, named. Reship a part, refund, reimburse a local repair. The agent can change it.
- Two buttons. Approve and send, or approve, send and close. One question goes with them: does this need someone to carry out an action?
- The AI draft kept. The draft is stored separately from what was sent, so the difference can be measured later.
In our 30 days, agents sent 23,120 replies that began as an AI draft, 19,339 of them after editing.
Tickets are not tasks
A reply that says "we will send the part" creates work for someone who never sees the ticket. A ticketing system that stops at the reply loses that work. In ours, approving a reply that needs action creates a task in an execution list at that moment. The list is divided by type of work, such as reshipments, order changes and carrier checks, and each type has a named owner.
Each approval also writes one line to a shared ledger. Every decision is its own line. An early version kept one record per ticket, and a second reshipment on the same ticket was dropped without a trace.
Closing is an end state, not a gate
No process waits for a ticket to close. A task is created when the decision is approved. A record is filed when the reply is sent. If follow-up steps wait for closing, anything on a ticket that stays open is never done.
A review queue for what AI sent alone
When AI sends simple replies without a person, those replies need their own place to be checked. Ours is a queue sorted by six types of reply, where a reviewer checks them. For a reply that involves an action, the task is created only after the reviewer passes it. In the 30 days, the AI sent 3,331 replies this way.
Notes and system records apart
The notes field on a ticket holds what people wrote by hand. What the system records, such as "task created" or "survey sent", goes to the ticket's activity log. Mixed together, the one note a colleague left gets buried under machine lines.
Satisfaction surveys belong to the ticket
The survey goes out when the ticket closes. When to send it is covered in what is CSAT.
Choosing a ticketing system
- Does it merge by thread?
- Can it show order data beside the conversation?
- Does it have an API that an AI agent can read tickets from and write drafts to?
- Can a reply create a task for another team?
- Can you export every ticket with its history?
If you already use a helpdesk, an AI agent can be added to it: see adding an AI agent to a helpdesk. If you work from a shared mailbox, see AI for a shared support inbox. Tell us what you use today and the free plan shows where AI fits, within two working days.