Amiclubwear.com: After trying on a prior day and being caller...
A Amiclubwear.com customer review by GetHuman user ~Anonymous from November 13th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Amiclubwear.com customers when your case took place?
~Anonymous: Sure. It was afternoon, on November 12th.
GetHuman: Did you reach out to Amiclubwear.com, and if so, how?
GetHuman: And which of these common Amiclubwear.com customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Amiclubwear.com problems)
~Anonymous: "Change order" was why I was trying to call.
~Anonymous's review of Amiclubwear.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Amiclubwear.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.
~Anonymous: After trying on a prior day and being caller **, I called again and waited to get through. Don't order through this site unless you're absolutely sure that you won't need to return it or change your order.
GetHuman: Let's quantify your experience contacting Amiclubwear.com. On a scale of 1 to 5, how easy is it go get help on a Amiclubwear.com problem?
~Anonymous: 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?
~Anonymous: I'd give them a four out of five on communication.
GetHuman: And what about Amiclubwear.com's ability to quickly and effectively address your problem?
~Anonymous: For that I would say three out of five.
GetHuman: And finally- any advice for other Amiclubwear.com customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Amiclubwear.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Amiclubwear.com customer service problem that occurred on November 12th, 2017.