American Airlines: Called * times and got disconnected each time...
A American Airlines customer review by GetHuman user GetHuman-196970 from November 25th, 2017
Background on GetHuman-196970's case
GetHuman: GetHuman-196970 - can you tell our other American Airlines customers when your case took place?
GetHuman-196970: Yes I can. It was afternoon, on November 15th.
GetHuman: Did you reach out to American Airlines, and if so, how?
GetHuman: And which of these common American Airlines customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-196970 a list of common American Airlines problems)
GetHuman-196970: "Find Itinerary" was why I was trying to call.
GetHuman-196970's review of American Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's American 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-196970: Called * times and got disconnected each time. The call back system also called with no one on the line!
GetHuman: Let's quantify your experience contacting American Airlines. On a scale of 1 to 5, how easy is it go get help on a American Airlines problem?
GetHuman-196970: 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-196970: I'd give them a four out of five on communication.
GetHuman: And what about American Airlines's ability to quickly and effectively address your problem?
GetHuman-196970: For that I would say five out of five.
GetHuman: And finally- any advice for other American Airlines customers?
GetHuman-196970: Call them early in the day or late. Don't forget any personal or account information you might need for American Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-196970 taken from his American Airlines customer service problem that occurred on November 15th, 2017.