Ashley Furniture: The woman I spoke to was very nice and helpful...
A Ashley Furniture customer review by GetHuman user ~cdubbs from November 9th, 2017
Background on ~cdubbs's case
GetHuman: ~cdubbs - can you tell our other Ashley Furniture customers when your case took place?
~cdubbs: Yeah. It was morning, on October 30th.
GetHuman: Did you reach out to Ashley Furniture, and if so, how?
GetHuman: And which of these common Ashley Furniture customer issues best describes the reason you wanted to talk to them?
(Shows ~cdubbs a list of common Ashley Furniture problems)
~cdubbs: "Overcharge/Strange charge" was why I was trying to call.
~cdubbs's review of Ashley Furniture customer service
GetHuman: So how would you sum up your experience for GetHuman's Ashley 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.
~cdubbs: The woman I spoke to was very nice and helpful. I wish i could say the same for Ashley Furniture store customer service in Duluth, GA. They were rude and I would NEVER purchase Ashley furniture again based on * experiences there.
GetHuman: Let's quantify your experience contacting Ashley Furniture. On a scale of 1 to 5, how easy is it go get help on a Ashley Furniture problem?
~cdubbs: 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?
~cdubbs: I'd give them a one out of five on communication.
GetHuman: And what about Ashley Furniture's ability to quickly and effectively address your problem?
~cdubbs: For that I would say five out of five.
GetHuman: And finally- any advice for other Ashley Furniture customers?
~cdubbs: Call them early in the day or late. Don't forget any personal or account information you might need for Ashley Furniture to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~cdubbs taken from his Ashley Furniture customer service problem that occurred on October 30th, 2017.