Swiss Airlines: This was an excellent number . They answered im...
A Swiss Airlines customer review by GetHuman user ~Boston Traveler from November 21st, 2017
Background on ~Boston Traveler's case
GetHuman: ~Boston Traveler - can you tell our other Swiss Airlines customers when your case took place?
~Boston Traveler: Yeah. It was middle of the night, on November 13th.
GetHuman: Did you reach out to Swiss Airlines, and if so, how?
GetHuman: And which of these common Swiss Airlines customer issues best describes the reason you wanted to talk to them?
(Shows ~Boston Traveler a list of common Swiss Airlines problems)
~Boston Traveler: "Frequent flyer program" was why I was trying to call.
~Boston Traveler's review of Swiss Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's Swiss 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.
~Boston Traveler: This was an excellent number . They answered immediately after the question of what was I interested in and were great. Thanks.
GetHuman: Let's quantify your experience contacting Swiss Airlines. On a scale of 1 to 5, how easy is it go get help on a Swiss Airlines problem?
~Boston Traveler: 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?
~Boston Traveler: I'd give them a five out of five on communication.
GetHuman: And what about Swiss Airlines's ability to quickly and effectively address your problem?
~Boston Traveler: For that I would say four out of five.
GetHuman: And finally- any advice for other Swiss Airlines customers?
~Boston Traveler: Call them early in the day or late. Don't forget any personal or account information you might need for Swiss Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Boston Traveler taken from his Swiss Airlines customer service problem that occurred on November 13th, 2017.