United Airlines: Dear Sirs, I've been privileged to travel the w...
A United Airlines customer review by GetHuman user GetHuman-kathy1m from November 29th, 2017
Background on GetHuman-kathy1m's case
GetHuman: GetHuman-kathy1m - can you tell our other United Airlines customers when your case took place?
GetHuman-kathy1m: Sure. It was morning, on November 20th.
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-kathy1m a list of common United Airlines problems)
GetHuman-kathy1m: "Baggage Problem" was why I was trying to call.
GetHuman-kathy1m'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-kathy1m: Dear Sirs, I've been privileged to travel the world over but had my most horrible customer service experience ever here in Tyler, TX.
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-kathy1m: I'd give them a three 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-kathy1m: 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-kathy1m: For that I would say five out of five.
GetHuman: And finally- any advice for other United Airlines customers?
GetHuman-kathy1m: 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-kathy1m taken from his United Airlines customer service problem that occurred on November 20th, 2017.