Iberia Airlines: I waited ** minutes for a call back, and they c...
A Iberia Airlines customer review by GetHuman user GetHuman-192644 from November 20th, 2017
Background on GetHuman-192644's case
GetHuman: GetHuman-192644 - can you tell our other Iberia Airlines customers when your case took place?
GetHuman-192644: Yes. It was morning, on November 13th.
GetHuman: Did you reach out to Iberia Airlines, and if so, how?
GetHuman: And which of these common Iberia Airlines customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-192644 a list of common Iberia Airlines problems)
GetHuman-192644: "Frequent flyer program" was why I was trying to call.
GetHuman-192644's review of Iberia Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's Iberia 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-192644: I waited ** minutes for a call back, and they called and told me I needed to call back and press option * which is a non-existent option
GetHuman: Let's quantify your experience contacting Iberia Airlines. On a scale of 1 to 5, how easy is it go get help on a Iberia Airlines problem?
GetHuman-192644: 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-192644: I'd give them a four out of five on communication.
GetHuman: And what about Iberia Airlines's ability to quickly and effectively address your problem?
GetHuman-192644: For that I would say three out of five.
GetHuman: And finally- any advice for other Iberia Airlines customers?
GetHuman-192644: Call them early in the day or late. Don't forget any personal or account information you might need for Iberia Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-192644 taken from his Iberia Airlines customer service problem that occurred on November 13th, 2017.