A support ticket is a unique record created when a customer or employee reports a problem or asks for help. It holds the message, requester, assigned agent, priority, status and the full history of replies and internal notes until the issue is closed.
Why it matters
Tickets turn scattered messages into measurable work. Each has an ID so the conversation can be found and referenced, a status such as open, pending or solved, and timestamps that feed metrics like first response time and time to resolution. Patterns across tickets reveal recurring bugs, confusing features and gaps in documentation, which feed back to the product team.
Example
Ticket #1307
Requester: customer@example.com
Subject: Cannot reset password
Priority: Normal Status: Pending (waiting on customer)
Tags: login, password
SLA: first reply due in 8 hoursCommon mistakes
- Starting a new ticket for every reply instead of keeping a thread, which loses context.
- Closing tickets without confirming the customer is satisfied.
- Using too many or inconsistent tags and priorities.
- Not recording the root cause, so the same issue returns.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.