Allegiant: This was supposed to be the airline company cal...
A Allegiant customer review by GetHuman user ~seabeam from November 11th, 2017
Background on ~seabeam's case
GetHuman: ~seabeam - can you tell our other Allegiant customers when your case took place?
~seabeam: Yeah. It was afternoon, on November 4th.
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 ~seabeam a list of common Allegiant problems)
~seabeam: "Flight delayed" was why I was trying to call.
~seabeam'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.
~seabeam: This was supposed to be the airline company calling me back and it turned out to be a sales pitch, not the airline, and my important question was not answered. This is false advertising on your part, I wasted ** min and then had to fight off a sales pitch for coupons I did not want. I will be informing my friends
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?
~seabeam: I'd give them a two 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?
~seabeam: I'd give them a five out of five on communication.
GetHuman: And what about Allegiant's ability to quickly and effectively address your problem?
~seabeam: For that I would say four out of five.
GetHuman: And finally- any advice for other Allegiant customers?
~seabeam: 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 ~seabeam taken from his Allegiant customer service problem that occurred on November 4th, 2017.