I lol'd

[theotherhiveking]

Look what i found in Slashdot.

I once had a user call because he "couldn't get into his e-mail." After about half an hour of being stonewalled on the phone, it turns out that:
1. He couldn't load his e-mail because he couldn't run his e-mail application.
2. He couldn't run his e-mail application because he couldn't run windows.
3. He couldn't run windows because his computer wouldn't turn on.
4. His computer wouldn't turn on because he had yanked out the previous motherboard, stuck in a new one (without a CPU, of course), and just assumed everything would work.
5. Seeing as how this was painfully stupid, he didn't actually tell the tech support this for fear that the tech support would figure out what he had done wrong.
6. And, instead of calling the hardware manufacturer's help line, he called his ISP.
My second favorite tech support call was a user who was having trouble getting online, and no matter how many settings we changed nothing seemed to fix it. "Hardware problem" you suggest? Yup. Over the weekend someone had bulldozed the wall with her network jack.
No matter how bad things might get at my current job, at least I'm not doing tech support.