How to Report an IT Problem: What Support Needs to Fix It Faster

How you report an IT problem decides how fast it is fixed. “The computer is broken” starts a conversation of ten questions. “The accounting program shows error 5 when I print an invoice, since this morning’s update, only on my computer” starts the repair. This guide shows what to include when you report an IT problem, by e-mail or phone, so that a technician can diagnose it quickly, often in the first reply. It also covers how to rank urgency, what to expect from the person helping you, and a template you can keep for your whole team.
Under our IT maintenance service, you report a problem by e-mail or phone. We solve it on site or remotely and advise how to avoid it next time. Computer repair works in the same way: you describe the problem, we diagnose it at your office or home, or through remote support when a visit is not needed, and we explain what is wrong and what the repair involves before we start. What you say in the first message shapes everything that follows.
Why the first message matters
Support work is mostly diagnosis. The repair is often quick once the cause is known. A precise first report removes rounds of questions, lets the technician decide at once whether the problem can be solved remotely and reveals whether it affects one person or the whole office. A vague report costs time on both sides, and during that time the person who needs the computer cannot work.
| Vague report | Useful report |
|---|---|
| “Internet does not work.” | “Wi-Fi shows connected but no pages load on my laptop. A colleague’s phone works on the same Wi-Fi. Started after lunch.” |
| “Printer is broken.” | “The third-floor printer prints a blank page from Word and PDF on two computers. The toner is new. Printing from the same files worked yesterday.” |
| “My e-mail is not working.” | “Outlook on my desktop asks for a password again and again since Monday. Webmail in the browser works. Phone mail works.” |
| “Computer is slow.” | “My computer takes about five minutes to start and freezes when I open more than three programs. It was fast until about two weeks ago.” |
The useful reports share a pattern: what happens, where, since when, who is affected and what still works. That last item, what still works, is one of the most useful clues you can give.
The seven things to include
1. What exactly happens
Describe what you see, not what you think the cause is. “A window says the license has expired” is better than “the program is broken”. Copy the exact words of any error message, or take a photo of the screen. Error codes and wording often identify the problem on sight.
2. What you were doing
The action that triggers the problem: opening a file, printing, signing in, sending a message. If you can repeat it, say so, and note the steps. A fault that can be reproduced can be diagnosed.
3. When it started
Today, since an update, since the weekend, since a move? The start time is a strong clue because most problems follow a change: an update, a new program, a power cut, new equipment or a changed password.
4. What changed
Any change before the problem began, even one that seems unrelated. People often leave out things they believe irrelevant, such as a new printer, a plugged-in device or a software update that the computer installed overnight.
5. Who and what is affected
One user, one computer, one department or everyone? One program or all of them? One location or all locations? If a colleague can do the same task on another computer, say so. This tells the technician whether to look at the computer, the account, the network or a server.
6. What you have already tried
Restarting, reconnecting cables, running updates, uninstalling something. This avoids repeating steps and shows what has been ruled out. Mention results as well: “restarting fixed it for an hour, then it returned” is valuable.
7. How urgent it is
What is blocked and by when it matters. “I cannot issue invoices and the deadline is today at 16:00” belongs at the top of the queue. “The screen flickers a little” can wait for a scheduled visit.
Ranking urgency honestly
When everything is urgent, nothing is. A simple three-level scale helps both sides.
| Level | Meaning | Examples |
|---|---|---|
| Critical | Work has stopped for several people or a critical service is down | Mail server down, no internet for the office, accounting server unavailable |
| High | One person cannot work, or an important function is impaired | A laptop will not start, a key program crashes, a printer is down before a deadline |
| Normal | Work continues with a workaround or the problem is minor | A slow computer, a request for a new program, a cosmetic fault |
State the level and the reason. If your business has set hours or service targets, our article on the IT helpdesk for small teams explains how priorities and response targets can be organised.
Evidence that helps
- A screenshot or phone photo of the error, taken so that the whole message is visible (Microsoft explains the built-in tools in its Windows support pages).
- The exact text of the message, copied if possible.
- The device name or number, usually printed on a label on the case, and the user name of the affected account.
- A short list of steps to reproduce the problem.
- The time of the incident, which helps match it to logs.
Never include passwords in a message. If a technician needs access, they will explain how to provide it safely, for example through a controlled remote session or a password reset that you perform yourself. The NCSC’s tips for staying secure online explain why passwords should never be shared in messages.
E-mail or phone?
Both work, and each suits different situations.
- E-mail suits problems that are not critical, because it leaves a written record and lets you attach screenshots. Send it from a computer that is still working, not from the affected machine if it cannot send mail.
- Phone suits urgent problems and cases where you cannot describe the fault easily. Have the computer in front of you, so that you can follow instructions while you talk.
- Both is sometimes best: phone for speed, followed by an e-mail with the details, so that the record is complete.
What to expect from good support
A well-run support process behaves in a recognisable way. The technician asks only the questions that matter, tells you whether the problem can be solved remotely or needs a visit, explains what is wrong and what the repair involves before starting, repairs and tests, and then tells you how to avoid the problem. If it needs a visit, you should be told roughly when. Many software problems are solved through remote support, and our guide to remote support for business computers explains what can be fixed without a visit and how a safe session works.
Reporting problems inside a team
In a company, the way problems are reported is a process, not just a habit. A few measures keep it smooth.
- One address and one number. Everyone should know where to send reports. Scattered requests to many people get lost.
- A short template pinned where staff can see it, such as the one below.
- A named contact in the company who collects reports, avoids duplicates and tells staff what to expect.
- Collective problems reported once. If a whole office is affected, one person writes the report, with the names of those affected.
- A record of recurring issues. Repeated problems are signals that the underlying cause needs work, as covered in our article on Windows update problems and in regular IT care.
A template you can copy
Subject: [Urgency] Short description - Name - Device
1. What happens (exact message / photo attached):
2. What I was doing:
3. Since when:
4. What changed before it started:
5. Who and what is affected:
6. What I already tried:
7. Urgency and reason:
Contact: name, phone, best timeKeep the subject line specific: “High – cannot print invoices – Anna – accounting PC” is far better than “Help”. The first line tells the technician where to start.
Three full examples
A problem with a clear cause
“High – cannot sign in to the accounting program – Peter. Since 08:30 the program says ‘user account locked’. I changed my Windows password yesterday. Colleagues can sign in. I tried restarting, no change. I need it before the 14:00 payment run.” The technician reads this and goes straight to the account settings: the likely cause is a stored old password in a service or a lockout caused by repeated attempts. The fix may take two minutes.
A problem affecting the whole office
“Critical – no internet in the office – Maria for all. Everyone lost internet at 10:10. Wi-Fi and cable both show no connection. The router lights are on but the internet light is red. We restarted the router once. Phones on mobile data work.” This points to the connection or the router, not to individual computers, and the technician can begin by checking the provider’s line and the router’s status, probably through a call, not a long e-mail exchange.
An intermittent problem
“Normal – computer restarts by itself – Tom. It has restarted about five times in the last week, always when I am in a video call, never during other work. No error message. The computer is four years old and often hot to the touch.” Intermittent faults are hard, so details count: the pattern, the heat and the age suggest overheating or a failing component, and the technician can propose a hardware check on site instead of guessing remotely.
Common reporting mistakes
- Reporting a guess as a fact. “The server is down” may really mean “my program will not open”. Say what you see and let the technician find the cause.
- Several problems in one message. Separate faults need separate reports, so that each can be tracked and solved.
- Waiting too long. Small warnings, such as strange noises, repeated errors or slow starts, are cheapest to fix early.
- Trying risky fixes first. Reinstalling the system or deleting files from advice found online can make a recoverable problem worse. Contact support before drastic steps.
- Not saying who to contact. Include a phone number and the best time, especially if you will be away from your desk.
- Not following up. If the fix worked, confirm it. If the problem returned, say so in the same thread, so that the history stays together.
Before you call: quick checks that save time
- Is the device powered, and are cables firmly connected?
- Has the computer been restarted since the problem began?
- Do other devices on the same network work?
- Does the problem occur in another account or program?
- Is there a pending update or a message that has not been read?
These checks take two minutes and sometimes solve the problem. Even if they do not, the answers go into your report. For slowness, our troubleshooting checklist gives a longer list.
Frequently Asked Questions
How do I report a problem?
You report a problem by e-mail or phone. We solve it on site or remotely and advise how to avoid it next time.
Do I need a maintenance contract to ask for help?
No. Every service is also available without a contract, on call. A contract suits companies that want regular care, hardware audits and an upgrade plan.
Can problems be solved remotely?
Yes. Many software problems are solved through remote support. When a visit is needed, our specialists come to your office.
Will you explain what is wrong before starting?
Yes. We explain what is wrong and what the repair involves before we start.
What should I never send in a message?
Passwords. If access is needed, the technician explains a safe way to provide it.
Is computer repair available to home users?
Yes. It is available to companies, institutions and home users.
The Bottom Line
A good report answers seven questions: what happens, what you were doing, when it started, what changed, who is affected, what you tried and how urgent it is. Add a screenshot, never send passwords, choose phone for urgent problems and e-mail for the rest, and keep a short template for your team. The result is faster diagnosis, fewer questions and less lost time. To arrange regular care or a single repair, see our IT maintenance service.