United Airlines: complaint
A United Airlines customer review by GetHuman user GetHuman-julieke from November 30th, 2017
Background on GetHuman-julieke's case
GetHuman: GetHuman-julieke - can you tell our other United Airlines customers when your case took place?
GetHuman-julieke: Yeah. It was middle of the night, on November 26th.
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-julieke a list of common United Airlines problems)
GetHuman-julieke: "Account access" was why I was trying to call.
GetHuman-julieke'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: Can you tell the rest of us a bit more from what happened on 11/26/17?
GetHuman-julieke: they oversold my flight - we almost didn't get on - had to check baggage
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-julieke: I'd give them a four 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-julieke: I'd give them a three out of five on communication.
GetHuman: And what about United Airlines's ability to quickly and effectively address your problem?
GetHuman-julieke: For that I would say two out of five.
GetHuman: And finally- any advice for other United Airlines customers?
GetHuman-julieke: Call them early in the day or late. Don't forget any personal or account information you might need for United Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-julieke taken from his United Airlines customer service problem that occurred on November 26th, 2017.