American Airlines: the agent I talked to could have told me about...
A American Airlines customer review by GetHuman user ~Vicki Bellino from November 26th, 2017
Background on ~Vicki Bellino's case
GetHuman: ~Vicki Bellino - can you tell our other American Airlines customers when your case took place?
~Vicki Bellino: Yes. It was morning, on November 20th.
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 ~Vicki Bellino a list of common American Airlines problems)
~Vicki Bellino: "Problem With a Flight" was why I was trying to call.
~Vicki Bellino'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.
~Vicki Bellino: the agent I talked to could have told me about having to return to the airport regarding my problem with damages luggage
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?
~Vicki Bellino: I'd give them a one 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?
~Vicki Bellino: 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?
~Vicki Bellino: For that I would say one out of five.
GetHuman: And finally- any advice for other American Airlines customers?
~Vicki Bellino: 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 ~Vicki Bellino taken from his American Airlines customer service problem that occurred on November 20th, 2017.