How to Ask for Tech Support So You Get Good Answers Quickly

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, both 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.

  1. 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.)
  2. 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.”
  3. 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.”
  4. 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:

  1. 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.”
  2. 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.”
  3. 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.”
  4. 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.

AI Usage Transparency Report

Pre-AI Era · Written before widespread use of generative AI tools

AI Signal Composition

Rep Tone Struct List Instr
Repetition: 65%
Tone: 65%
Structure: 65%
List: 8%
Instructional: 45%
Emoji: 0%

Score: 0.07 · Low AI Influence

Summary

A guide on how to effectively communicate with tech support, including steps to troubleshoot problems and ask for help.

Related Posts

Setting up Ollama on macOS

Recently, after some bad experiences with OpenAI's ChatGPT and CODEX, I decided to look into and learn more about running local AI models. On its face it was intimidating, but I had seen a lot of people in the MacAdmins community posting examples of macOS setups, which really helped lower the bar for me both in terms of approachability and just making me more aware of the local AI community that exists out there today.

Read more

AI Agent Constraints and Security

I really feel like in this era of AI it's essential to write about and share experiences for others who are leveraging AI, especially now that AI usage seems almost ubiquitous. Specifically, when it comes to AI in development and the rapid growth of AI-driven automations in the IT landscape, I believe there's a need for open discussion and exploration.

Read more

ABM Warranty 0.4.1

The 0.4.x release series for ABM Warranty is focused on operational scale. The earlier 0.3 releases were about trust, correctness, and stabilizing the foundation. Version 0.4.1 builds directly on that work by making the app more practical for consultants, internal IT teams, and managed service providers who need to support multiple environments without losing isolation, control, or visibility. This includes improvements to user interface and workflow, as well as enhanced reporting capabilities to help these users manage their workflows more efficiently.

Read more

Vibe Coding with Codex: From Fun to Frustration

So there I was, a typically day, a typical weekend. As a ChatGPT customer, I had heard good things about Codex and had not yet tried the platform. To date my experience with agentic coding was simply snippit based support with ChatGPT and Gemeni where I would ask questions, get explanations and support with squashing bugs in a few apps that I work on, for fun, on the side. There were a few core features in one of the apps I built that I wanted to try implementing but the...

Read more

Why Apple Fleet Risk Isn’t a Security Problem—Until It Is

Security and risk are often treated as interchangeable concepts in modern IT environments, but they are not the same discipline. Security focuses on controls, enforcement, and prevention. Risk management, by contrast, is concerned with likelihood, impact, and consequence across operational, financial, and organizational domains. Frameworks such as those published by NIST make this distinction explicit: risk assessment is not a technical exercise, but a business one. Technology informs risk decisions, but it does not define them.

Read more

ABM Warranty 0.3.1

The 0.3.x release series for ABM Warranty is about tightening guarantees. Where earlier releases focused on surfacing data and making long-running operations observable, 0.3.x focuses on ensuring that what you see is complete, consistent, and safe to trust—particularly as the app is used in larger, slower, and more varied environments. This shift in focus aims to provide a more reliable foundation for users who require higher levels of assurance from their warranty management system.

Read more

ABM Warranty 0.2.0

ABM Warranty 0.2.0 is a feature release focused on visibility, safety, and scale. This version does not change what ABM Warranty is meant to be, but it significantly improves how the app behaves under real-world conditions—large device counts, API throttling, long-running imports, and the kinds of failure modes Apple IT admins actually encounter. The improvements in this release are designed to make the app more reliable and efficient, allowing it to handle complex scenarios without breaking or becoming unresponsive.

Read more

Running a Beta Program: Lessons Learned

Shipping software in isolation is comforting. You control the inputs, the environment, and the narrative you tell yourself about how things work. The moment you invite other people in—especially people who don’t share your assumptions—you lose that comfort. You also gain something far more valuable. Running a public beta for ABM Warranty through Apple’s TestFlight program forced me to confront that tradeoff head-on, and it fundamentally changed how quickly and confidently the app matured.

Read more

The Day I Unmanaged a Mac Into a Corner

There are a few kinds of mistakes you make as a Mac admin. There are the ones that cost you time, the ones that cost you sleep, and then there are the ones that leave you staring at a perfectly good laptop thinking, “How did I possibly make this *less* manageable by touching it?” These mistakes often stem from a lack of understanding or experience with macOS, but they can also be the result of rushing through tasks or not taking the time to properly plan and test.

Read more