A ticket is a message with responsibilities attached
An email has a sender, a recipient and a body. A ticket has all of that plus an owner, a state, a priority, a category, a deadline and a history — and every one of those exists so that somebody other than the original recipient can act on it competently.
What the number does
The reference number seems trivial and is not. It gives the customer something to quote, gives your team something to search, and quietly signals that this conversation belongs to the company rather than to one person’s inbox.
Businesses that introduce ticket numbers report the same odd side effect: customers become more patient. Knowing that a request has been recorded is most of what people want when they chase.
The anatomy
Identity: number, subject, description, creation time.
Classification: department, category, priority, labels, custom fields.
Responsibility: assigned agent, assigned team, current status.
Conversation: customer replies, staff replies, internal notes, attachments.
History: every status change, reassignment and escalation, timestamped and attributed.
Where tickets go wrong
Too many required fields at creation, so customers abandon the form. Statuses that do not describe who is waiting for whom, so reporting lies. And categories invented by whoever set the system up rather than derived from what customers actually write about.