In this guide
Appearance
Summary
This article explains how to write a clear, detailed IT support request so the helpdesk team can diagnose and resolve your issue faster. Providing the right information upfront can reduce back-and-forth and get you back to work sooner.
Before You Start
- Access to your organization's IT ticketing system (email, web portal, or Teams channel).
- Your computer name and basic system information (see How to Find Your Computer Name and IP Address).
Instructions
1. Describe the Problem Precisely
A good IT ticket answers three questions: What happened? When did it start? What were you doing?
- Write a specific subject line
- Instead of "Help" or "Something is broken," be specific.
- ❌
Computer not working - ✅
Outlook freezes when opening attachments since Tuesday
- ❌
- Instead of "Help" or "Something is broken," be specific.
- Describe the exact symptoms
- What do you see on screen? Include any error messages word-for-word.
- What were you doing when it happened? (e.g., "I clicked Print and received an error.")
- Use plain description rather than borrowed jargon — "the sign-in page loads and then goes blank" beats "I think it's a token issue". If a term from a previous reply would genuinely help, check what it means first in Understanding Common IT Terms — A Plain English Glossary.
- Note when it started
- Did it start after a Windows update, a restart, or a specific change?
- Is it happening every time or intermittently?
2. Include Your Device Information
IT often needs to know which device you are using to troubleshoot remotely.
- Computer name — Press Win + Pause/Break or go to Settings > System > About and note the Device name.
- Operating system — Note whether you are on Windows 10 or Windows 11 (visible on the same About page).
- Application version — If the issue is in a specific app (e.g., Outlook), note the version. In most Office apps, go to File > Account to find the version number.
See How to Find Your Computer Name and IP Address for detailed steps.
3. Capture a Screenshot or Screen Recording
Press Windows + Shift + S to capture the error on screen, or Windows + Alt + R to record a sequence of events, then attach the file to the ticket.
- Take a screenshot — Press Win + Shift + S to open the Snipping Tool, select the area of the error, and paste it into your ticket or email.
- Record the issue — Press Win + Alt + R to start a screen recording (Xbox Game Bar) if the issue is a sequence of events. Press the same shortcut to stop recording.
- Attach the file — Include the screenshot or recording as an attachment in your ticket.
See How to Take Screenshots on Windows for more screenshot methods.
4. Note What You Have Already Tried
This prevents IT from asking you to repeat steps you have already taken.
- "I restarted my computer."
- "I cleared the browser cache."
- "I checked the cable and it is connected."
- "I ran the Windows troubleshooter — it found no issues."
Tip: Even if something did not fix the problem, mentioning it helps IT narrow down the cause faster.
5. Indicate the Impact and Urgency
Help IT prioritize by explaining how this affects your work.
- Who is affected? Only you, your whole team, or a customer-facing process?
- Is there a deadline? Mention it if the issue is blocking time-sensitive work.
- Is there a workaround? Can you continue working (e.g., using the web version), or are you completely blocked?
6. Example of a Great IT Ticket
Copy the shape of the worked example: a specific subject line, the symptoms with the error text word-for-word, your device and OS, what you already tried, the business impact and any deadline, and the screenshot attached.
Subject: Outlook crashes when opening PDF attachments — since Monday
Description: Since Monday morning (May 12), Outlook freezes for about 30 seconds every time I try to open a PDF attachment. After freezing, I get the error:
Microsoft Outlook is not responding. This happens every time with any PDF attachment, not only one specific email.Device: DESKTOP-4F7K2R1 — Windows 11 — Microsoft 365 Apps (Version 2405)
What I've tried:
- Restarted my computer twice
- Opened Outlook in Safe Mode (issue still occurs)
- Other file types (Word, Excel) open fine
Impact: I cannot review contracts sent by vendors. I have a deadline on Thursday.
Screenshot attached: [error_screenshot.png]
7. Follow Up When Your Ticket Stalls
Add new information to the ticket you already have rather than opening a second one, because a quiet ticket is usually queued rather than ignored.
A helpdesk works a queue. Your ticket sits in it alongside everything else that arrived that morning, and the technician who picks it up is working through what landed before yours. Silence is what a queue sounds like from the outside — it is rarely a decision anyone made about you.
Give it a fair amount of time first
Many ticketing systems display a target response time on the ticket itself, so look for it in the ticket record before you chase. Where no target is stated, one full working day before your first follow-up, then every second working day after that, keeps you visible without spending goodwill you will want later. A problem that stops you working earns a faster rhythm than a request for a software license.
Add information, not pressure
Repeating "any update on this?" gives the technician nothing they did not already have, so it changes nothing about where your ticket sits. Three things do move a ticket, because each one changes the size of the problem:
- It now affects more people. "Two colleagues on my team have hit the same error since this morning" turns one person's problem into a team's.
- It now blocks a deadline with a date on it. "This blocks the month-end report due Thursday 14 August" is a fact someone can prioritize against. "It's urgent" is not.
- You found a reproduction. "It happens every time with PDFs over 5 MB and never with smaller files" hands the technician the next hour of their investigation.
Put any of those in a reply to the ticket you already have. Opening a second ticket for the same problem slows the work down — the history, the diagnostics and your earlier answers all live on the first one, the two records can land with different technicians, and someone has to spend time merging them before anyone gets back to fixing anything.
Copy and paste this, replacing the specifics with yours:
Adding an update here rather than opening a new ticket.
Since I raised this, two colleagues on my team have hit the same error, so it now affects three of us.
It also blocks the month-end report due Thursday 14 August.
New detail: it happens every time with PDFs over 5 MB, and never with smaller files. Restarting the computer does not change it.
Happy to test anything from my end if that helps.
Ask for the three answers that tell you where you stand
When a ticket has gone quiet past its target, ask for facts rather than an apology. An apology costs the technician a reply and tells you nothing. These three answers tell you what to do next:
- A rough timeframe. "This week" and "after the vendor comes back to us" are both answers you can plan around.
- Who owns it now. Tickets get reassigned, and a name means your next reply reaches a person rather than a queue.
- What the ticket is waiting on. This is the most useful of the three and the one people ask for least. A stalled ticket is often waiting on something outside the helpdesk — a vendor's own support case, a license purchase, a change approval, or another team's work. If that is the answer, pressing IT harder changes nothing, but knowing it tells you to set up a workaround and stop refreshing your inbox.
Copy and paste this:
Following up on this one. No rush intended — I mainly need to plan around it.
Could you let me know roughly when it is likely to be picked up, who owns it now, and whether it is waiting on anything outside your team? If it is more than a few days out, I will set up a workaround at my end in the meantime.
When to bring your manager in
Not as a threat, and not to go over anyone's head. Prioritisation is a business decision, and your manager can state a business impact in terms you cannot: what the delay costs, which customer or deadline it touches, and whether this work needs to displace something else in the queue. "This is blocking me" and "this is holding up the client onboarding we committed to for the 20th" are different inputs, and only the second one can outrank other work.
Do it in the open. Ask your manager to add a comment to the same ticket rather than emailing someone privately — it keeps everything on one thread, and it spares the technician hearing about it second-hand.
Copy and paste this into a message to your manager:
Ticket #48231 with IT has been open since 4 August. It stops me from exporting the vendor contracts, which holds up the renewal pack due on the 20th.
Would you add a short comment to the ticket confirming that business impact? A line from you carries weight that a line from me does not, and it helps IT rank it honestly against everything else in their queue.
The one thing that genuinely helps IT
If you find a workaround while you wait, write it into the ticket. It takes two minutes and it does three useful things: it tells the technician which parts of the system still work, which narrows the cause; it lowers the urgency honestly, so nobody is chasing an emergency that has stopped being one; and the next person who hits the same problem gets your workaround out of the ticket history instead of losing an afternoon to it. Helpdesk teams remember the people who do this, and that memory is worth more than any escalation.
Troubleshooting
TIP
The single most helpful thing you can include in a ticket is the exact error message. Copy and paste it if possible — do not paraphrase. IT teams use error messages to search internal databases and vendor documentation for known fixes.
| Symptom / Error | Potential Cause | Solution |
|---|---|---|
| IT asks for more information | Original ticket lacked details | Resubmit using the format in Section 6 above. |
| Ticket seems stuck or no response | Ticket is sitting in a queue, or was misrouted | Reply to the existing ticket with new information — never open a second one. Section 7 above has the wording. |
| IT replies "waiting on a third party" | The fix depends on a vendor, a license, or another team | Ask for a rough timeframe and set up a workaround in the meantime. Add the workaround to the ticket so the next person benefits. |
| Unsure which ticketing system to use | Multiple support channels available | Check with your manager or IT intranet page for the correct submission method. |
| Cannot take a screenshot | Snipping Tool not available | Try pressing Print Screen (PrtScn) to capture the full screen, then paste into Paint or an email. |