What is a support ticket?

A support ticket is a single, tracked record of a customer request or issue — created when someone reaches out, carried through to resolution. Each ticket has its own status, history, and owner, which is what lets a team manage many requests without losing track of any of them.

The lifecycle of a ticket

A ticket is typically created automatically when a customer emails, chats, or submits a form. It moves through statuses — open, pending (waiting on someone), resolved, closed — while accumulating the full history of the conversation. That record means any agent can pick it up with full context, and nothing slips through the cracks.

Why tickets matter

Tickets turn a chaotic stream of requests into something a team can own, prioritize, and report on. Whether your tool calls them tickets or conversations, the underlying idea is the same: one tracked unit of work per request, so it gets resolved and measured.

Selvo Shared Inbox

Run support from one inbox, not a free-for-all

Selvo's shared inbox turns email into real support: assignments, internal notes, saved replies, SLA tracking, and CSAT — without the duplicate replies and dropped threads a plain distribution list creates.

See how Selvo Shared Inbox works

Questions about Support Ticket

What's the difference between a ticket and a conversation?

They're largely the same idea with different framing. "Ticket" feels formal and transactional; "conversation" feels personal. Modern shared inboxes use conversation language while keeping ticket-like tracking underneath.

How are support tickets created?

Usually automatically — from an inbound email, a chat, a contact form, or an API call. Each inbound request becomes a ticket so it can be tracked to resolution.

Related terms

Ticketing System

A ticketing system converts customer requests into structured, trackable tickets — each with a reference number, status, priority, and routing. It's built to manage support at scale: high volumes, multiple teams, and formal processes, with reporting on everything that flows through.

Ticketing System vs Shared Inbox

A ticketing system converts every request into a formal ticket with IDs, queues, statuses, and automation — powerful but more rigid and process-heavy. A shared inbox keeps support as natural email-style conversations the whole team can manage together. Ticketing scales structure; shared inboxes keep things personal and low-overhead.

Resolution Rate

Resolution rate is the percentage of support tickets that get resolved out of all tickets received in a period. It's a fundamental throughput metric — are you actually closing what comes in? A resolution rate consistently below 100% means a growing backlog of unresolved issues.

Browse the full customer support glossary →