Received following message by email. I have received Amazon shipments quite often for...

GetHuman5879441's customer service issue with Amazon Local from March 2021

Help with my Amazon Local issue
First: share to improve GetHuman5879441's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman5879441 may need:
Name on the account, Billing address, and Email address on the account
The issue in GetHuman5879441's own words
Received following message by email. I have received Amazon shipments quite often for years, so I cannot understand why this one should be any different. I responded to a questionnaire as to the exact location to deliver at my home. This is so dumb that I thought it was a phishing message. **Hi Joseph, *Unfortunately, we ran into an issue when attempting your delivery. We will try again. *Please add or update delivery instructions, if you have any information that may help drivers complete deliveries to this address. **Track your delivery * *Order * ***-*******-*******.

GetHuman5879441 did not yet indicate what Amazon Local should do to make this right.

How GetHuman5879441 fixed the problem

We are waiting for GetHuman5879441 to fix the problem and share the solution with the rest of us customers.

Find similar issues & fixes
Follow other customers in the midst of the same issue or find a prior solution.
Kab milega my delevar safran idemia safran morpho contacts nom dijaMera mobile mujhe nahi mila h aur meri kist kat chuki h
Do you have a customer issue as well?
We can help you get Amazon Local's attention and get better help faster. Tap below to get started.
Having Amazon Local issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid

Amazon Local

Customer service issue
Reported by GetHuman5879441
Mar 23rd, 2021 - 2 months ago
Not resolved
Seen by 9 customers so far
Similar issue to 241 others
0 customers following this


GetHuman5879441 started working on this issue
Mar 23rd 6:54pm