I scheduled an order in CA for something to be delivered to a friend in TX. I put the...

GetHuman1038506's customer service issue with UberEATS from August 2018

3 views
 | 
14828 similar
 | 
0 following
Help with my UberEATS issue
First: share to improve GetHuman1038506's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman1038506's next move: talk to UberEATS when they open.
UberEATS's call center is closed now. We will send GetHuman1038506 a reminder to call them when they open. Nothing to do for now but wait!
The issue in GetHuman1038506's own words
I scheduled an order in CA for something to be delivered to a friend in TX. I put the time it should have been delivered in TX time zone, but it arrived * hours later in my time zone to the address in TX. It would be helpful to know that when ordering. UberEATS is a wonderful way to help support friends and family when you can't be there to make a meal in times of need because you are in a different state.
GetHuman1038506 did not yet indicate what UberEATS should do to make this right.
I have an issue with UberEATS too
How GetHuman1038506 fixed the problem
We are waiting for GetHuman1038506 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 GetHuman1038506 fixes it.
This email address isn't valid

UberEATS

Customer service issue
Reported by GetHuman1038506
Aug 26th, 2018 - 4 mons ago
I have an issue with UberEATS too
Not resolved
Seen by 3 customers so far
Similar issue to 14828 others
0 customers following this
Follow this issue to see how it gets fixed
Items needed
Name
Email address
Phone number
Timeline
GetHuman1038506 started working on this issue
Aug 26th 3:59pm