Southwest Airlines: I use this number when I have a problem that th...
A Southwest Airlines customer review by GetHuman user ~David from November 23rd, 2017
Background on ~David's case
GetHuman: ~David - can you tell our other Southwest Airlines customers when your case took place?
~David: Yup. It was middle of the night, on November 18th.
GetHuman: Did you reach out to Southwest Airlines, and if so, how?
GetHuman: And which of these common Southwest Airlines customer issues best describes the reason you wanted to talk to them?
(Shows ~David a list of common Southwest Airlines problems)
~David: "Refund a Charge" was why I was trying to call.
~David's review of Southwest Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's Southwest 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.
~David: I use this number when I have a problem that the *-*** number can't resolve. Definitely hard to get through (busy signals are common, as most have noted), but once you do get through, these folks are awesome.
GetHuman: Let's quantify your experience contacting Southwest Airlines. On a scale of 1 to 5, how easy is it go get help on a Southwest Airlines problem?
~David: 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?
~David: I'd give them a three out of five on communication.
GetHuman: And what about Southwest Airlines's ability to quickly and effectively address your problem?
~David: For that I would say four out of five.
GetHuman: And finally- any advice for other Southwest Airlines customers?
~David: Call them early in the day or late. Don't forget any personal or account information you might need for Southwest Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~David taken from his Southwest Airlines customer service problem that occurred on November 18th, 2017.