Amazon Local: Second time that a voucher was purchased and se...
A Amazon Local customer review by GetHuman user ~sbaldwin7@verizon.net from November 27th, 2017
Background on ~sbaldwin7@verizon.net's case
GetHuman: ~sbaldwin7@verizon.net - can you tell our other Amazon Local customers when your case took place?
~sbaldwin7@verizon.net: Yup. It was afternoon, on November 21st.
GetHuman: Did you reach out to Amazon Local, and if so, how?
GetHuman: And which of these common Amazon Local customer issues best describes the reason you wanted to talk to them?
(Shows ~sbaldwin7@verizon.net a list of common Amazon Local problems)
~sbaldwin7@verizon.net: "Overcharge on Account" was why I was trying to contact.
~sbaldwin7@verizon.net's review of Amazon Local customer service
GetHuman: So how would you sum up your experience for GetHuman's Amazon Local 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.
~sbaldwin7@verizon.net: Second time that a voucher was purchased and second time the vendor will not honor.*Bait and switch?*Amazon local is dragging down Amazons great name.
GetHuman: Let's quantify your experience contacting Amazon Local. On a scale of 1 to 5, how easy is it go get help on a Amazon Local problem?
~sbaldwin7@verizon.net: 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?
~sbaldwin7@verizon.net: I'd give them a five out of five on communication.
GetHuman: And what about Amazon Local's ability to quickly and effectively address your problem?
~sbaldwin7@verizon.net: For that I would say three out of five.
GetHuman: And finally- any advice for other Amazon Local customers?
~sbaldwin7@verizon.net: Call them early in the day or late. Don't forget any personal or account information you might need for Amazon Local to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~sbaldwin7@verizon.net taken from his Amazon Local customer service problem that occurred on November 21st, 2017.