From my own journal...

[fuego.livejournal.com]

Is it too much to ask for that my coworker should learn to do her job? Seriously, it's not brain surgery. It isn't even rocket science.

I'm sick of being the answer girl for someone who's been here for over four months now. It's always the same questions too. I should make up a little chart and stick it to her monitor. Get the customer's information, get their serial number or model name, click a few buttons, enter a line or two of notes, give them the ticket number and get them the hell off the phone and if they have a contract, call their account tech. Why is it that you can't do in ten minutes what I can do in less than two? Hell, even in my first couple of days, it took me less than five minutes.

Don't hang up without creating a ticket- especially on an elite contract, but don't do it at all. Don't write it all down and open the ticket after they're off the line. Don't talk in a garbled voice that I can't even understand sitting next to you. Don't ask me the same questions five times a week. Learn a little bit of call control, trust me it will make your life so much easier. No, saying "Oh, well I guess if you want I could call the on call tech and see if they'll call you back" to someone who doesn't have a contract or a business critical issue is NOT call control, it's showing them that you're a spineless wuss. Don't snore. I don't want to hear it. This is job time, not nap time. Don't get pissed off at me when you can't get someone off the line because of your spineless wussiness when they hang up, call back get me and I have them on their way in two minutes with barely a peep of protest. Don't take your lunch break the hour before the shift is over and leave me with all the incoming early morning calls.

Don't say "Do you know what I mean" every other sentence when speaking to me. Don't say "Do you hear what I'm saying when you're not saying "Do you know what I mean." If I don't hear you, and if I don't understand what you're saying, if I care, I'll ask for clarification, thanks.

Just learn to do your blasted job. You had a week of training for what others have picked up in a matter of a few hours with no problem. You've been doing this for months now. Why is this so difficult to grasp?

*tears hair out*

Edit: Oh my god. Tell me she didn't just not open a ticket on an elite client, make two unsuccessful attempts to get ahold of the account tech and then go on lunch without bothering to try and call the backup or supervisor???

I just had to fix her screwup. Which meant a phone call to one of our supervisors (Oh well, I had to tell him why I called, hopefully now something will happen to remedy the issue.) And a couple of other phone calls to the client (who wasn't too thrilled that forty minutes after he called, we haven't even made contact with a tech and to the tech himself.)

...

[toxico.livejournal.com]

Wow, people sure do get bitchy when you don't just arbitrarily give them a password simply because they asked.

"We're trying to install some security cameras, and the port over which the feed is broadcast is being blocked by this application. What's the password to unlock the interface so I can edit the policies?"
"How do you know it's that application doing it?"
"It's in the log file."
"Okay, fair enough. Can you send that to me?"
"What?! Can't you just give it to me?"
"Only after you show me the log file."
"This is ridiculous grumble bitch mumble inefficient blah."

~45 seconds of verbal diarrhea later~

"Yup, there it is! Here's the password."


See, was that so HARD?! Douche.

Grrrr....

[laptop-mechanic.livejournal.com]

Okay, Sony. 2 DOA motherboards in a row? Both DOA for different reasons? Do you guys even CHECK stuff before you ship it out? Frak this. I'm shipping the machine to you and letting YOU fix it. I'm not tearing this thing down AGAIN. Hire some competent engineers to design your parts, please.