Handybook: Easy resolution. Unfortunately, I was extremely...
A Handybook customer review by GetHuman user GetHuman-434853 from November 27th, 2017
Background on GetHuman-434853's case
GetHuman: GetHuman-434853 - can you tell our other Handybook customers when your case took place?
GetHuman-434853: Yup. It was middle of the night, on November 20th.
GetHuman: Did you reach out to Handybook, and if so, how?
GetHuman: And which of these common Handybook customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-434853 a list of common Handybook problems)
GetHuman-434853: "None of those really matches why I wanted to call Handybook that day." was why I was trying to call.
GetHuman-434853's review of Handybook customer service
GetHuman: So how would you sum up your experience for GetHuman's Handybook 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-434853: Easy resolution. Unfortunately, I was extremely frustrated after not being able to find a solution to my problem online and having to google a number.
GetHuman: Let's quantify your experience contacting Handybook. On a scale of 1 to 5, how easy is it go get help on a Handybook problem?
GetHuman-434853: 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-434853: I'd give them a four out of five on communication.
GetHuman: And what about Handybook's ability to quickly and effectively address your problem?
GetHuman-434853: For that I would say three out of five.
GetHuman: And finally- any advice for other Handybook customers?
GetHuman-434853: Call them early in the day or late. Don't forget any personal or account information you might need for Handybook to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-434853 taken from his Handybook customer service problem that occurred on November 20th, 2017.