The last couple of days up here have been really slow. Although slow periods make you feel good, because it means you've been doing your job well and no one's having any problems, it also is kind of unfortunate because you are forced to live on your salary alone instead of the extra cash you bring in for actually doing repairs.
I'm sitting at my desk, going for the new high score on Minesweeper, when the phone rings for the first time in about 20 minutes. When it's slow like this, the techs fight over who gets to answer the phone; sitting at your desk playing Minesweeper for hours is all well and good, but it makes the shift seem as though it's never going to end.
I jockey with the other 15 techs in the office for the phone and come out ahead, picking up the line and slipping my headset on in one deft motion.
"Technical support," I say with a flourish, "How may I help you?"
"Yeah," says the gruff voice on the other end, "I'm still having the same damn problem as before!"
I don't say anything. Lots of calls start off like this, with unbridled anger from the client. At least 50% of my job is just getting the person on the line to calm down and not freak out about the issue that they're having.
But instead of continuing to explain the problem, the client waits on the phone in silence. After about 45 seconds of no talking, I finally say something.
"Are you there?"
"Yeah I'm here! What are you doing to fix my problem?"
"What problem is that, sir?"
The client is flustered. "The same problem I was having before!"
"And what problem is that, sir?"
"Aren't you the one I just talked to?"
I look around the office again. There's a cluster of techs checking results from the Olympics. There's another talking on his cell phone to his wife. Behind me, there's two techs at the water cooler finalizing their plans for the weekend in hushed voices (they still think their inter-office romance is a secret). I put my client on hold.
"Hey," I shout to the office, "Has anyone been on the phone with a client in about the last half hour?" My question is met with head-shaking and verbal denial. I pick the phone back up.
"No sir, I wasn't the one you were just talking to, but I'll be happy to help you out."
"Well, I'd rather talk to the young lady I was speaking with before, since she already knows what's going on."
"That'll be fine sir, do you know her name?"
"Well how should I know? You're the one that works there!"
"That's true," I sigh heavily, "But we have eight ladies in this office right now, and at least six of them could be considered 'young' so I'm not sure who you're referring to." I'm trying to make the situation more lighthearted, and failing miserably.
"Well you need to find her," my client says, "She's the one I talked to two weeks ago!"
"So when you say you 'just' talked to someone, you mean you talked to them two weeks ago?"
"Could've been three, I guess."
The company I work for is not a huge one, but our total number of tech support employees is in the 40s. Even if it wasn't and I was the only employee in the building, why would someone assume I could remember their problem from two to three weeks ago? If the client can't even remember the name of the tech he spoke to, how would I remember anything about him?
Assuming I had a photographic memory and actually
could remember his problem, how exactly does he expect me to recall it if he doesn't even give me his name? Am I now expected to have a photographic memory
and be a mind-reader?
Just a note to everyone who uses tech support - I have no idea what your name is or what problem you're having, even if you talked to me two minutes ago. When we hang that phone up, we immediately wash our minds of everything that just happened on the phone. Every time you call tech support, just assume you're going to have to start at the very beginning and you'll be pleasantly surprised if we actually
do remember you.