Need help with something? On occasion, we all need tech support. Speaking as the people who are sometimes on the other end of those requests for help, we have some suggestions on how to get the support you need as quickly as possible.

For instance, think about what we have to do if we receive an email message along the lines of “I keep getting a note that my backups aren’t working.” All we can tell from that message is that something may be wrong with the user’s backups. But without knowing what app they’re using and what the specific error is, we can’t even begin to recommend a solution. We’ll have to go back and forth to figure out what we need to learn to address the problem. By the end of the (possibly lengthy) process, the user and we may be quite frustrated.

So here’s a simple set of steps you can use to get to the heart of a troubleshooting problem whenever you’re communicating with tech support.

Describe your setup as it relates to the problem. Whenever possible, be specific about what apps you’re using and include screenshots or videos. In our example above, this might involve saying, “I back up with Time Machine to an external hard drive. It has been working fine, but now I’m getting this error.” (Obviously, if you’re talking on the phone, it might not be possible to share a screenshot, but you can read it to the support rep.)
Next, explain how you’ve tried to resolve the problem so tech support doesn’t automatically tell you to repeat the same actions. (They may anyway, just to confirm that you did everything properly, but it’s still a help.) You might say, “I clicked OK and let Time Machine try again, but I got the error on the next backup too. Then I launched Disk Utility, selected my Time Machine drive, and clicked First Aid.” Finally, explain what happened (or failed to happen) when you took the actions in the previous step. For instance, “First Aid also reported an error.”
At this point, you may need to repeat Step 2 and 3 for each thing you tried, but you’ve given the support person enough for them to start recommending other courses of action. (In this case, we’d have you erase the drive using Disk Utility and see if that eliminated the error. Even if it did, we’d recommend that you get a new backup drive since you don’t want to depend on a potentially flaky drive for important backup data.)

The steps are a little different if you’re trying and failing to figure out how to accomplish some task. Try this script:

I want to _____. State what you’re trying to achieve, and as before, make sure to say what apps you’re using. For instance, “I’m using Preview to read a PDF, and I want to print it with four pages per sheet of paper to avoid wasting hundreds of pieces of paper.” I tried ____. As before, explain what you’ve already attempted, as in: “In Preview’s Print dialog, I tried choosing 4 from the Copies Per Page menu.”
What happened was _____. Finally, explain what happened after what you tried, and why it was wrong. “That caused me to get four copies of the same page in the preview, rather than four different pages.” Again, you may need to repeat Steps 2 and 3 for everything you tried, but in this case, we have all we need to explain that you need to click the Preview menu in the middle of the Print dialog, choose Layout, and then choose 4 from the Pages Per Sheet menu.

One last thing. It’s always important to explain your overall goal, rather than just ask a specific question. In the example above, for instance, saying that your goal was to reduce paper usage was helpful because we could then suggest that you select the Two-Sided checkbox near the top to print on both sides of the paper, cutting your paper usage in half.

So next time you need to contact tech support, make sure to use these tips, and you’ll likely get better support and a faster resolution to your problem.

(Featured image by Christina Morillo from Pexels)

Social Media: Do you have frustrating interactions with tech support? Follow our advice on how to talk to a support rep to get better support and a faster resolution to your problem.