The sweetest thing for an IT person to hear

I love self-healers. Amen!

and of course, you still have to fill out the necessary paper work in the WO system … and bill your time accordingly!

ahhh… my favorite phone calls…

A> It happens everytime i do thi… it not doing it anymore. Never mind.

B> Well, while I was on hold, i got it figured out. Have a good one. :slight_smile:

Self Healers kick ass!

Ah, but let’s not forget that some self-healers don’t like to let go. Then, they call anyway and want you to somehow troubleshoot something that no longer exists. That can be much worse than the people who call with an actual issue to solve.

You mean, someone actually took the time to let you know they no longer had a problem?!? As opposed to waiting for you to travel across campus, find their building, find their desk, wait for them to get back from <whatever>, and THEN say “oh, that’s been working since this morning”!?!

Amazing. Simply amazing. :wink:

Reminds me of a commercial I heard on the way to work this morning:

“Fred, I just promised everybody remote access today. What is remote access?”

“Fred, you know that e-mail virus you told us not to open? I opened it.”

“Fred, I turned my computer off and on like you told me to, and now my phone doesn’t work.”

“Fred?”

Actually, this was a rare case. Usually I find out when I contact the luser. :slight_smile:

well, there is ONE thing you can hear from a luser that is even better than the OP. It goes something like “according to the manual, here on page 127, it says X but when I do it, Y doesn’t happen.” This is the best type of call, the luser is actually reading the manual.
I was once advised by a BOFH that I should conduct all tech support calls like this:
Luser: I have this problem.
BOFH: OK, what page of the manual did you get stuck on?
Luser: umm…
BOFH: OK, go through the manual, and call me back when you get stuck.

The idea was to divert all support calls into lusers reading documentation, if they hadn’t read the docs, no support, and most support questions are simple enough to be solved by reading the manual. This was obviously not a very practical idea, but I can see his point. I actually applied this successfully in training, I used to sit down lusers for training and start with “ok, let’s start with page 1 of the manual…” Some people wont RTFM without someone sitting beside them making them do it. I made a lot of money watching people RTFM.

I love this. It’s so fun watching their little eyes light up when they find the solution the problem themselves. Then, some even realize how annoying they’ve been, and actually appologize!

Geez, and here I thought the sweetest thing was “Thank you.”

Although…what you mentioned is nice too.

My favorite response to situations like that is “Thank you for calling the Psychic Helpdesk. Our clairvoyants noticed the problem and we dispatched the faith healers immediately. Your bill has been telepathically beamed to you.”

Some lusers reward you with gifts. I have, on separate occasions from differnet people received candy, a nice coffee mug, and a bottle of wine.

Isn’t it amazing??

I swear that in my last job, every time someone said “This doesn’t work”, I sat down and tried it and it worked.

They started looking at me with a little fear in their eyes. They knew I didn’t do anything, but they also knew it didn’t work before I sat down. :eek:

Actually I don’t mind the disappearing problem too much. Sometimes I have them, too, after all. :wink: But I wish I got gifts.

I like the “what page of the manual…” idea. Too bad we don’t actually have any of those. :frowning:

I think the one that ticked me off the most was when I spent over an hour trying to resolve a problem on a dumb VT terminal. I didn’t handle those very often, I was covering for someone else. I only asked five or six times, “Have you moved this or touched any of the cables?”, since that was our most common problem. Every time, they insisted that they had not even TOUCHED the thing, it just quit working.

Eventually I realized that they had plugged the mainframe cable into the telephone socket. When I pointed this out, they actually said “Oh, well, yeah, we must have done that when we moved it. We had to move it in order to move this desk, you know.”!!! :mad::mad::mad:

Yeah, there’s a BOFH term for this, “I/O Error” (Idiot Operator).

I explain this (to help the person feel better) that the computer knows I am on the way and it fixes itself, it’s my kharma or something. It may be wrong but gives them a little giggle to know that stuff happens like that. :wink: Just like when you take your car to the mechanic. It suddenly stops it’s horrible tantrum.

I just call it the Hammack touch.

We refer to it as an ID 10 T error

The famous PEBKAC

Problem exists between keyboard and chair.

Or the BSD (not BSOD) error - between seat and desk.