Roamans.com: I will never get anything else from your compan...
A Roamans.com customer review by GetHuman user GetHuman-305987 from November 20th, 2017
Background on GetHuman-305987's case
GetHuman: GetHuman-305987 - can you tell our other Roamans.com customers when your case took place?
GetHuman-305987: Yeah. It was evening, on November 17th.
GetHuman: Did you reach out to Roamans.com, and if so, how?
GetHuman: And which of these common Roamans.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-305987 a list of common Roamans.com problems)
GetHuman-305987: "Complaint" was why I was trying to call.
GetHuman-305987's review of Roamans.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Roamans.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-305987: I will never get anything else from your company. each month i have a late charge for a dress that is paid in full!!! i will send your * late charges and do not ever contact me by mail or e-mail again
GetHuman: Let's quantify your experience contacting Roamans.com. On a scale of 1 to 5, how easy is it go get help on a Roamans.com problem?
GetHuman-305987: 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?
GetHuman-305987: I'd give them a three out of five on communication.
GetHuman: And what about Roamans.com's ability to quickly and effectively address your problem?
GetHuman-305987: For that I would say four out of five.
GetHuman: And finally- any advice for other Roamans.com customers?
GetHuman-305987: Call them early in the day or late. Don't forget any personal or account information you might need for Roamans.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-305987 taken from his Roamans.com customer service problem that occurred on November 17th, 2017.