I got annoyed when I had to call in for product support on a server a few yers back.
When I heard the thick accent, and the speech patterns that screamed "Hi sir, I am reading a script for you!", I felt part of my soul try to commit seppuku.
What followed was pretty bad. To get the story straight, what happened was we had a server with dual-processor capability, but one of the CPU modules (P3 Xeon) conked out. I managed to verify that the board was fine, using scraps from the IT junkbin...but I had to get them to get me a new CPU. Keep in mind I was a certified repair tech for that brand of server at the time, but for warranty repair, I still had to call in...however for some reason the direct contact number we had now went to generic support.
(my quotes are in 'these', his quotes are in "these"
'Yes, this is Steve _____ , service tech ID # _________, service account # ________ we have a server, serial ________, which needs a new secondary CPU due to failure, a PIII 1ghz Xeon.
"we don't support that".
'what, how can you not support your own hardware'
"what hardware"
*bonk!*
'I was talking about a processor'
"so what's the problem"
'the second processor on this system is not functioning'
"oh, you have to make sure the software is designed for dual-processor applications"
'I know that, I mean the second processor is dead'
"what do you mean by, dead?"
'it won't work, at all. I have to remove it for the system to boot'
"are you sure this processor is compatible with your hardware?"
'dude...(the manufacturer) shipped it to us with these processors...of course it's compatible'
"uhh...."
*long pause*
"sir, have you checked to be sure the processor is fully seated"
'yes'
"can you reseat all PCI cards"
'easy, there are no PCI cards, everything is built-in to the mainboard'
"is it done yet?"
*sigh*
'yeah it's done'
"so does it work?"
'no'
"hmm...."
'may I be so bold as to make a proposal?'
"what do you mean?"
'how about you escalate this so I can get this done with, it's 3am over here, and I really need to get this done with so I can get home, and get 3 hours of sleep before I get here for a meeting on why this server has went down.'
"I can't do that sir"
'why not?'
"I just can't"
'can I talk to a supervisor then?'
"he's busy right now"
'what's your full name again'
"Wayne"
'Wayne what?'
"wayne"
'nevermind'
*click* (I hung up on him...)
I ended up having to get the server up using underpowered CPUs and having to do another service the next weekend with the replacement part. Needless to say we dropped that comapny after I got chewed royally and they lost about 3mil in annual business over a poorly trained support person that didn't listen, and refused to escalate when he ran out of ideas.
Amusingly enough, from what some of my friends in other companies said, they went back to US support for corporate accts soon after. I guess there were quite a few people that got chewed over it.
I also had great offshore support experiences, it's all a matter of training. In the above case, they probably drug some guy with no education beyond primary school, dropped him in front of a computer, and showed him how to use the automated system. Script readers are by far the worst types of support...anything beyond the norm, and you are pretty much stuck downriver without a paddle.
Trained offshore, OK....untained/scripted any-shore, not OK.