Spirit Air: I finally got a human on the phone. Trying to...
A Spirit Air customer review by GetHuman user GetHuman-132212 from November 24th, 2017
Background on GetHuman-132212's case
GetHuman: GetHuman-132212 - can you tell our other Spirit Air customers when your case took place?
GetHuman-132212: Yeah. It was afternoon, on November 22nd.
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-132212 a list of common Spirit Air problems)
GetHuman-132212: "Cancel flight" was why I was trying to call.
GetHuman-132212'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-132212: I finally got a human on the phone. Trying to fix their website issues for my *** year old mother so she doesn't incur their charges fro dealing with a human. The BARE FARE is really ****. Fly on a REAL airline!
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-132212: I'd give them a one 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-132212: I'd give them a four out of five on communication.
GetHuman: And what about Spirit Air's ability to quickly and effectively address your problem?
GetHuman-132212: For that I would say one out of five.
GetHuman: And finally- any advice for other Spirit Air customers?
GetHuman-132212: 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-132212 taken from his Spirit Air customer service problem that occurred on November 22nd, 2017.