AshleyStewart.com: Sarah was very professional, helpful and quick...
A AshleyStewart.com customer review by GetHuman user GetHuman-426855 from November 20th, 2017
Background on GetHuman-426855's case
GetHuman: GetHuman-426855 - can you tell our other AshleyStewart.com customers when your case took place?
GetHuman-426855: Yes I can. It was evening, on November 18th.
GetHuman: Did you reach out to AshleyStewart.com, and if so, how?
GetHuman: And which of these common AshleyStewart.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-426855 a list of common AshleyStewart.com problems)
GetHuman-426855: "Returns" was why I was trying to call.
GetHuman-426855's review of AshleyStewart.com customer service
GetHuman: So how would you sum up your experience for GetHuman's AshleyStewart.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-426855: Sarah was very professional, helpful and quick to find the information I requested. I am most pleased with the outcome.
GetHuman: Let's quantify your experience contacting AshleyStewart.com. On a scale of 1 to 5, how easy is it go get help on a AshleyStewart.com problem?
GetHuman-426855: 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-426855: I'd give them a three out of five on communication.
GetHuman: And what about AshleyStewart.com's ability to quickly and effectively address your problem?
GetHuman-426855: For that I would say one out of five.
GetHuman: And finally- any advice for other AshleyStewart.com customers?
GetHuman-426855: Call them early in the day or late. Don't forget any personal or account information you might need for AshleyStewart.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-426855 taken from his AshleyStewart.com customer service problem that occurred on November 18th, 2017.