- cross-posted to:
- nottheonion@lemmy.world
- cross-posted to:
- nottheonion@lemmy.world
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
I can guarantee making them wait won’t make them read if that wasn’t their first choice to begin with. All you’re doing is making them angrier for when they finally do get connected to a person.
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.
How could you tell that people were not reading the knowledge base? They probably didn’t need to call if they did, so maybe you reduced the volume by 50%. I get what you are trying to say, but if they make me wait 15 minutes just because, I’m going to be pissed once I reach someone. Then the person who doesn’t deserve my bad temper will feel it and I will never buy hardware from you again.
And I’m saying that despite having worked at customer support for years, writing knowledge-base entries and developing the system we used to store it.
Thankfully we didn’t take phone calls. And I knew they weren’t reading the KB because we’d reply with a link to the KB and they’d be happy.
Yes, but I mean how do you know people didn’t read it.
You probably didn’t see the ones reading into it, just the ones that didn’t.
The only time the KB really saved was being able to send them a link to the docs that they should have been able to find instead of retyping the response. Which is good because time to first response kept going down as we wrote more articles.
All of the answers were right there and they didn’t see it. And no matter how many articles we added the volume of tickets resolved on the first reply with a KB article didn’t go down. (I know because I tracked this as a KPI for a while until it became obvious it wasn’t budging.)
My only conclusion from this is that there is a segment of people who will always ask someone for help rather than take initiative.
What he is saying is, while a lot of the phone calls you got were answered with the KB, this doesn’t reflect the people who didn’t call because they used the KB. For that, you would need to track total sales, new customer intake, volume over time, etc. It’s quite possible you could have customers who got a KB reply from your support staff in a timely manner and decided if it was that easy for you to get an answer to them, it would be worth it for them to try it before calling next time.
Of course, the reality is quite likely that the main users of the knowledge base you built was the support team, which still isn’t a loss.
Oh, totally. Having a KB full of ready made answers reduced response times and increased customer satistfaction
Thanks 💖
I was too tired to come back yesterday.
I spent a couple of years doing phone support (for a Windows program, in the internet-by-modem days), and we had a paper manual that we spent a lot of effort on. I’m not sure it helped too many people. We didn’t have a way of measuring, though. We had no idea how many people were blundering through things on their own, how many people set things up on their own with the manual’s help, or how many people were chucking the whole product in a closet and forgetting about it.
Sure, some callers definitely felt it was a waste of time to learn how to work things; they just wanted their things to work. They wanted their things to serve them, instead of the other way around, and I can’t even argue with that philosophy.
But most callers just didn’t have the technical experience to make sense of any documentation we could write. Some didn’t know what the desktop computer they used every day even looked like, didn’t know which of the metal-and-plastic boxes around their desk was “the computer.” They didn’t know the difference between a floppy drive and a hard drive, and they’d argue with us about it. “I don’t have a floppy drive, my drive takes those hard disks.” No manual or knowledge base article was going to help these folks, no matter how much effort we made.
I’m currently struggling with a product that I’d love to use the knowledge base for help but they keep changing their goddamn gui every version so the knowledge base docs never apply to me. “Click on files->database->security”, uhhh, there is no “security” under “database” you mother f’ers…