Core concepts

What is support ticket?

Also known as: ticket, case

Published September 10, 2026 · Reviewed by the Fidiora team

Definition

A support ticket is the tracked record of a single customer request, holding the conversation, the customer identity, a status, an owner, and metadata such as priority and tags. It exists so that a request cannot be lost, and so that work on it can be measured and transferred.

Why it matters

The ticket is the atomic unit of support operations, which means the way you define it shapes every metric downstream. Teams that create a ticket per message and teams that create one per issue produce completely different volume, resolution, and cost numbers from identical work.

What to know

  • A ticket should represent an issue, not a message, or your volume metrics inflate with every follow-up.
  • Status vocabulary should be short. Open, pending, resolved, and closed covers nearly every real workflow.
  • Merging duplicates matters. The same customer emailing twice should not appear as two problems.
  • The ticket record is also the audit trail, which matters for disputes and for regulated industries.
  • Ticket count measures activity, not value, and should never be used as an individual performance target.

An example

Example: a customer sends three emails about the same broken export over two days. As one ticket, it is one issue that took two days. As three tickets, it is three issues resolved quickly, and the reporting says the team is doing well.

Common mistakes

  • Creating a ticket per message rather than per issue
  • Maintaining a dozen statuses nobody can define
  • Never merging duplicate tickets from the same customer
  • Using tickets closed as an individual performance metric
Where Fidiora fits

Fidiora is designed so that routine questions are answered without becoming tickets at all. What reaches your help desk is the work that genuinely needs a record and a human, which makes ticket data a truer picture of your hard problems.

See Pricing
FAQ

Questions

What information should a support ticket contain?
The full conversation, verified customer identity and account context, a current status, a named owner, priority, and topic tags. Anything beyond that should earn its place, because every extra field is a field agents will leave blank.
What is the difference between a ticket and a conversation?
A conversation is the exchange of messages. A ticket is the tracked work item wrapped around it, with state and ownership. One ticket can contain a long conversation, and it should.
Is ticket count a good performance metric?
No. It measures activity and rewards closing rather than resolving. Cost per resolution, first contact resolution, and reopen rate all describe the outcome instead.

Related terms

Help desk A help desk is the system and the team that receive, track, and resolve customer requests. As software, it provides a sh... Support queue A support queue is the ordered set of requests waiting to be worked, usually grouped by team, topic, or priority. The qu... Ticket tagging Ticket tagging is the practice of labelling support requests with categories so they can be counted, reported, and autom... Resolution A resolution in customer support is a request that ends with the customer having a correct, complete answer and no need ...
Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

Start Free Book a 15-min Demo

No credit card · Live in under an hour