I wasn’t planning on calling tech support yesterday. I really wasn’t. But my printer decided to have what I can only describe as a nervous breakdown, flashing lights I’d never seen before and making sounds reminiscent of a small animal caught in machinery.
“No problem,” I thought naively. “I’ll just call the helpline and get this sorted in ten minutes.”
Three hours later, I was seriously contemplating whether throwing the printer out the window would be more cost-effective than continuing this Kafkaesque nightmare of automated responses and scripted “solutions” that had absolutely nothing to do with my actual problem.
It started, as these things always do, with the robot.
“Please say in a few words why you’re calling today,” it chirped with artificial cheerfulness.
“Printer making horrible noise and flashing amber light,” I said clearly.
“I think you said you want to order ink. Is that right?”
No. No, it wasn’t right. Not even close. After three more attempts at being understood by this digital gatekeeper, I finally unlocked the secret code (“representative”) that connected me to a human being.
Or so I thought.
Martin introduced himself with the enthusiasm of someone who had already repeated the same greeting 437 times that day. Fair enough. Customer service is brutal. I launched into my description of the printer problem, feeling oddly proud of my technical specificity – the exact model, the precise nature of the noise (like a “whirring followed by a clunk”), the pattern of the flashing light.
And then it happened. The moment I realized Martin wasn’t really listening to me at all.
“I understand your frustration, sir. Let’s start by unplugging your printer, waiting 30 seconds, and plugging it back in.”
The script had begun.
Now, I’m not technically inept. Before calling, I’d already power-cycled the printer. Twice. I’d checked for paper jams. I’d cleaned the print heads. I’d performed every basic troubleshooting step listed in the manual and on the company’s website. I mentioned this to Martin.
“I understand your frustration, sir. Let’s start by unplugging your printer, waiting 30 seconds, and plugging it back in.”
Exactly the same words. Exactly the same intonation. It was as if he hadn’t heard me at all.
And so began my descent into tech support purgatory. For the next 45 minutes, Martin walked me through a series of steps that had absolutely nothing to do with the symptoms I was describing. We checked WiFi settings (for a printer connected via USB). We updated drivers (which I’d already done). We verified paper sizes (despite the fact that the printer wasn’t even attempting to print).
The most maddening part wasn’t just the irrelevance of the troubleshooting steps – it was the absolute refusal to acknowledge that the script wasn’t working. Each time a “solution” failed, Martin would simply move to the next item on his list without any recognition that perhaps we were barking up the wrong tree entirely.
“Let’s try cleaning the print heads,” he suggested after the 40-minute mark.
“I already did that before calling,” I reminded him, feeling my blood pressure climbing to dangerous levels.
“It’s best if we do it again following the exact procedure,” he insisted.
I bit my tongue and followed along, knowing full well this wouldn’t fix the horrible grinding noise that was clearly mechanical in nature. And of course, it didn’t.
My friend Sarah works in tech support for a major software company. Over drinks last month, she confessed the dirty secret of the industry: most first-tier support representatives are essentially script-readers with extremely limited authority to deviate from prescribed troubleshooting paths.
“We have these knowledge base articles that are basically flow charts,” she explained. “If customer says X, we do Y. If that doesn’t work, we try Z. Only after going through the entire script are we allowed to escalate to someone who might actually know what they’re doing.”
The economic logic is sound, I suppose. Most technical problems are indeed solved by basic troubleshooting steps. Why pay for expensive expertise when 80% of issues can be resolved by following a simple script? The problem is that if you’re in the 20% with a more complex issue – or worse, if you’ve already tried all the basic steps – you’re essentially forced to waste your time performing a ritualistic dance before you’re permitted to speak to someone who can actually help.
After nearly an hour with Martin, I finally uttered the magic words that seem to trigger the next level of support: “I’d like to speak to your supervisor.”
The line went quiet for a moment. “I understand your frustration, sir. Let me see if a senior technical advisor is available.”
Fifteen minutes of hold music later, Jasmine came on the line. Her first question gave me hope: “So I see you’re having an issue with unusual noises and a flashing amber light. Can you describe exactly what happens when the noise occurs?”
An actual question about my actual problem! I nearly wept with joy.
Within five minutes, Jasmine had identified the likely culprit – a gear mechanism that was known to fail in this particular model. Not something I could fix myself. Not something that turning it off and on again would resolve. A genuine mechanical failure that required repair or replacement.
“Why,” I asked as politely as my frayed nerves would allow, “couldn’t Martin have just told me this was a known issue with this model?”
“He probably didn’t have that information available in his troubleshooting script,” Jasmine admitted. “First-tier support follows a standard protocol regardless of the specific symptoms.”
And there it was – the fundamental flaw in modern technical support. The scripts aren’t designed to efficiently solve problems; they’re designed to efficiently process customers. The goal isn’t to fix your specific issue as quickly as possible; it’s to move through a predetermined sequence of steps that will eventually either solve the problem or exhaust your patience.
My colleague Terry had an even more absurd experience with his internet provider last year. His connection would drop precisely every 45 minutes, like clockwork. He tested different devices, different websites, different times of day – the pattern was consistent. When he called support, he was instructed to reboot his router (which he’d done dozens of times), check for software updates, and scan for viruses.
“But none of that explains why it happens at exactly 45-minute intervals,” he protested.
“Let’s just follow the troubleshooting steps, sir,” came the reply.
After three separate calls and probably six hours of his life he’ll never get back, Terry finally reached a network specialist who immediately recognized the issue: a timer misconfiguration in their system was forcing a connection reset at fixed intervals. Something no amount of rebooting on Terry’s end could possibly have fixed.
I sometimes wonder how many collective human hours are wasted each year on this theater of troubleshooting – customers pretending they haven’t already tried the basics, support representatives pretending their script might actually solve the problem. It’s a strange dance of mutual deception that benefits no one.
The most frustrating part is that many of us would happily skip straight to tier-two support and pay extra for the privilege. I’d have gladly handed over £20 to bypass Martin entirely and speak directly to Jasmine. But that option doesn’t exist in most support ecosystems.
My brother-in-law works in IT and says there’s actually an unofficial language you can use to signal to tech support that you’re not a novice. Phrases like “I’ve already verified layer one connectivity” or “I’ve checked the registry keys and found no corruption” can sometimes prompt support reps to deviate from their scripts. But even this is hit-or-miss, depending on whether the person on the other end is empowered to recognize and respond to such signals.
The irony is that as our technology becomes more complex, our support systems become more simplified and rigid. It’s like trying to perform surgery with a sledgehammer – a tool fundamentally unsuited to the nuance of the task.
After my printer ordeal, I did what any reasonable person would do: I vented on Twitter. The responses were both validating and depressing – dozens of people sharing similar experiences across every imaginable product category. The woman whose car’s infotainment system kept crashing, only to be told repeatedly to check her phone’s Bluetooth settings. The man whose specific prescription was constantly being rejected by his insurance company’s website, yet the support team insisted on walking him through how to clear his browser cache.
It’s enough to make you nostalgic for the days when products came with actual repair shops staffed by people who understood how they worked.
I did eventually get my printer fixed – or rather, replaced under warranty. But not before spending nearly four hours of my life engaged in troubleshooting theater. Four hours I’ll never get back. Four hours that could have been compressed into fifteen minutes if the support system had been designed to address actual problems rather than process customers through predetermined scripts.
Next time something breaks, I might just try shouting technical jargon at the automated system and see what happens. “Hard drive fragmentation causing exponential registry corruption during BIOS initialization!” Maybe that’ll confuse it enough to connect me directly to someone who can actually help.
Or maybe I’ll just throw the damn thing out the window and be done with it. Might be more cost-effective in the long run.
0 Comments