Avon Products, Inc.: Ben was knowledgeable, helpful and pleasant. Ve...
A Avon Products, Inc. customer review by GetHuman user GetHuman-20238 from November 27th, 2017
Background on GetHuman-20238's case
GetHuman: GetHuman-20238 - can you tell our other Avon Products, Inc. customers when your case took place?
GetHuman-20238: Yup. It was afternoon, on November 17th.
GetHuman: Did you reach out to Avon Products, Inc., and if so, how?
GetHuman: And which of these common Avon Products, Inc. customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-20238 a list of common Avon Products, Inc. problems)
GetHuman-20238: "Cancel order" was why I was trying to call.
GetHuman-20238's review of Avon Products, Inc. customer service
GetHuman: So how would you sum up your experience for GetHuman's Avon Products, Inc. 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-20238: Ben was knowledgeable, helpful and pleasant. Very positive CS experience. He's a keeper. Thank you Ben.
GetHuman: Let's quantify your experience contacting Avon Products, Inc.. On a scale of 1 to 5, how easy is it go get help on a Avon Products, Inc. problem?
GetHuman-20238: I'd give them a three 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-20238: I'd give them a four out of five on communication.
GetHuman: And what about Avon Products, Inc.'s ability to quickly and effectively address your problem?
GetHuman-20238: For that I would say five out of five.
GetHuman: And finally- any advice for other Avon Products, Inc. customers?
GetHuman-20238: Call them early in the day or late. Don't forget any personal or account information you might need for Avon Products, Inc. to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-20238 taken from his Avon Products, Inc. customer service problem that occurred on November 17th, 2017.