upvote
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).

reply
As a bonus, half the time the customer unplugs their own phone line, dropping your average call time metric.
reply
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.

reply
I've only believed the ethernet cable is connected if I get that satisfying "click" sound.
reply
This is so thoughtful that it should be able to be transposed to software support
reply
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.

reply