A ticket is one customer problem, kept as one record. An email is just a message. A ticket is the message plus everything the team decides about it.
One source describes a support ticket as "a running report on a particular problem, its status, and other relevant data"1. That wording is a good test. If your current setup can't show a problem's status, it isn't really tracking tickets yet.
What changes when an email becomes a ticket
In a plain inbox, a message sits there until someone reads it. Nobody knows whether it's been answered, who has it, or whether the customer wrote back twice.
Turn the same message into a ticket and the software wraps it in a record. The record holds the customer's words, every reply, and a set of fields. The ticket stays one thing from the first message to the last, even if ten replies pile up.
Help desk software, in general terms, is a program that lets operators "keep track of user requests"2. Tracking is the whole point.
What a ticket usually holds
Another source says a ticket generally includes "vital information for the account involved and the issue encountered"1. In practice, that breaks down into a few parts you can look for when you compare products.
- The conversation. The customer's first message, your replies, and any customer replies after that.
- The requester. Name and email, and sometimes company and phone.
- A status. Where the ticket stands right now. The statuses page covers the usual set.
- An owner. One product's documentation describes a field to "Assign tickets to another group or agent"3. See assigning and routing.
- A priority. How soon the problem needs attention. The words used differ by product.
- Labels. The same documentation says to "Add tags or labels to easily organize and find your tickets"3. The tags page goes further.
- Private notes. Comments only staff can see.
A picture of the change
The diagram shows the shape. The message arrives the same way it always did. What's new is the record built around it.
What to check before you pay for anything
Ask whether each field above exists, and whether you can rename or add your own. Small teams often find that a few fields are enough. Ten fields that nobody fills in just slow everyone down.
Check how a ticket gets created. Most buyers want email to work first, so ask how a message sent to your support address becomes a ticket, and what happens to a reply that arrives later.
Then look at the customer's side. Does the person writing in see a ticket number, or does it feel like email as usual? Neither is wrong, but you should know which one you're buying.
Last, ask what you can get back out. Can you export tickets with their fields? A system you can't leave is a bigger commitment than the price suggests.
Sources used
- Issue tracking system (support ticket), Wikipedia
- Help desk software, Wikipedia
- Understand the Ticket Details View, Freshworks (Freshdesk Support)