Amazon: Great service . However, I was charged on my Ma...
Amazon Ulasan pelanggan oleh pengguna GetHuman ~Ray dari November 26, 2017
Background on ~Ray's case
GetHuman: ~Ray - can you tell our other Amazon customers when your case took place?
~Ray: Sure. It was middle of the night, on November 17.
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 ~Ray a list of common Amazon problems)
~Ray: "Update account information" was why I was trying to call.
~Ray'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.
~Ray: Great service . However, I was charged on my MasterCard for two customer service calls last month! *-***-***-**** showed up twice on my credit card statement. It was followed by uppercase WA, followed by $*.** for each call. At no time was I told that I would be charged by Amazon for any customer service calls about my new Kindle Fire HDX or Fire Keyboard. I was outraged.
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?
~Ray: 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?
~Ray: 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?
~Ray: For that I would say three out of five.
GetHuman: And finally- any advice for other Amazon customers?
~Ray: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Amazon mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~Ray taken from his Amazon customer service problem that occurred on November 17, 2017.