Ryanair: Unfriendly customer support* didn't seem like t...
A Ryanair customer review by GetHuman user ~Unsatisfied Customer from November 25th, 2017
Background on ~Unsatisfied Customer's case
GetHuman: ~Unsatisfied Customer - can you tell our other Ryanair customers when your case took place?
~Unsatisfied Customer: Yes. It was middle of the night, on November 16th.
GetHuman: Did you reach out to Ryanair, and if so, how?
GetHuman: And which of these common Ryanair customer issues best describes the reason you wanted to talk to them?
(Shows ~Unsatisfied Customer a list of common Ryanair problems)
~Unsatisfied Customer: "Baggage Problem" was why I was trying to call.
~Unsatisfied Customer's review of Ryanair customer service
GetHuman: So how would you sum up your experience for GetHuman's Ryanair 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.
~Unsatisfied Customer: Unfriendly customer support* didn't seem like they cared about your problems. Feels as if the support was outsourced to companies outside of Europe (ie. heavy-accented)
GetHuman: Let's quantify your experience contacting Ryanair. On a scale of 1 to 5, how easy is it go get help on a Ryanair problem?
~Unsatisfied Customer: I'd give them a five 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?
~Unsatisfied Customer: I'd give them a five out of five on communication.
GetHuman: And what about Ryanair's ability to quickly and effectively address your problem?
~Unsatisfied Customer: For that I would say five out of five.
GetHuman: And finally- any advice for other Ryanair customers?
~Unsatisfied Customer: Call them early in the day or late. Don't forget any personal or account information you might need for Ryanair to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Unsatisfied Customer taken from his Ryanair customer service problem that occurred on November 16th, 2017.