Amazon: Felt like I was speaking with a computer due to...
A Amazon customer review by GetHuman user ~tippytoes0125 from November 2nd, 2017
Background on ~tippytoes0125's case
GetHuman: ~tippytoes0125 - can you tell our other Amazon customers when your case took place?
~tippytoes0125: Yes I can. It was afternoon, on October 23rd.
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 ~tippytoes0125 a list of common Amazon problems)
~tippytoes0125: "Track order" was why I was trying to call.
~tippytoes0125'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.
~tippytoes0125: Felt like I was speaking with a computer due to weird phone connection, and it took a bit on the phone to only somewhat fix a pretty big problem, but it was better than waiting for an e-mail response since I'm going to be away from home (and computer access) for a few days.
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?
~tippytoes0125: 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?
~tippytoes0125: I'd give them a five out of five on communication.
GetHuman: And what about Amazon's ability to quickly and effectively address your problem?
~tippytoes0125: For that I would say four out of five.
GetHuman: And finally- any advice for other Amazon customers?
~tippytoes0125: 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 ~tippytoes0125 taken from his Amazon customer service problem that occurred on October 23rd, 2017.