When a colleague asks you to raise a ticket, they are asking you to write the request down where the team can see it, with an owner and a state attached. The customer’s email is the input; everything that tracks it after that is the ticket.
A support ticket is one customer request followed from arrival until someone closes it. Four things travel with it: the conversation, the state, the owner and the history. A shared address, agreed states and a rule about who claims what run the same idea for a team of three.
What a ticket holds
A ticket is four parts, and the mailbox supplies only the first.
| Part | What it is | The question it answers |
|---|---|---|
| Conversation | Every reply between the customer and your team, in order | What has been said so far? |
| State | Where the request sits in the workflow | Is the ball with us or with them? |
| Owner | The person responsible for the next move | Who is doing this? |
| History | Assignments, tags, notes and links to the work | Why is it like this? |
Email gives you the conversation and nothing else. It becomes a ticket when the other three parts are attached. History is what a forwarded-to-everyone setup loses first, because each member’s sent replies stay in their own mailbox. Ask what the team told a customer in March and the answer sits in somebody’s sent folder.
The states a ticket moves through
States exist so two people do not answer the same request at once, and so nothing waits a week with nobody noticing.
| State | What it means | What moves it on |
|---|---|---|
| New | Nobody has picked it up | Someone claims it |
| In progress | Someone owns the next move | A reply goes out |
| Waiting on us | The customer has replied, and the next move is ours | A teammate answers |
| Waiting on the customer | We asked a question and have no answer | The customer replies |
| Resolved | An answer has gone out | Time, or a reply that reopens it |
| Closed | No further action is expected | A new request |
Waiting on us and waiting on the customer are the pair that earns the system, because they say where a delay lives. An out-of-office reply does not move a ticket between states, and the out-of-office examples page covers what to write.
What a ticket is not
An email in a shared inbox is not a ticket until something tracks its state. The message holds the request; the
state, the owner and the history come from whatever tracks them. Five people on support@ look like a
queue and behave like five inboxes, which is the gap a collaborative inbox closes.
A ticket is also not a Linear issue, which describes the work that fixes the problem rather than the request from the person waiting on it.
| Aspect | Support ticket | Linear issue |
|---|---|---|
| Describes | One customer’s request | The work needed to fix it |
| Read by | The team answering, and the customer | The team doing the work |
| Counts | One per report, so ten customers means ten tickets | Usually one, however many reported it |
| Closes when | The customer has an answer | The change ships |
An automatic reply cannot become a ticket either, because there is no conversation to have. Why do-not-reply addresses exist covers when that is the right call.
The words that come with tickets
These eight terms turn up in the first week.
| Term | What it means |
|---|---|
| Queue | The tickets not yet closed, in the order the team will work them |
| Triage | The first pass over new tickets, sorting, owning and labelling each one |
| Assignment | Naming the person responsible for the next move |
| Priority | A ranking of what to do first, separate from arrival order |
| First response | The first reply a human sends to the customer |
| Resolution | The reply or the change that answers the request |
| Escalation | Moving a ticket to someone with more context or authority |
| SLA | A target for first response or resolution, often written into a contract |
Priority and SLA are the two to leave until something asks for them. A team of five can run on oldest-first plus one agreed exception.
When a team is too small for ticket software
Headcount is the wrong test. What matters is whether requests get lost and whether two people answer the same one.
| What you use | What it gives you | Where it stops |
|---|---|---|
| A shared login | Everyone sees every message | No attribution, and the password is the access control |
| A Google Group | One address for every member, and a Collaborative Inbox type with assignment and resolution in the web view | Mail lands in members’ own mailboxes, so the record is spread out |
| A shared mailbox | One mailbox several people open, with send-as permission | No owner or state unless something adds them |
| A spreadsheet or a pinned Linear issue | An explicit owner, state and notes | Someone updates it by hand, and it drifts from the email |
Move when two people answer the same customer in a week, or when nobody can say what is still open without asking around. If you are choosing between the free options, shared mailbox vs distribution list is the shorter decision.
A shared inbox that keeps the state
Chirp is a shared inbox for teams that answer support themselves, and it keeps the parts of a ticket a small team misses. A thread carries a status, an assignee and tags, in one list beside every other inbox the team answers.
Press i to link, create or search a Linear issue from a thread. Snooze the thread until that issue is done, and when
every linked issue is Done or Canceled it returns with a reply drafted that names the issue. You read it and send it,
and no rule in Chirp can send mail to a customer. The Issues view (g i) sorts linked issues by how many customers
are waiting.
FAQ
What does “raise a support ticket” mean? Write the request into whatever your team tracks, with an owner and a state. On a support desk that means opening a case, and on a small team it can mean claiming the thread in a shared inbox.
What is the difference between a support ticket and an email? An email is one message. A ticket is that message plus a state, an owner and a history. Gmail keeps the conversation, and it will not tell you which teammate is answering.
What is a support ticket system? Software that stores tickets and moves them through states. It earns its place when several people answer one address, or when you report on first response and resolution times.
How do I respond to a support ticket? Answer the customer, then set the state so nobody else picks it up. If the answer closes the request, finish with the sign-off the team uses: email sign-offs.
Next step
If you are setting up the shared address, what a collaborative inbox is is the next read: the four ways to build one, and how each breaks. Decide the states and the owner rule before you add automation.
