Email ticketing is the practice of turning incoming email into tracked items of work. Each conversation acquires an owner, a state and a history that outlives any individual's mailbox. The person who wrote in notices none of this: they send an email and receive a reply.
What a ticket adds to a message
- An owner, so responsibility is explicit rather than assumed
- A state, so "handled" is a fact about the record rather than a memory
- A durable history, so the thread survives staff changes and mailbox cleanups
- Attachment to something: a customer, an account, a project, or in a services firm a client and a retainer
How threading actually works
Keeping a reply attached to the right ticket is the part that quietly determines whether the system is usable. Mail clients rewrite headers, strip references and reformat subjects, so a robust system uses a ladder of signals rather than one:
- A token in the reply address, for example
[email protected]. This is the strongest signal because it is the envelope recipient: it survives every mail client, since delivery depends on it. - The
In-Reply-ToandReferencesheaders, matched against message IDs the system generated when it sent. - Sender plus normalised subject within a recency window, after stripping localised
Re:andFwd:prefixes.
Where none of these match, a new ticket is the right answer. Attaching a message to the wrong conversation is worse than opening a redundant one, because it can show one customer another customer's history.
Forwarded mail
A common case in professional services: a colleague forwards a client's email into the system. Naively, the ticket now belongs to the colleague and a reply goes back to them rather than to the client. Better systems parse the forwarded block, or the attached original message where the forward was sent as an attachment, and attribute the conversation to the original sender.
Detection is heuristic and occasionally fails, particularly with clients that print a name and no address, so a one-click way to correct the contact matters as much as the parsing.
Ticketing versus a shared inbox
The two terms describe the same machinery from different angles. Email ticketing stresses that the message became a tracked item; a shared inbox stresses that a team works the queue together. The meaningful distinction is what the sender experiences: reference numbers, portals and automated acknowledgements, or an ordinary reply from a person.
What to measure
Help desks measure first response time, resolution time and volume, all of which suit high-volume consumer support. A firm billing by the hour has a different question. The useful measure is how much time client requests consume, which accounts consume it, and whether it is reaching an invoice.
That measure only exists if the time is recorded where the request is handled. Otherwise email ticketing produces a well-ordered queue and exactly the same write-downs as before.