HP: Your customer service is horrible, it took almo...
A HP customer review by GetHuman user GetHuman-348917 from November 26th, 2017
Background on GetHuman-348917's case
GetHuman: GetHuman-348917 - can you tell our other HP customers when your case took place?
GetHuman-348917: Yeah. It was middle of the night, on November 25th.
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 GetHuman-348917 a list of common HP problems)
GetHuman-348917: "Device Support" was why I was trying to call.
GetHuman-348917'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.
GetHuman-348917: Your customer service is horrible, it took almost an hour just to get to the correct dept, after being transferred and call dropped twice, who running this company? My dog gives better service. I purchased your warranty, I know this was a big mistake because I have to deal with your incompetent staff for a year!
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?
GetHuman-348917: I'd give them a five 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?
GetHuman-348917: 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?
GetHuman-348917: For that I would say five out of five.
GetHuman: And finally- any advice for other HP customers?
GetHuman-348917: 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 GetHuman-348917 taken from his HP customer service problem that occurred on November 25th, 2017.