Uber EATS: Took money out my account
A Uber EATS customer review by GetHuman user GetHuman-dnlldych from December 5th, 2017
Background on GetHuman-dnlldych's case
GetHuman: GetHuman-dnlldych - can you tell our other Uber EATS customers when your case took place?
GetHuman-dnlldych: Yes. It was middle of the night, on December 2nd.
GetHuman: Did you reach out to Uber EATS, and if so, how?
GetHuman: And which of these common Uber EATS customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-dnlldych a list of common Uber EATS problems)
GetHuman-dnlldych: "Problem With an Order" was why I was trying to call.
GetHuman-dnlldych's review of Uber EATS customer service
GetHuman: So how would you sum up your experience for GetHuman's Uber EATS customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
GetHuman-dnlldych: Took money out my account
GetHuman: Can you tell the rest of us a bit more from what happened on 12/02/17?
GetHuman-dnlldych: You guys tried to charge my card * times .. and the bank put a block in my card
GetHuman: Let's quantify your experience contacting Uber EATS. On a scale of 1 to 5, how easy is it go get help on a Uber EATS problem?
GetHuman-dnlldych: I'd give them a five out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
GetHuman-dnlldych: I'd give them a five out of five on communication.
GetHuman: And what about Uber EATS's ability to quickly and effectively address your problem?
GetHuman-dnlldych: For that I would say five out of five.
GetHuman: And finally- any advice for other Uber EATS customers?
GetHuman-dnlldych: Call them early in the day or late. Don't forget any personal or account information you might need for Uber EATS to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-dnlldych taken from his Uber EATS customer service problem that occurred on December 2nd, 2017.