On ******** @ *:** pm I placed Order ***E** for Boston market (**** W. Brandon Blvd Tam...

GetHuman1906566's customer service issue with UberEATS from January 2019

Help with my UberEATS issue
The issue in GetHuman1906566's own words
On ******** @ *:** pm I placed Order ***E** for Boston market (**** W. Brandon Blvd Tampa FL) . The total was $**.***As soon as i placed the order, I went back to add an item to the order. It gave me a new Order ****** and the new total was $**.**.*The past orders on the UberEATS app is showing that i am being charged $**.** for cancelling the *st order * **E**. I only added items to the order.*PLEASE DO NOT charge me $**.** for changing my order or REMOVE the $**.** if my credit card ending in **** has already been charged as this is my Company credit card and this will cause issues for me*Can someone contact me to confirm this has been corrected (***)***-****. I called the customer service number and she took my information and placed me on hold then the line went dead.
GetHuman1906566 did not yet indicate what UberEATS should do to make this right.
I have an issue with UberEATS too
How GetHuman1906566 fixed the problem
I contacted UberEars customer service about the issue. They called the restaurant to verify that the *st order was not prepared and refunded the charge back to my credit card and I was satisfied with the quick follow-up to this issue.
Please help with my UberEATS issue
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


Customer service issue
Reported by GetHuman1906566
Jan 6th, 2019 - 4 mons ago
I have an issue with UberEATS too
Seen by 2 customers so far
Similar issue to 42767 others
0 customers following this
Items needed
Email address
Phone number
GetHuman1906566 started working on this issue
Jan 6th 1:01am
GetHuman1906566 confirmed the issue is fixed. Hooray!
Jan 6th 5:03pm