this post was submitted on 20 Mar 2026
194 points (97.5% liked)

Technology

82834 readers
4082 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
194
HP realizes that mandatory 15-minute support call wait times isn’t good support (arstechnica.com)
submitted 4 hours ago* (last edited 3 hours ago) by criss_cross@lemmy.world to c/technology@lemmy.world
21 comments fedilink hide all child comments
 

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.”

you are viewing a single comment's thread
view the rest of the comments
[–] Semi_Hemi_Demigod@lemmy.world 25 points 3 hours ago* (last edited 2 hours ago) (1 children)

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.

[–] SeductiveTortoise@piefed.social 7 points 2 hours ago (1 children)

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.

[–] Semi_Hemi_Demigod@lemmy.world 4 points 2 hours ago* (last edited 2 hours ago) (1 children)

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.

[–] SeductiveTortoise@piefed.social 3 points 2 hours ago (1 children)

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.

[–] Semi_Hemi_Demigod@lemmy.world 2 points 1 hour ago* (last edited 1 hour 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. 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.