Amazon: My issue with my non-functioning Kindle was NOT...
A Amazon customer review by GetHuman user GetHuman-403510 from November 22nd, 2017
Background on GetHuman-403510's case
GetHuman: GetHuman-403510 - can you tell our other Amazon customers when your case took place?
GetHuman-403510: Yes I can. It was afternoon, 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 GetHuman-403510 a list of common Amazon problems)
GetHuman-403510: "Complaint" was why I was trying to call.
GetHuman-403510'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.
GetHuman-403510: My issue with my non-functioning Kindle was NOT esolved to my satisfaction whatsoever. This was the second time I have had to be shifted from one to another operator. I am completely UNIMPRESSED with Amazon and Kindle's so called fabulous customer service. *****@***.com
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?
GetHuman-403510: I'd give them a five 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-403510: I'd give them a four out of five on communication.
GetHuman: And what about Amazon's ability to quickly and effectively address your problem?
GetHuman-403510: For that I would say three out of five.
GetHuman: And finally- any advice for other Amazon customers?
GetHuman-403510: 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 GetHuman-403510 taken from his Amazon customer service problem that occurred on November 13th, 2017.