Korean Air: very friendly and helpful. turned a rather terr...
A Korean Air customer review by GetHuman user ~blahblah from November 24th, 2017
Background on ~blahblah's case
GetHuman: ~blahblah - can you tell our other Korean Air customers when your case took place?
~blahblah: Yup. It was morning, on November 19th.
GetHuman: Did you reach out to Korean Air, and if so, how?
GetHuman: And which of these common Korean Air customer issues best describes the reason you wanted to talk to them?
(Shows ~blahblah a list of common Korean Air problems)
~blahblah: "Complaint" was why I was trying to call.
~blahblah's review of Korean Air customer service
GetHuman: So how would you sum up your experience for GetHuman's Korean 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.
~blahblah: very friendly and helpful. turned a rather terrible situation into a pleasant customer service experience. It took awhile and multiple calls to reach a resolution my friends and I were happy with the outcome. I did talk to the korean call center by pressing *. us call center wasn't much of help.
GetHuman: Let's quantify your experience contacting Korean Air. On a scale of 1 to 5, how easy is it go get help on a Korean Air problem?
~blahblah: I'd give them a three 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?
~blahblah: I'd give them a five out of five on communication.
GetHuman: And what about Korean Air's ability to quickly and effectively address your problem?
~blahblah: For that I would say five out of five.
GetHuman: And finally- any advice for other Korean Air customers?
~blahblah: Call them early in the day or late. Don't forget any personal or account information you might need for Korean Air to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~blahblah taken from his Korean Air customer service problem that occurred on November 19th, 2017.