United Airlines: As soon as I pressed ** for "current or future...
Una recensione del cliente United Airlines da parte dell'utente GetHuman GetHuman-319841 da novembre 28º, 2017
Background on GetHuman-319841's case
GetHuman: GetHuman-319841 - can you tell our other United Airlines customers when your case took place?
GetHuman-319841: Sure. It was afternoon, on novembre 20º.
GetHuman: Did you reach out to United Airlines, and if so, how?
GetHuman: And which of these common United Airlines customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-319841 a list of common United Airlines problems)
GetHuman-319841: "Special Request" was why I was trying to call.
GetHuman-319841's review of United Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's United Airlines 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-319841: As soon as I pressed ** for "current or future travel" I was connected to a very courteous representative
GetHuman: Let's quantify your experience contacting United Airlines. On a scale of 1 to 5, how easy is it go get help on a United Airlines problem?
GetHuman-319841: 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-319841: I'd give them a two out of five on communication.
GetHuman: And what about United Airlines's ability to quickly and effectively address your problem?
GetHuman-319841: For that I would say three out of five.
GetHuman: And finally- any advice for other United Airlines customers?
GetHuman-319841: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per United Airlines sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-319841 taken from his United Airlines customer service problem that occurred on novembre 20º, 2017.