HP: After quick answer, I spent nearly ** minutes h...
A HP customer review by GetHuman user ~Bampy from November 19th, 2017
Background on ~Bampy's case
GetHuman: ~Bampy - can you tell our other HP customers when your case took place?
~Bampy: Sure. It was evening, on November 9th.
GetHuman: Did you reach out to HP, and if so, how?
GetHuman: And which of these common HP customer issues best describes the reason you wanted to talk to them?
(Shows ~Bampy a list of common HP problems)
~Bampy: "Technical support" was why I was trying to call.
~Bampy's review of HP customer service
GetHuman: So how would you sum up your experience for GetHuman's HP customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~Bampy: After quick answer, I spent nearly ** minutes holding and being transferred. USB pass-through ports are not working on my new HP monitor. This required help from the "Workstation" team. Finally talked to "David" (an American) who was polite and VERY helpful. He gave me a callback number: ***-***-****. He said if I then asked for "Z series running Microsoft," I'd get to the right help person. I'm retired, happily running a Mac Pro at my home.
GetHuman: Let's quantify your experience contacting HP. On a scale of 1 to 5, how easy is it go get help on a HP problem?
~Bampy: I'd give them a two out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~Bampy: I'd give them a five out of five on communication.
GetHuman: And what about HP's ability to quickly and effectively address your problem?
~Bampy: For that I would say two out of five.
GetHuman: And finally- any advice for other HP customers?
~Bampy: Call them early in the day or late. Don't forget any personal or account information you might need for HP to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Bampy taken from his HP customer service problem that occurred on November 9th, 2017.