Frontier Airlines: Due to a nuclear customer service failure, I ha...
A Frontier Airlines customer review by GetHuman user ~Mark from November 22nd, 2017
Background on ~Mark's case
GetHuman: ~Mark - can you tell our other Frontier Airlines customers when your case took place?
~Mark: Sure. It was morning, on November 17th.
GetHuman: Did you reach out to Frontier Airlines, and if so, how?
GetHuman: And which of these common Frontier Airlines customer issues best describes the reason you wanted to talk to them?
(Shows ~Mark a list of common Frontier Airlines problems)
~Mark: "Frequent flyer program" was why I was trying to call.
~Mark's review of Frontier Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's Frontier 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.
~Mark: Due to a nuclear customer service failure, I had to speak with a supervisor. Definitely the longest on-hold customer service wait I've ever experienced. With all the unemployed people in the US, you'd think they could hire a few hundred.
GetHuman: Let's quantify your experience contacting Frontier Airlines. On a scale of 1 to 5, how easy is it go get help on a Frontier Airlines problem?
~Mark: 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?
~Mark: I'd give them a two out of five on communication.
GetHuman: And what about Frontier Airlines's ability to quickly and effectively address your problem?
~Mark: For that I would say three out of five.
GetHuman: And finally- any advice for other Frontier Airlines customers?
~Mark: Call them early in the day or late. Don't forget any personal or account information you might need for Frontier Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Mark taken from his Frontier Airlines customer service problem that occurred on November 17th, 2017.