Why won't God strike me down?

[mtlchick.livejournal.com]

I've been on this call now for over 2 hours.
I am sure that this is an ID1OT error.
However my company policy is that I have to prove it.
Please kill me.

Comments

[pisceandreamer.livejournal.com]

*bang*bang*bang*bang*bang*bang*bang*

Did that help?

(I totally understand.)

[moosie.livejournal.com]

Give me an address and I will go and stomp on the lUSER'S fingers so they cannot perform any typing functions. if it will help :)

~M~

[loosechanj.livejournal.com]

More info plz. Perhaps someone could suggest an exit strategy.

[mtlchick.livejournal.com]

It's okay, I'm out now. It was just one of those calls where you KNOW that you're missing something obvious because the user is so slow. (Did that make sense?)

[loosechanj.livejournal.com]

Yeah, that's pretty much what was I talking about when I said someone ought to make a "how to talk to tech support for dummies" book.

[marahsk.livejournal.com]

OK, but if the people who need to read How to Talk to Tech Support for Dummies were the sort who would read ...for Dummies books, they wouldn't need to read it.

[lrdjester.livejournal.com]

I feel for you...

I've been on some long calls too.

My longest was almost 8.5 hours (during an 8 hour shift). My team lead just about had a stroke, was sure I screwed the call average for the week for his entire team. When all was said and done, my call average for the week was like 22 minutes.

[loosechanj.livejournal.com]

What in the name of all that is good and true and fine in the universe could take EIGHT AND A HALF HOURS??? Seriously, I gotta hear that story.

[ex-prunesnp.livejournal.com]

Dunno about his but I had a call last year, maybe 18 months ao, that was 12 hours, and THEN I called someone else in cause I thought I would die. It was a Saturday, too, and started at 8 am. (I do a pager rotation.)

[lrdjester.livejournal.com]

Well...

I can't exactly remember what the issue was. I was doine Win95 support and this guy called in at the beginning of my shift. He was a business executive (sales drone) on a trip. He had a laptop that he used for presentations and it wasn't working.
I worked with him for about 45 minutes and when I went to transfer him into the escalation queue, I was told by my team lead after 30 minutes of going back and trying stuff to get his info and a tech would call the next morning. As it turns out, he was in a different city everyday that week and wouldn't know his hotel until that evening for the next day. Needless to say he wasn't willing to let me off the phone until I was able to pass him off to someone else. Well, I did work with him off and on, and we made a little progress, but it was not fixed when I finally got through to a next level tech. As it turns out, a project manager ended up clearing a queue for me to have it transfered. I was told that it ended up in the hands of an MS Senior Engineer that couldn't get it resolved.

[dmsalem00.livejournal.com]

all week i can see it now

wrong queue - transfer
wrong queue - transfer
wrong queue - transfer

those things really help your call time..

[lrdjester.livejournal.com]

No, I didn't transfer many people. I had about an 85% solution rate. Nor did I resort to the tactics of other techs, their solutions were often "FDisk, format, reinstall. Goodbye."

I feel for you

[bottleopener.livejournal.com]

They need to print lables on computers " Dont buy this product if you are over the age of 50. "

So many calls i got of elderly people that didnt know what the fuck they were talking about . . and they believe themselves to be RIGHT all the time, no matter what you say. . .

Them: " I KNOW what im talking about son, i have a degree in somethingorrather and i was in somewaroranother so dont you sit there and tell me that im not doing it correctly "

Me: ( as im trying really hard not to slam m head on the desk ) Please listen to me and do as I say, and your problems will be solved. "