I used the “use my location” button and proceeded to order food. Once I had placed the...

GetHuman1332627's customer service issue with UberEATS from October 2018

2 views
 | 
23898 similar
 | 
0 following
Help with my UberEATS issue
First: share to improve GetHuman1332627's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman1332627's next move: call UberEATS.
The best way to get your problem resolved is to tap the button below to start calling UberEATS. We will check on you later to see if it's fixed or needs to be escalated.
Before contacting them, items GetHuman1332627 may need:
Name, Email address, and Phone number
The issue in GetHuman1332627's own words
I used the “use my location” button and proceeded to order food. Once I had placed the order and was looking at the route I noticed that it had my location at an incorrect address (several blocks away) I canceled the order and typed in my location and made the order again. I was charged for both orders, I would like a refund for the first.
GetHuman1332627 did not yet indicate what UberEATS should do to make this right.
I have an issue with UberEATS too
How GetHuman1332627 fixed the problem
We are waiting for GetHuman1332627 to fix the problem and share the solution with the rest of us customers.
Follow this to see how it gets fixed
Do you have a customer issue as well?
We can help you get UberEATS's attention and get better help faster. Tap below to get started.
Having UberEATS issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would UberEATS email you?
This email address isn't valid
Follow this issue
See how GetHuman1332627 fixes it.
This email address isn't valid

UberEATS

Customer service issue
Reported by GetHuman1332627
Oct 12th, 2018 - 10d ago
I have an issue with UberEATS too
Not resolved
Seen by 2 customers so far
Similar issue to 23898 others
0 customers following this
Follow this issue to see how it gets fixed
Timeline
GetHuman1332627 started working on this issue
Oct 12th 3:29pm