What to put in an IT support ticket (and why it saves everyone time)

Most support back-and-forth is not caused by hard problems. It is caused by tickets that leave out the details needed to start. A ticket that carries the right information can often be solved in a single reply.

The six things to include

1. A clear summary line. "Cannot print from Accounting printer since 9 AM" beats "Printer problem".
2. What you expected and what happened. Describe both, in plain words.
3. The exact error message. Copy the text or attach a screenshot. Paraphrasing loses the one detail that matters.
4. When it started and how often. Always, sometimes, or only after something changed (an update, a new device, a password reset)?
5. Who and what is affected. One person, one team, or everyone? One application or the whole computer?
6. What you already tried. Restarting, reconnecting, trying another device. It stops the same suggestions from being repeated.

Before and after

Before: "Internet not working, please fix."

After: "Laptop on the 3rd floor cannot open any website since 10:15. Wi-Fi shows connected, but pages time out. Other colleagues on the same floor are fine. Restarting the laptop and reconnecting to Wi-Fi did not help. Screenshot of the error attached."

The second version already tells the technician it is probably local to that laptop, not the network, which changes where they look first.

If you are the one answering tickets

• Reply with the next step and what you need from the user, not just "working on it".
• Write down the cause and the fix when you close the ticket. It becomes the knowledge base for the next person.
• If the same issue appears twice, treat it as a prompt to fix the root cause or automate the fix.

A tiny template

Summary:
What I expected / what happened:
Exact error message (or screenshot):
Started when / how often:
Who and what is affected:
What I already tried:

Pin it to your ticketing form or share it with your team. A minute spent on a good ticket usually saves an hour later.