i love languages and linguistics and other cultures but please, for the love of god, if you're going to call tech support, you must be able to speak english and understand what "forward slash," "capital letters" and other such technical terms mean. honestly, it is hard enough to explain this stuff to NATIVE english speakers, and i already have to repeat myself at least ten times to get them to the right website. but if you don't even have the basic linguistic understanding to parse the sentences i am saying, how am i supposed to help you?
i know this sounds horribly racist, but it's true. of course, the flipside of this is outsourced (to bangalore) tech support, and the customers not being able to understand the techs. i'm all for linguistic diversity, but some level beyond basic language skills needs to be in place for us to be able to understand each other. this is why, despite the fact that i can speak spanish, i don't take calls in spanish -- because i don't have the technical vocabulary.
grr.
i know this sounds horribly racist, but it's true. of course, the flipside of this is outsourced (to bangalore) tech support, and the customers not being able to understand the techs. i'm all for linguistic diversity, but some level beyond basic language skills needs to be in place for us to be able to understand each other. this is why, despite the fact that i can speak spanish, i don't take calls in spanish -- because i don't have the technical vocabulary.
grr.
no subject
Date: 2006-01-12 09:20 pm (UTC)One of our biggest pet peeves here is probably something interent to a culture - or maybe just inherent to an international phone connection - that really nothing can be done about: some callers from Eastern cultures will follow every sentence with "Hello?" and tend to interrupt a lot. Sometimes we're lucky if a whole sentence gets finished.
"Yes, I'm having a problem with my Excha -- Hello?"
"Yes, I'm here; go ahead."
"I'm having a problem with my Exchange server, do I need to send you anything? Hello?"
"If you don't mind, send me the log-"
"Hello?"
"...yes, I'm here. Send me the log file in the-"
"Okay, I will send you a log file, which one and what is your email address?"
I'm usually okay with these scenarios; others that I work with will usually need a smoke break after one of these.
no subject
Date: 2006-01-12 09:48 pm (UTC)We have a few employees for whom english is a second language. I do not fault them for that. What does bother me is the ones that after several years of working here are still no better equiped to converse with any complex language skills.
My observation over the few jobs I have had that many ESL individuals do not practice thier skills. Thier sole, or nearly sole, interactuion with others using english is on the job or in class. Othertimes they surround themselves with others whose native languagfe is the same and that is what they speak. As a result, accents do not fade and vocabulary and comprehension skills do not improve as fast as they might, if they improve at all.
no subject
Date: 2006-01-12 09:54 pm (UTC)no subject
Date: 2006-01-12 10:14 pm (UTC)OTOH, when I lodge a support req for my own domain with my domainhosts for an email problem, I expect it to be sorted, not to get a response after 3 requests and 2 months that says in very VERY broken english "have you checked your settings" *bangs head on desk*
no subject
Date: 2006-01-12 10:16 pm (UTC)no subject
Date: 2006-01-12 10:26 pm (UTC)anyway, yeah i don't have too much of a problem with thick accents (as long as they can spell things out if i can't understand them) or even weird linguistic twitches (like your example). it's where the person has absolutely no way of understanding what i'm trying to communicate to them -- that's when i get peeved.
no subject
Date: 2006-01-12 10:30 pm (UTC)no subject
Date: 2006-01-12 10:35 pm (UTC)no subject
Date: 2006-01-12 10:48 pm (UTC)no subject
Date: 2006-01-12 10:50 pm (UTC)no subject
Date: 2006-01-12 11:34 pm (UTC)One of the clients I used to do work on site had engineers from Japan come over all the time, and they used the Japanese language version of windows. 200's IME support sucks, BTW. XP was very cool on the few machines that had it, as I could change the language, wait a minute or two while the OS re-loaded everything, and I could do my work.
Often times it would end up being the user at the control (or our Point of Contact at the control), the user sitting behind him, and me walking the person at the keyboard through what was going on. (our P.O.C. was fluent in both english and japanese, and acted as our translator when I had to fix stuff for them.)
Oddly enough, these folks were pretty high level engineers. they built optical inspection systems for silicon wafer inspection after the etching process.
no subject
Date: 2006-01-13 12:39 am (UTC)no subject
Date: 2006-01-13 01:31 am (UTC)I get a lot of flac for my support of English only workplaces, much like what California instituted. I have been accused of being racist or a facist.
I really believe that if your job requires verbal or written interaction with co-workers or customers, you should be fluent in the language that is spoken there.
An argument I get is, what about interpreters? Actually many interpreters speak excellent english in my experience. But they are well trained, and they are taught the importance of practicing.
If I was in another country, I would take every opportunity to speak the native language. Even with other native english speakers, I would look at it as an opportunity to practice. The only reason in those situations to speak english, is to try to clarify something that I am unable to comprehend or explain in the other language. But you can bet I would be learning that PDQ.
no subject
Date: 2006-01-13 02:08 pm (UTC)no subject
Date: 2006-01-13 02:31 pm (UTC)On the other end of that equation, my mother was having issues with her EarthLink email last time I was home, so after tinkering with it for a while, I called EarthLink support and promptly wound up talking to an L1 somewhere on the Subcontinent. She was obviously reading from a script, and frankly almost sounded like a computer. Her accent was also so thick that I had to ask her to repeat virtually every single sentence, sometimes five or six times. (And I'm actually used to deciphering Indian accents, because we have a large Indian community here, and my brother-in-law is Indian.) Good waste of 45 minutes of my life, just to have her tell me someone would call back.
And yet, that's the sort of support I'm indirectly losing my job to. Well, you get what you pay for.
no subject
Date: 2006-01-13 02:33 pm (UTC)We know have a large customer base in Haiti. I've had calls so bad I can't even manage to get the person on the other end to understand you need to call this other number. The person didn't even know English numbers. That was a pain in the ass. And I am supposed to help this person point a satellite dish? I think not.
no subject
Date: 2006-01-13 04:04 pm (UTC)no subject
Date: 2006-01-13 05:51 pm (UTC)no subject
Date: 2006-01-13 05:53 pm (UTC)no subject
Date: 2006-01-13 08:11 pm (UTC)me: hello, may i have your username please?
them: hello?
me: yes, may i have your username or your email address?
them: my computer it does not work!
me: OK. I need to know what is your USERNAME first please.
them: i sorry i do not understand, i am not so good with english
me: That's OK. What is your email address?
them: my email! yes! it is not working! can you fix?
me: I will try. What is your name please?
them: XHSHRIVIAULINGIJANIO.
me: Spell it please. X like... uh.. xylophone?
them: I am sorry my english is not so good, I don't know what you say. My computer is broken.
And so on, we never get anywhere with these calls.
no subject
Date: 2006-01-13 08:31 pm (UTC)no subject
Date: 2006-01-13 08:38 pm (UTC)i get a lot of calls transfered from bellsouth and sbc and, let me tell you, those folks are always ridiculously pissed off. they usually calm down when i solve their problems in 10 minutes, when they've spent 3 hours with sbc...
no subject
Date: 2006-01-13 08:38 pm (UTC)sigh.
You know what's scary?
Date: 2006-01-14 08:52 pm (UTC)no subject
Date: 2006-01-15 05:43 am (UTC)no subject
Date: 2006-01-18 02:14 pm (UTC)