United Airlines: There was no communication. Automated thing jus...
A United Airlines customer review by GetHuman user GetHuman-165379 from November 25th, 2017
Background on GetHuman-165379's case
GetHuman: GetHuman-165379 - can you tell our other United Airlines customers when your case took place?
GetHuman-165379: Yes. It was middle of the night, on November 17th.
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-165379 a list of common United Airlines problems)
GetHuman-165379: "Special Request" was why I was trying to call.
GetHuman-165379'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-165379: There was no communication. Automated thing just says "leave a message". Useless. Called * times before **** CTZ from Missouri
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-165379: 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-165379: I'd give them a five out of five on communication.
GetHuman: And what about United Airlines's ability to quickly and effectively address your problem?
GetHuman-165379: For that I would say one out of five.
GetHuman: And finally- any advice for other United Airlines customers?
GetHuman-165379: 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-165379 taken from his United Airlines customer service problem that occurred on November 17th, 2017.