More Adventures in Troubleshooting

Today, with some help from a coworker, I finally got around to unraveling the mystery of a trouble sheet that came in last week. No major issue, just slightly weird. I email the person who reported the problem and gave her the details on why it wasn’t really a problem – i.e. yeah, we know, it’s inconvenient, but there's nothing we can do about it, and here’s why it shows up this way.

She then proceeds to come down to my floor and look for me to tell me that I must be wrong, there’s no way that there’s not a problem. Luckily, my coworker intercepted her and fetched up some technicians to explain to this stupid cow why I was right.

Allow me to dispense some Totally Amazing Advice: If you’re going to ask for help correcting a problem you have no goddamned knowledge of or experience with, don’t tell the people who know how to fix it that they’re wrong.

Seriously, lady? Fuck you. Just because I gave you an answer you don’t like doesn’t mean it’s not the answer. I’m not a mouth-breathing customer service rep over here. I’m a tech specialist who consulted with electrical engineers on your issue (you know, just in case it was legitimate), and you’re gonna tell us we’re wrong because you don’t like what we tell you? Your skill is typing, and you know better than me? No. No, you don’t, and actually, I’d wager there is precious little in this fucking life you know better than me, unless it’s how to be a fucking retard, because you’ve pretty much got that whole area wrapped up. And good luck getting your tech problems handled in the future, because God knows if there’s anything we fancy-pants tech folks like, it’s a glorified stenographer who questions our knowledge about data collection. Can you fuckin' dig it?