What is a ticket?

A ticket is a single customer request recorded as a trackable piece of work. It carries a unique reference, a status, an owner and a deadline, so a request cannot quietly disappear the way an email in a shared mailbox can. Tickets can be raised by email, through a web form, or by an agent on the customer's behalf.

What is inside a ticket?

• A reference number - the unique ID both sides quote when discussing the request.
• The requester - who asked, and which company or department they belong to.
• Subject and description - what they need, in their own words.
• Category and priority - what kind of request it is and how urgent, so an outage is not queued behind a how-to question.
• Status - where it has reached in its lifecycle.
• An owner - the agent or group accountable for it.
• Timestamps and targets - when it arrived, when it was first answered, and the service level agreement it is measured against.
• The full history - every reply, attachment and internal note, kept on the ticket rather than scattered across mailboxes.

What are the ticket statuses?

• Open - created by a customer or an agent. First response time is measured from here.
• In Progress - someone is actively working on it.
• Pending - waiting on an external party, such as a vendor or a developer.
• Resolved - the agent believes the issue is fixed.
• Closed - the customer has accepted the resolution. Resolution time runs from creation to closure.
• Reopened - closed previously, then raised again because the problem returned.

What does a ticket look like in practice?

A customer emails to say they cannot log in. That becomes ticket #4821, categorised as Access, priority High, owned by the first agent who picks it up, with a four-hour response target running from the moment the email arrived. Every reply, the internal note about the expired certificate and the eventual fix all stay attached to #4821 - so when the same problem appears next month, the history is already there.

Is a ticket the same as an incident or a service request?

Not quite - the ticket is the record, and the others describe what the record is about. An incident is something broken that needs restoring, such as an outage. A service request is routine work that was expected, such as a password reset or a new account. A problem is the underlying cause sitting behind repeated incidents. All three are tracked as tickets; separating them matters because they deserve different priorities and different targets.

What else is a ticket called?

The same record goes by several names depending on the industry. Trouble ticket is the older term, still common in telecoms and IT operations. Case is the usual word in CRM and customer service tools. Issue is what development and project tools call it. You may also see support request, service ticket or simply request. They all describe one logged item of work with an owner and a status.

Why use tickets instead of a shared mailbox?

A shared inbox works until it does not. The usual signs are requests answered twice or not at all, no clear owner for anything, and no way to answer a simple question such as how long customers typically wait. Tickets fix that by giving every request an owner, a status and a measurable clock. They also build a searchable history, so the second person to hit the same problem is not starting from nothing.

Who can see a ticket?

The person who raised it can follow its progress and reply, and agents see the tickets in their queues. Internal notes are visible only to the support team, so colleagues can discuss a request without that discussion reaching the customer. Where it is useful - for a manager overseeing a team, for instance - end users can be given visibility of every ticket raised by their company rather than only their own.