Maidenform.com: I spent all my breaks from work trying to canta...
A Maidenform.com customer review by GetHuman user GetHuman-324721 from November 8th, 2017
Background on GetHuman-324721's case
GetHuman: GetHuman-324721 - can you tell our other Maidenform.com customers when your case took place?
GetHuman-324721: Sure. It was evening, on October 30th.
GetHuman: Did you reach out to Maidenform.com, and if so, how?
GetHuman: And which of these common Maidenform.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-324721 a list of common Maidenform.com problems)
GetHuman-324721: "Complaint" was why I was trying to call.
GetHuman-324721's review of Maidenform.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Maidenform.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.
GetHuman-324721: I spent all my breaks from work trying to cantact someone there and I got no results. Also I left voice messages and sent e-mails, no re-ply whatsoever.
GetHuman: Let's quantify your experience contacting Maidenform.com. On a scale of 1 to 5, how easy is it go get help on a Maidenform.com problem?
GetHuman-324721: 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-324721: I'd give them a two out of five on communication.
GetHuman: And what about Maidenform.com's ability to quickly and effectively address your problem?
GetHuman-324721: For that I would say one out of five.
GetHuman: And finally- any advice for other Maidenform.com customers?
GetHuman-324721: Call them early in the day or late. Don't forget any personal or account information you might need for Maidenform.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-324721 taken from his Maidenform.com customer service problem that occurred on October 30th, 2017.