Allegiant: HORRIBLE CUSTOMER SERVICE AND HORRIBLE AIRLINE...
A Allegiant customer review by GetHuman user ~your airline sucks from November 12th, 2017
Background on ~your airline sucks's case
GetHuman: ~your airline sucks - can you tell our other Allegiant customers when your case took place?
~your airline sucks: Yup. It was afternoon, on November 8th.
GetHuman: Did you reach out to Allegiant, and if so, how?
GetHuman: And which of these common Allegiant customer issues best describes the reason you wanted to talk to them?
(Shows ~your airline sucks a list of common Allegiant problems)
~your airline sucks: "Missing item" was why I was trying to call.
~your airline sucks's review of Allegiant customer service
GetHuman: So how would you sum up your experience for GetHuman's Allegiant 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.
~your airline sucks: HORRIBLE CUSTOMER SERVICE AND HORRIBLE AIRLINE, DONT FLY THEM, THEIR PILOTS ARE NOT EVEN TRAINED, THEY ARE WORKING ON FLIGHT HRS, WHY DO YOU THINK THEIR FARES ARE SO CHEAP?
GetHuman: Let's quantify your experience contacting Allegiant. On a scale of 1 to 5, how easy is it go get help on a Allegiant problem?
~your airline sucks: 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?
~your airline sucks: I'd give them a one out of five on communication.
GetHuman: And what about Allegiant's ability to quickly and effectively address your problem?
~your airline sucks: For that I would say three out of five.
GetHuman: And finally- any advice for other Allegiant customers?
~your airline sucks: Call them early in the day or late. Don't forget any personal or account information you might need for Allegiant to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~your airline sucks taken from his Allegiant customer service problem that occurred on November 8th, 2017.