Handybook: I had to fight and threaten to speak poorly of...
A Handybook customer review by GetHuman user ~nycFreelance from November 28th, 2017
Background on ~nycFreelance's case
GetHuman: ~nycFreelance - can you tell our other Handybook customers when your case took place?
~nycFreelance: Yup. It was morning, on November 22nd.
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 ~nycFreelance a list of common Handybook problems)
~nycFreelance: "None of those really matches why I wanted to call Handybook that day." was why I was trying to call.
~nycFreelance'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.
~nycFreelance: I had to fight and threaten to speak poorly of their company and refuse payment on my credit card before the supervisor even tried to offer me a fair deal. Remains to be seen if I will actually get a refund.
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?
~nycFreelance: 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?
~nycFreelance: I'd give them a one out of five on communication.
GetHuman: And what about Handybook's ability to quickly and effectively address your problem?
~nycFreelance: For that I would say two out of five.
GetHuman: And finally- any advice for other Handybook customers?
~nycFreelance: 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 ~nycFreelance taken from his Handybook customer service problem that occurred on November 22nd, 2017.