I want to delete my Uber acct. because of fraud...
Uber Ulasan pelanggan oleh pengguna GetHuman GetHuman-263022 dari November 27, 2017
Background on GetHuman-263022's case
GetHuman: GetHuman-263022 - can you tell our other Uber customers when your case took place?
GetHuman-263022: Yeah. It was morning, on November 25.
GetHuman: Did you reach out to Uber, and if so, how?
GetHuman: And which of these common Uber customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-263022 a list of common Uber problems)
GetHuman-263022: "Billing" was why I was trying to contact.
GetHuman-263022's review of Uber customer service
GetHuman: So how would you sum up your experience for GetHuman's Uber 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-263022: I want to delete my Uber acct. because of fraudulent charges on it. Uber won't reimburse me for the charge and instead asked me to update my acct. with a new password. I don't want any Uber acct. at all. They refuse to delete. I will report them to the ATTY. Gen. and to the FTC.
GetHuman: Let's quantify your experience contacting Uber. On a scale of 1 to 5, how easy is it go get help on a Uber problem?
GetHuman-263022: I'd give them a one 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-263022: I'd give them a two out of five on communication.
GetHuman: And what about Uber's ability to quickly and effectively address your problem?
GetHuman-263022: For that I would say five out of five.
GetHuman: And finally- any advice for other Uber customers?
GetHuman-263022: Cuba berurusan dengan mereka pada awal hari atau kemudian. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Uber mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-263022 taken from his Uber customer service problem that occurred on November 25, 2017.