Marlo Furniture: Do not buy furniture from Marlo's Furniture, *B...
A Marlo Furniture customer review by GetHuman user GetHuman-429652 from November 18th, 2017
Background on GetHuman-429652's case
GetHuman: GetHuman-429652 - can you tell our other Marlo Furniture customers when your case took place?
GetHuman-429652: Yeah. It was morning, on November 14th.
GetHuman: Did you reach out to Marlo Furniture, and if so, how?
GetHuman: And which of these common Marlo Furniture customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-429652 a list of common Marlo Furniture problems)
GetHuman-429652: "Complaint" was why I was trying to call.
GetHuman-429652's review of Marlo Furniture customer service
GetHuman: So how would you sum up your experience for GetHuman's Marlo Furniture 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-429652: Do not buy furniture from Marlo's Furniture, *Bad experience for me, I would not recommend that to anyone. *Atrocious customer service.........!
GetHuman: Let's quantify your experience contacting Marlo Furniture. On a scale of 1 to 5, how easy is it go get help on a Marlo Furniture problem?
GetHuman-429652: 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-429652: I'd give them a one out of five on communication.
GetHuman: And what about Marlo Furniture's ability to quickly and effectively address your problem?
GetHuman-429652: For that I would say four out of five.
GetHuman: And finally- any advice for other Marlo Furniture customers?
GetHuman-429652: Call them early in the day or late. Don't forget any personal or account information you might need for Marlo Furniture to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-429652 taken from his Marlo Furniture customer service problem that occurred on November 14th, 2017.