Kleargear.com: Could not contact anyone by phone or email. Thi...
A Kleargear.com customer review by GetHuman user ~Bill Henderson from November 19th, 2017
Background on ~Bill Henderson's case
GetHuman: ~Bill Henderson - can you tell our other Kleargear.com customers when your case took place?
~Bill Henderson: Yes I can. It was afternoon, on November 9th.
GetHuman: Did you reach out to Kleargear.com, and if so, how?
GetHuman: And which of these common Kleargear.com customer issues best describes the reason you wanted to talk to them?
(Shows ~Bill Henderson a list of common Kleargear.com problems)
~Bill Henderson: "Track order" was why I was trying to call.
~Bill Henderson's review of Kleargear.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Kleargear.com 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.
~Bill Henderson: Could not contact anyone by phone or email. This company doesn't give a **** about it's customers. They take your money and don't deliver the products you ordered
GetHuman: Let's quantify your experience contacting Kleargear.com. On a scale of 1 to 5, how easy is it go get help on a Kleargear.com problem?
~Bill Henderson: 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?
~Bill Henderson: I'd give them a three out of five on communication.
GetHuman: And what about Kleargear.com's ability to quickly and effectively address your problem?
~Bill Henderson: For that I would say four out of five.
GetHuman: And finally- any advice for other Kleargear.com customers?
~Bill Henderson: Call them early in the day or late. Don't forget any personal or account information you might need for Kleargear.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Bill Henderson taken from his Kleargear.com customer service problem that occurred on November 9th, 2017.