EL Al Airlines: First u charged me $**.- more since i wasn't ab...
A EL Al Airlines customer review by GetHuman user ~norafeit1 from November 14th, 2017
Background on ~norafeit1's case
GetHuman: ~norafeit1 - can you tell our other EL Al Airlines customers when your case took place?
~norafeit1: Sure. It was late at night, on November 9th.
GetHuman: Did you reach out to EL Al Airlines, and if so, how?
GetHuman: And which of these common EL Al Airlines customer issues best describes the reason you wanted to talk to them?
(Shows ~norafeit1 a list of common EL Al Airlines problems)
~norafeit1: "Frequent flyer program" was why I was trying to call.
~norafeit1's review of EL Al Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's EL Al 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.
~norafeit1: First u charged me $**.- more since i wasn't able to conclude my flight which i regard as reprehnsible. Squeezing more from your clients because u make it a hardship to conclude a flight is your problem not mine.
GetHuman: Let's quantify your experience contacting EL Al Airlines. On a scale of 1 to 5, how easy is it go get help on a EL Al Airlines problem?
~norafeit1: I'd give them a four 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?
~norafeit1: I'd give them a five out of five on communication.
GetHuman: And what about EL Al Airlines's ability to quickly and effectively address your problem?
~norafeit1: For that I would say two out of five.
GetHuman: And finally- any advice for other EL Al Airlines customers?
~norafeit1: Call them early in the day or late. Don't forget any personal or account information you might need for EL Al Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~norafeit1 taken from his EL Al Airlines customer service problem that occurred on November 9th, 2017.