Amazon: I could not understand what the representive wa...
A Amazon customer review by GetHuman user ~Linda McPherson from November 19th, 2017
Background on ~Linda McPherson's case
GetHuman: ~Linda McPherson - can you tell our other Amazon customers when your case took place?
~Linda McPherson: Yup. It was morning, on November 13th.
GetHuman: Did you reach out to Amazon, and if so, how?
GetHuman: And which of these common Amazon customer issues best describes the reason you wanted to talk to them?
(Shows ~Linda McPherson a list of common Amazon problems)
~Linda McPherson: "Dispute a Charge" was why I was trying to call.
~Linda McPherson's review of Amazon customer service
GetHuman: So how would you sum up your experience for GetHuman's Amazon 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.
~Linda McPherson: I could not understand what the representive was saying, she did not understand me either. It was tortuous and wasted at least ** or more minutes of my time. She was pleasant and nice and tried her best, but the language barrier was impossible.
GetHuman: Let's quantify your experience contacting Amazon. On a scale of 1 to 5, how easy is it go get help on a Amazon problem?
~Linda McPherson: 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?
~Linda McPherson: I'd give them a two out of five on communication.
GetHuman: And what about Amazon's ability to quickly and effectively address your problem?
~Linda McPherson: For that I would say five out of five.
GetHuman: And finally- any advice for other Amazon customers?
~Linda McPherson: Call them early in the day or late. Don't forget any personal or account information you might need for Amazon to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Linda McPherson taken from his Amazon customer service problem that occurred on November 13th, 2017.