I placed my very first order ever because I has a $** dollar credit as a gift. I though...

GetHuman-lidakle's Problem With an Order issue with UberEATS from May 2020

Help with my UberEATS issue
The issue in GetHuman-lidakle's own words
I placed my very first order ever because I has a $** dollar credit as a gift. I thought it might be nice to try. Boy was I wrong! I placed the order the first time and ended up being taken to a screen that didn’t go anywhere. Had to close it and start again. I place the order for the second time and when I’m at the review screen, I see the $** credit and the full sum total of my bill. Great. I place the order and still see that the full amount is going to be charged to my card. I cancel the order. I order the third time and the credit is gone. My husband attempted to figure it out a few more times with no luck. Nowhere on the bill did it show the credit being used. So where did it go? We tried to re-enter the code buy as I suspected, it said it was already applied. Of course. I have to say, this was by far the worst And most frustrating experience I’ve had with an app in years! I would like the credit back. Thank you.

GetHuman-lidakle did not yet indicate what UberEATS should do to make this right.

How GetHuman-lidakle fixed the problem
I called them out in Twitter with *ubereatssucks and *garbagecompany and they responded immediately.
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
This email address isn't valid


Problem With an Order issue
Reported by GetHuman-lidakle
May 21st, 2020 - 3 years ago
GetHuman-lidakle shared how to fix
Seen by 8 customers so far
Similar issue to 30580 others
0 customers following this
Items needed
Email address
Phone number


GetHuman-lidakle started working on this issue
May 21st, 2020 10:44pm
GetHuman-lidakle confirmed the issue is fixed. Hooray!
May 24th, 2020 11:39am