EDIT: This happened back in 2025. Will leave as I’m sure I’m not the only one that didn’t know, but I saw it on hacker news and didn’t realize it was a year old. My bad.
In an odd approach to trying to improve customer tech support, HP allegedly implemented mandatory, 15-minute wait times for people calling the vendor for help with their computers and printers in certain geographies.
Callers from the United Kingdom, France, Germany, Ireland, and Italy were met with the forced holding periods, The Register reported on Thursday. The publication cited internal communications it saw from February 18 that reportedly said the wait times aimed to “influence customers to increase their adoption of digital self-solve, as a faster way to address their support question. This involves inserting a message of high call volumes, to expect a delay in connecting to an agent and offering digital self-solve solutions as an alternative.”
Having run a couple support teams, I get where they’re coming from with the wait time.
Every minute my team wasn’t spending helping customers was spent updating the knowledge base. We invested a ton of effort into it, and 90% of the tickets were answerable in the first interaction with a simple search.
But getting people to actually read the docs was impossible. And maybe if we made them wait they’d get frustrated
But that’s not very nice to your customers or the agents.
My very first desk job was an outsourced support role where 99% of calls we simply found the answer in the user manual and provided that to them. The other 1% was usually something isoteric we’d forward on to someone within the company. The amount of callers who’d say “I’ve read the user manual cover to cover and I just can’t figure out how to…” And I’d just try to page 12 on the PDF and read them the instructions word for word
At the scale of HP, I can see the logic. You know that, say 60% of calls are directly covered by the knowledge base because you have those metrics. That’s means 60% of their support overhead could be eliminated if they somehow got people to read those documents. Hardware sales usually have very thin margins and a customer contacting support can easily cost more in support than the entire profit margin of the product (and often it’s a self-inflicted problem) and of course an RMA for most products basically negates all profit from that sale. It’s a real business challenge and the asshole solution is to simply tie people up for 15 minutes in the phone system before connecting to a human to see how many people hang up and how much that reduces support load
When I started at one company I put together a text file with all the different sources of info I found in training. By the end of training I had turned it into an HTML file. Years later we got bought out. Support from corporate disappeared on legacy customs who hadn’t moved over to new stuff.
A coworker tapped me on the shoulder “If I were to make a local network web server on one of these computers could I upload your help system to it for everyone to use?”
Next thing you know I’m the default source for all information on every system that has ever existed. Prior to that everyone knew that I had it all in my brain but only a handful of people knew that I also had it all in HTML.
TL;DR I built a pirate help desk knowledge base.