United Airlines: Very frustrating not to find a phone number on...
A United Airlines customer review by GetHuman user ~Weezie's mom from November 21st, 2017
Background on ~Weezie's mom's case
GetHuman: ~Weezie's mom - can you tell our other United Airlines customers when your case took place?
~Weezie's mom: Yup. It was afternoon, 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 ~Weezie's mom a list of common United Airlines problems)
~Weezie's mom: "Special Request" was why I was trying to call.
~Weezie's mom'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.
~Weezie's mom: Very frustrating not to find a phone number on the United website, but thanks to this website, I obtained the number. Once I called I received help very quickly.
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?
~Weezie's mom: 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?
~Weezie's mom: I'd give them a four out of five on communication.
GetHuman: And what about United Airlines's ability to quickly and effectively address your problem?
~Weezie's mom: For that I would say five out of five.
GetHuman: And finally- any advice for other United Airlines customers?
~Weezie's mom: 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 ~Weezie's mom taken from his United Airlines customer service problem that occurred on November 17th, 2017.