What system info to record before remote tech support

Before a remote support session, it helps to have the basics ready: what device you use, what went wrong, and what you already tried. A few clear details can save time, but sending a full dump of personal information usually does not help.

Use TooLab's System Info to check details such as your processor, graphics, screen, battery, and network. Then make a short note that you can share through the support channel you trust.

Gather the details before support connects

Open System Info on the computer you need help with. Review the processor, graphics, screen, battery, and network details shown. Do not assume a field is exact if the browser only provides an estimate.
Write down your device type and operating system version. On Windows 11, open Settings › System › About. On a Mac, open the Apple menu and choose About This Mac. Include the version number if support asks for it.
Describe the problem in plain language. Note what you were doing, what you expected, what happened instead, and any error message exactly as it appeared.
List recent changes and the checks you have already tried. Include updates, new devices, changed settings, and whether restarting or reconnecting changed anything.
Keep the note focused on the problem. Share it through the company's known support portal, phone number, or other verified channel, not in a public post.

You do not need to send every system detail just because it is available. For a display issue, screen details may matter. For a computer that shuts down, the processor and power or battery context may help. For a connection problem, note whether you are using Wi-Fi or Ethernet and when the issue occurs.

What system details are useful?

Device and operating system

Start with whether it is a desktop, laptop, tablet, or phone, plus the operating system and version. The same steps can differ between Windows 11 and macOS, and a technician may need to know if you are using a managed work computer. Include the device model only if you know it and it is relevant. You can usually find it in the system's About page or on a label, but do not include serial numbers in an ordinary support message unless the official support process asks for one.

Processor and graphics

These details are useful when an app runs slowly, crashes during a graphics task, or reports that the computer is unsupported. Record the names shown by System Info, but do not treat a browser test as a full hardware inspection. It may not reveal every component or confirm that a component is working correctly.

Screen details

For blurry text, a blank display, or problems using an external monitor, note the screen resolution and how many screens are connected if that information appears. Also describe which display has the problem. A photo of the screen can help if it does not show private documents, account names, or notifications.

Battery and power

Battery information can help with complaints about sudden shutdowns, short battery life, or a laptop that behaves differently when unplugged. The browser only shows battery information on devices that report it. A battery percentage or drain reading is not a diagnosis of battery health, so describe the symptom and when it happens as well.

Network details

For slow or interrupted calls, say whether you were on Wi-Fi or wired Ethernet and whether other devices had the same problem. A network result is a snapshot, not proof that the connection is always healthy. You usually do not need to send your Wi-Fi password, public IP address, or the names of nearby networks to describe a basic connection issue.

How to make the note useful

Give a time and pattern. Say whether the problem happens every time, after the computer has been running for a while, or only during a particular task. If it comes and goes, note roughly when it started and how often it happens.
Separate facts from guesses. Write “the display went black for five seconds” rather than “the graphics card is failing.” A clear observation helps the technician test possible causes without locking onto the wrong one.
Record steps already tried. Mention any restart, cable change, update, or setting change, and what happened afterward. This prevents repeating a step that did not help and gives support a useful before-and-after comparison.
Capture error wording carefully. Copy the message or take a screenshot if it contains no private information. Preserve punctuation or an error code, since a similar-looking message can point to a different issue.
Ask what else is needed. A technician may need a log, a version number, or a specific test result. Ask which item is necessary and how to send it securely rather than sharing a large collection of files at once.

If the System Info page shows a memory amount, treat it as an estimate. Browsers receive only a rounded hint about RAM size, not the exact installed capacity. For a support case that depends on exact memory, confirm it in the operating system or with the device manufacturer.

Protect your information during remote support

Verify that the person contacting you is connected to the support request you opened. If the contact was unexpected, end the conversation and reach the company through a phone number or website you already trust. Do not share your account password, one-time sign-in code, recovery key, or payment details during a screen-sharing session.

Before allowing remote access, close personal documents and private browser tabs, and turn off notifications that might reveal messages. Watch the screen while the technician is connected. If they ask to access an unrelated account, install an unexpected program, or take control without explaining why, pause the session and confirm the request with official support.

For a privacy-focused checklist on sharing device diagnostics, see how to share system diagnostics without exposing private info.