Monarch Airlines: Don't waste **p a minute by even trying to ring...
A Monarch Airlines customer review by GetHuman user GetHuman-268223 from October 30th, 2017
Background on GetHuman-268223's case
GetHuman: GetHuman-268223 - can you tell our other Monarch Airlines customers when your case took place?
GetHuman-268223: Yup. It was evening, on October 21st.
GetHuman: Did you reach out to Monarch Airlines, and if so, how?
GetHuman: And which of these common Monarch Airlines customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-268223 a list of common Monarch Airlines problems)
GetHuman-268223: "Cancel flight" was why I was trying to call.
GetHuman-268223's review of Monarch Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's Monarch 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-268223: Don't waste **p a minute by even trying to ring. I don't think the phone has ever been answered. It's just there to make a bit of cash.
GetHuman: Let's quantify your experience contacting Monarch Airlines. On a scale of 1 to 5, how easy is it go get help on a Monarch Airlines problem?
GetHuman-268223: 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?
GetHuman-268223: I'd give them a three out of five on communication.
GetHuman: And what about Monarch Airlines's ability to quickly and effectively address your problem?
GetHuman-268223: For that I would say one out of five.
GetHuman: And finally- any advice for other Monarch Airlines customers?
GetHuman-268223: Call them early in the day or late. Don't forget any personal or account information you might need for Monarch Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-268223 taken from his Monarch Airlines customer service problem that occurred on October 21st, 2017.