Why the details matter
Support technicians spend a surprising share of their time working out what the problem actually is. A request that says 'Outlook is broken' could mean Outlook won't open, won't send, won't receive, is slow, keeps asking for a password, or is showing someone else's calendar. Each has a different cause. The technician either guesses, or writes back asking questions, which adds hours or days to the fix.
The same applies whether you use an outside provider, an in-house IT person or the office manager who knows computers. Every minute spent clarifying is a minute not spent fixing. Good reports also help spot patterns: if three people report the same error within an hour, that points to a wider problem worth investigating straight away.
Who and where
Start with who is affected: just you, a few people, or everyone. If it's more than one person, name them or say which team. Then say which device: your laptop, a shared PC, your phone, the reception printer. Most computers have a name or an asset label; if you can include it, the technician can connect to the right machine without asking. Mention where you are if it matters. A problem that only happens when working from home points to a different cause than one that only happens in the office. If you're at a client site or on a hotel network, say so.
What you were doing and what happened
Describe what you were trying to do in a sentence, then what happened instead. 'I was trying to send an invoice from Xero by email; it said sent but the customer didn't receive it' is far more useful than 'email not working'. If the problem happens every time, say so. If it happens sometimes, say how often and whether anything seems to trigger it.
Copy the exact error message, or better, take a screenshot. On Windows, the Snipping Tool or Windows key, Shift and S captures part of the screen; on a Mac, Command, Shift and 4 does the same. Error codes that look meaningless to you often point a technician straight to the cause. Avoid paraphrasing; 'something about a certificate' is much less helpful than the actual words.
When it started and what changed
Say when the problem began, as precisely as you can. 'Since this morning' or 'since the update last Tuesday' helps narrow causes quickly. Mention anything that changed around that time: a new password, a Windows update, a new printer, a move to a different desk, a new app installed, a power cut over the weekend. Also mention what you've already tried. If you've restarted the computer, signed out and back in, or tried another browser, say so. That saves the technician from suggesting the same steps and tells them the problem is past the obvious fixes.
How urgent it really is
Be honest about urgency, in business terms. 'I can't send quotes and we have a tender closing at 3pm' tells support what matters and when. 'Nobody in the office can access the internet' is clearly urgent. 'My second monitor flickers sometimes' can wait until tomorrow. Marking everything as urgent makes it harder for support to tell the real emergencies apart, and over time it means genuine emergencies wait in the same queue as minor annoyances.
If there is a workaround, mention it. 'I can use the other printer for now' tells support it can be scheduled rather than dropped everything for. And if something looks like a security problem, such as an unexpected password reset email, a pop-up demanding payment or files that suddenly won't open, report it immediately and say so plainly. Don't try to fix it yourself, and don't turn the computer off unless support tells you to.
Use the proper channel
Log requests through the route your business has agreed, whether that's a support email address, a portal or a ticket system, rather than messaging a technician's personal phone or catching them in the corridor. Logged requests don't get lost, can be passed to whoever is available, and build a history that helps spot recurring problems.
If your business doesn't have a clear support route yet, set one up. A single support email address that goes to whoever handles IT, with a short template staff can copy, makes a real difference. Office IT clients log requests by email or portal for this reason, and the same approach works for any team.
In short
- Say who is affected and which device.
- Describe what you tried to do and what happened instead.
- Include the exact error message or a screenshot.
- Note when it started, what changed and what you have tried.
- State the real business urgency, and report security issues immediately.