The Woes of Wireless

[Samaliel]

Quoth Blade_Raver

May it also be said that the department this guy is in has absolutely NOTHING to do with the creation or mass transport of company product. He had no right to call the helpdesk during afterhours. Period.

You've mentioned that in another post, and I want to be sure I understand this right:
- per company policy, they're not supposed to call the after-hours help desk if their task isn't business critical and regarding either creation or mass transport of the company's product;
- but, as per the same company policy, you have to deal with whatever idiot not fitting in the aforementioned business critical scenario, right there and then,

What kind of crap policy is that? If you have to take every and any call, no matter what, there's not much point in forbidding some of them to call, since they will get away with it any way...

I'm willing to bet pennies to bucks that the problem was his router configuration.

[Captain Trips]

Don't you just love those users who are too dumb to troubleshoot themselves, yet are so certain that it isn't the <insert type of equipment here>? Like, how would they know?

These are the ones who, after I fix the problem, ask "what caused that to happen?" As if they would understand the answer? (I once told the user, "Well, it seems the ODN conduits got stuck in the oscillating Framistat mode." Her response to this Trek-related doubletalk? "Oh, I see. That does make sense.")

[technical.angel]

Isn't there a web site that generates tech talk excuses like that?

[EricKei]

I'm going to need half a dozen Niad Pulse Converters and an Anza Brush...

Or am I bluffing?

[Bandit]

Quoth technical.angel

Isn't there a web site that generates tech talk excuses like that?

THIS is one of many. Do a search on BOFH Excuse Generator.

It's a handy tool to have when dealing with the turnips we call users.

B