I can’t find a damn thing wrong with this analysis.
Of course I work in Technical Support two days a week, so that shouldn’t surprise anyone.
2) Stop trying to drive.
It is exceedingly rare that you’ll have a problem that the technician has never heard before. Most calls fall into one of a dozen or so categories that your tech has seen a hundred times at least. They know how to fix it.
There’s nothing wrong with telling a technician what you tried to right before you called. But after that, you’ll find that most tech support calls go faster if you just do what the technician tells you to do with a minimum of fuss. Interrupting to give information you weren’t asked for, to say “I already did that,” or worse, to say, “why am I doing this?” will generally only slow things down. Let the technician do what he wants, then if you’re really curious ask him after the fact what it was all about.
Abso-god-damn-lutely. Shut up and let me drive. I’ve been here before. Did I mention my 10+ years working with this product? Beats your 10 minutes all hollow.
4) Don’t emphasize your credentials and experience and try to impress the tech with how smart you are.
Damn straight. Start trying to tell me how smart you are and you immediately go to the back of the queue. (I don’t do phone support, so you’ll get an email from me when I’m done with everyone else.) If you flaunt your MCSE, I might get back to you next week.
And that guy Jerry who made an ass out of himself with his comment would be lucky if I even acknowledged his existence. That’s what we have junior techs for.
Now THAT’S funny. It’s a whole lot different getting assistance from IT people that work for companies other than the software or service provider. Where I work we call them the “Helpless Desk” because it usually takes two or three calls to get ANYTHING fixed. Even then we have to go up the food chain to Tier 2 or Tier 3 to get someone who knows what the Hell is going on.
I swear, the guy IT assigned to support our division is so dumb he couldn’t even be a teacher!