Haband: This number did the trick (*-***-***-**** ext...
A Haband customer review by GetHuman user GetHuman-199974 from November 10th, 2017
Background on GetHuman-199974's case
GetHuman: GetHuman-199974 - can you tell our other Haband customers when your case took place?
GetHuman-199974: Yes. It was middle of the night, on November 7th.
GetHuman: Did you reach out to Haband, and if so, how?
GetHuman: And which of these common Haband customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-199974 a list of common Haband problems)
GetHuman-199974: "Cancel order" was why I was trying to call.
GetHuman-199974's review of Haband customer service
GetHuman: So how would you sum up your experience for GetHuman's Haband 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-199974: This number did the trick (*-***-***-**** ext.*)! After trying numbers that only got me an autimated system that would just let you order or check on you order*account, I finally got a person to remove my account from the mailing list. Thank you gethuman.com!
GetHuman: Let's quantify your experience contacting Haband. On a scale of 1 to 5, how easy is it go get help on a Haband problem?
GetHuman-199974: I'd give them a one 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-199974: I'd give them a one out of five on communication.
GetHuman: And what about Haband's ability to quickly and effectively address your problem?
GetHuman-199974: For that I would say five out of five.
GetHuman: And finally- any advice for other Haband customers?
GetHuman-199974: Call them early in the day or late. Don't forget any personal or account information you might need for Haband to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-199974 taken from his Haband customer service problem that occurred on November 7th, 2017.