don't say i didn't warn you...

[reanimated.livejournal.com]

hey guy. that's really neat and special that we work for the same company. but i'm betting you're not in support. here's why.

1. you would know that you suddenly being in a rush and demanding an instant fix is outside my scope of support, and does not make the troubleshooting go faster. ;p especially when i'm on two chats and am consulting with someone who is also on two other chats.

2. you would know that our support is very departmentalized. thus, you would know that when i in fact tell you the next step, but that you should contact another department WHEN YOU HAVE TIME to walk through backing up files, it's in your best interest. you wouldn't say that's bad customer service. i don't really want to nuke your data and you don't want to either. but when you decide to nuke it on the run anyway, don't say i didn't warn you.

thank you kind people for letting me vent. i swear, a little bit of knowledge is the most dangerous. ;-)

Comments

[docskurlock.livejournal.com]

Yeah, I'm rooming with a guy right now that swears he's been working on computers for 17 years...but he's having a hard time figuring out why his network keeps dropping out. He also insists that his wireless N card is better than using a regular b/g. Eh.

[reanimated.livejournal.com]

Tellin ya. It's easier when they know what they don't know.

The former teacher in me kind of enjoys explaining cnames and what happens when it points back to the domain name or isn't there at all. ;-)