Before You Call IT: A Support Ticket Checklist for Faster Help
Give your IT support team the details they need without sharing passwords or spending an hour investigating the problem yourself.
A useful request describes the problem clearly
“It does not work” is understandable when you are busy, but it gives the responder little to start with. A short, specific description can help them identify the affected system and decide what needs attention first.
You do not need to diagnose the cause. Your job is to explain what you were trying to do, what happened and how the problem affects the business.
Include six details
- What: the application, device or service involved.
- When: the first time you noticed it and whether it is happening now.
- Who: one person, several people or the whole location.
- Expected result: the task that normally succeeds.
- Actual result: the error text or behaviour.
- Impact: the work that is stopped and any available workaround.
Capture the error safely
Copy the exact error message or take a screenshot if your policy permits it. Remove customer information, private conversations and other unnecessary sensitive content before sending. Include a reference or transaction identifier where safe.
Never put passwords, MFA codes, recovery codes or payment-card details in a support ticket. If access needs to be granted, use the approved process. A technician should not need your everyday password pasted into an email.
Use a short example
Subject: Invoicing app cannot export PDFs on reception laptop.
Description: Started around 9:20 am today. The app opens, but selecting Export shows “destination unavailable”. Two attempts had the same result. Another staff member can export from their computer. I can enter invoices, but cannot send them to customers. Screenshot attached with customer details removed.
That request describes a symptom and a business impact without claiming to know the cause.
Tell support what changed
Mention a move to another desk, a new device, an update prompt or a change of network. Say what you already tried and whether it made a difference. Avoid repeated restarts or changing settings while the responder is investigating.
Escalate through the agreed channel
For a widespread outage or suspected security incident, use your provider's urgent contact procedure. Sending more duplicate tickets is usually less useful than identifying the existing request and explaining a change in impact.
Ask your MSP to give staff a one-page guide with support hours, urgent contacts and this checklist. That routine is part of making IT support predictable.
Explore NOX managed IT to agree support channels and responsibilities for your team.