Spirit Air: What a joke. Took my ccard info to pay for one...
A Spirit Air customer review by GetHuman user GetHuman-432469 from November 18th, 2017
Background on GetHuman-432469's case
GetHuman: GetHuman-432469 - can you tell our other Spirit Air customers when your case took place?
GetHuman-432469: Yes. It was afternoon, on November 15th.
GetHuman: Did you reach out to Spirit Air, and if so, how?
GetHuman: And which of these common Spirit Air customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-432469 a list of common Spirit Air problems)
GetHuman-432469: "Change booking" was why I was trying to call.
GetHuman-432469's review of Spirit Air customer service
GetHuman: So how would you sum up your experience for GetHuman's Spirit Air 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-432469: What a joke. Took my ccard info to pay for one bag, then wouldn't send me an email confirmation. Instead, told "not to worry" about it, and just check in at the airport. We'll see if they try charging me $***...
GetHuman: Let's quantify your experience contacting Spirit Air. On a scale of 1 to 5, how easy is it go get help on a Spirit Air problem?
GetHuman-432469: 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-432469: I'd give them a five out of five on communication.
GetHuman: And what about Spirit Air's ability to quickly and effectively address your problem?
GetHuman-432469: For that I would say two out of five.
GetHuman: And finally- any advice for other Spirit Air customers?
GetHuman-432469: Call them early in the day or late. Don't forget any personal or account information you might need for Spirit Air to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-432469 taken from his Spirit Air customer service problem that occurred on November 15th, 2017.