American Airlines: The automated answering machine told the wait i...
A American Airlines customer review by GetHuman user ~tiredwaiting from November 26th, 2017
Background on ~tiredwaiting's case
GetHuman: ~tiredwaiting - can you tell our other American Airlines customers when your case took place?
~tiredwaiting: Yes. It was afternoon, on November 18th.
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 ~tiredwaiting a list of common American Airlines problems)
~tiredwaiting: "Problem With a Flight" was why I was trying to call.
~tiredwaiting'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.
~tiredwaiting: The automated answering machine told the wait is about **-**minutes so I waited. After being on hold for ** minutes, I gave up.
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?
~tiredwaiting: 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?
~tiredwaiting: I'd give them a two out of five on communication.
GetHuman: And what about American Airlines's ability to quickly and effectively address your problem?
~tiredwaiting: For that I would say three out of five.
GetHuman: And finally- any advice for other American Airlines customers?
~tiredwaiting: 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 ~tiredwaiting taken from his American Airlines customer service problem that occurred on November 18th, 2017.