Comment

Comment on HP realizes that mandatory 15-minute support call wait times isn’t good support

Semi_Hemi_Demigod@lemmy.world ⁨10⁩ ⁨hours⁩ ago

Having run a couple support team, 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.

source

Sort:hotnew top

FauxPseudo@lemmy.world ⁨1⁩ ⁨minute⁩ ago
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.

source
SeductiveTortoise@piefed.social ⁨10⁩ ⁨hours⁩ ago
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.

source
- Semi_Hemi_Demigod@lemmy.world ⁨9⁩ ⁨hours⁩ ago
  Thankfully we didn’t take phone calls. And I knew they weren’t reading the KB because we’d reply with a link tot be KB and they’d be happy.
  
  source
  - SeductiveTortoise@piefed.social ⁨9⁩ ⁨hours⁩ ago
    Yes, but I mean how do you know people didn’t read it.
    
    But getting people to actually read the docs was impossible. And maybe if we made them wait they’d get frustrated
    
    You probably didn’t see the ones reading into it, just the ones that didn’t.
    
    source
    Semi_Hemi_Demigod@lemmy.world ⁨9⁩ ⁨hours⁩ ago
    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.
    
    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.)
    
    source
    -> View More Comments
WesternInfidels@feddit.online ⁨7⁩ ⁨hours⁩ ago
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 up 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 any sense of any documentation we could write. Some of them 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.

source