Haband: I placed an order on Aug. **th. I received an e...
A Haband customer review by GetHuman user ~homer from November 6th, 2017
Background on ~homer's case
GetHuman: ~homer - can you tell our other Haband customers when your case took place?
~homer: Yeah. It was middle of the night, on October 30th.
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 ~homer a list of common Haband problems)
~homer: "Returns" was why I was trying to call.
~homer'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.
~homer: I placed an order on Aug. **th. I received an e-mail order confirmation. Until I checked my order tonight myself, I did not know that * of the * items were on backorder and one had been shipped. I received no notification of this at all from the company. Your order confirmation you sent me said you would notify me if anything shipped or backordered. I got nothing. Very poor service!!!
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?
~homer: 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?
~homer: 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?
~homer: For that I would say one out of five.
GetHuman: And finally- any advice for other Haband customers?
~homer: 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 ~homer taken from his Haband customer service problem that occurred on October 30th, 2017.