Tech support for naive (no offense) customers is an art. A friend's mom was a customer service rep for RCA TVs back in the day (way, way back in the day). Customers would call and complain that their TVs were doing nothing: no lights, nothing.
The standard response would be to ask them to pull the TV's (non-polarized) plug, reverse it, and plug it back in. This was generally successful, NOT because the plug polarity mattered, but because the customer had actually forgotten to plug in their TV.
If the rep had said "is your TV plugged in?", many customers would indignantly say "Of course!" without even checking. The "reverse your plug" request was more successful because it sounded like the customer was doing something intelligent. And, when they went to perform this task, they would discoverer that they'd forgotten to plug their TVs in. The customer could then report that the reversal worked, nobody would mention the unplugged TV, and everyone would be happy.
Yes, well, one time I was setting up on a new PC and I was getting a weird linux error about the network being unreachable when I tried to install some stuff. I went to the support desk and told one of the IT gods there what happened (those guys were really gods). He mumbled something like "I think I know what that is" and walked back to my desk with me. He knelt behind the tower, connected the ethernet cable and said "try now".
I have never felt so embarrassed in my entire life. I don't think I ever will.
This is so thoughtful that it should be able to be transposed to software support
I worked at a PC shop as a teen. People would bring home their newly fixed system then phone it to complain that it was dead.
Inevitably this would be because the switch on the back was OFF but the user normally turns their computer on through some kind of power strip.
Any form of asking them to turn that switch ON wouldn't work-- either they'd angrily say they already turned it on, pretend to do so, or just refuse.
It was far more effective to tell them to reach behind and turn the switch OFF. "Oh! it's coming on!".
Much later I worked as a field engineer for Juniper and was impressed by the number of times the customer and I would grind on an issue only to try support and have them solve it with basic procedural steps that avoid assumptions and begin with the basics-- stuff that "obviously" doesn't apply. Ever since I've tried to remember that experience and apply it to my own troubleshooting and I think it's been helpful.
Similarly: when I needed to guide users to check the wiring of their DSL modems, they of course always claimed that everything was hooked up exactly as stated on the little diagram that we sent out.
Asking them to blow the dust out of the RJ11 ports made them remove the cables and actually plug them in the right way around. Hard to say how many of them just got it right the second time and how many of them noticed their mistake but didn't want to admit it, but either way, it saved them waiting a day for a tech to come out (often at their own cost).