Support ticket: what belongs in one, and why most are missing it

A support ticket is the record of one request from arrival to resolution. Whether it takes one exchange or five is decided almost entirely at intake: a ticket that says it is not working starts a round trip that could have been avoided by asking three questions on the form the customer already had open.

That is the whole design problem. Every field you add improves the tickets you receive and reduces how many people finish the form. The balance is not a matter of taste — ask for what genuinely changes your first reply, and nothing else.

What a good ticket contains

• What the person was trying to do, in their words. The goal, not just the error — the fastest resolutions come from understanding the intent.
• What actually happened, including the exact message if there was one. A screenshot beats a paraphrase every time.
• When it started, and whether it worked before. This single question separates a change on your side from a change on theirs.
• How to see it happen: the page, the account, the steps. Not always possible, and hugely valuable when it is.
• Impact — blocked entirely, or inconvenient. This is what should drive priority, rather than how the request was phrased.
• How to reach them and when. Time zone included, because half of resolution time is usually waiting.

Designing the intake

1. Keep the form to five fields or fewer. Beyond that, completion falls faster than quality rises.
2. Ask for the goal in an open field, first. It is the highest-value answer and people give it willingly.
3. Capture context automatically where you can — account, plan, browser, version — rather than asking the customer to look it up.
4. Offer categories only if they change routing. Categories that exist for reporting get chosen at random and poison the reporting anyway.
5. Let people attach a file or an image without creating an account.
6. Confirm receipt immediately, with a reference and a realistic expectation of when someone will look.

Priority should be set from impact, not from tone. The angriest message is frequently not the most blocked person, and a queue sorted by how forcefully somebody wrote teaches customers that escalation works. Ask for impact explicitly and sort on that; it is fairer and it produces better decisions when everything is urgent at once. Where volume outgrows a shared mailbox, the same fields become the case record in a help desk.

Statuses that survive contact with a real queue

Three are enough for most teams: new, waiting on us, waiting on them. That last one matters more than it looks — it separates our backlog from the tickets stalled on a customer reply, and without it every queue looks worse than it is and nobody knows which number to act on. Add a fourth, resolved, and stop there. Elaborate status schemes with pending, on hold, escalated and monitoring create the illusion of process and quietly become places where tickets go to sit.

Closing well

Say what you did, not only that it is done. A resolution note the customer can read tells them whether it will happen again and often prevents the next ticket. Where the cause was on your side, say so plainly. Where the same ticket has now arrived three times, the resolution is a documentation or product change rather than a third reply — the pattern-finding half of this is covered in help desk.

Formal complaints deserve their own route. A customer complaint form that asks what happened and what outcome the customer wants makes the complaint actionable from the first contact.

One number tells you whether the queue is really shrinking. First call resolution counts the contacts finished in one interaction, measured by whether the customer comes back within a week rather than by whether the agent pressed close.

Where it lives

Ettex Forms is the intake: a short form anyone can reach without an account, with attachments, landing as structured records in Ettex Records where they can be filtered by impact and status and where the history stays attached to the customer in Ettex CRM.

The boundary, stated plainly: this is not a ticketing system. There is no queue automation, no service level timers, no customer portal where people track their own requests, and no live chat. For a team handling a handful of requests a week the form-and-records approach genuinely works; past that, a dedicated help desk product is the right purchase and we would rather say so. Where response times are promised to a customer, the fields also have to support the service level agreement being measured.