Support
What to Do Before Asking for Tech Support
By Matthew Roupp · Updated · 7 min read
A simple guide to collecting useful details before asking for help, so troubleshooting is faster, clearer, and less stressful.

Write down what is actually happening
The phrase 'it does not work' is understandable, but it does not give much to troubleshoot. A better description includes what you expected, what happened instead, when it started, and whether it happens every time or only sometimes.
For example: 'My laptop connects to Wi-Fi, but websites do not load after waking from sleep. Restarting fixes it for a few hours.' That gives a support person a much better starting point.
Take screenshots and keep error messages
Error messages are clues. Do not close them immediately if you can avoid it. Take a screenshot or write down the exact wording. The exact code or message can separate one problem from a completely different one.
If the issue is visual, a photo or screen recording can help too. This is especially useful for flickering screens, printer errors, pop-ups, account warnings, or intermittent problems.
Mention recent changes
Recent changes are often connected to new problems. Did an update install? Did the internet provider replace equipment? Did you move the router? Install a new printer? Add antivirus software? Drop the laptop? Change a password? Add a mesh system?
Try safe basics first
Safe first steps include restarting the device, checking cables, confirming power, testing another website, trying another device, checking for updates, and verifying that the account password works in a browser. These steps do not replace real troubleshooting, but they can quickly remove simple causes.
Avoid risky fixes like deleting random system files, installing unknown cleaner tools, changing router settings you do not understand, or giving remote access to someone who contacted you unexpectedly.
Useful support details to collect
- Device type, brand, and model if known.
- Operating system: Windows, macOS, ChromeOS, iOS, Android, etc.
- Exact error message or screenshot.
- When the issue started.
- What changed recently.
- Whether the issue affects one device or many.
- What has already been tried.