Korean Air: chat service online did not work*hard to find p...
A Korean Air customer review by GetHuman user GetHuman-19773 from November 24th, 2017
Background on GetHuman-19773's case
GetHuman: GetHuman-19773 - can you tell our other Korean Air customers when your case took place?
GetHuman-19773: Yup. It was middle of the night, on November 17th.
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 GetHuman-19773 a list of common Korean Air problems)
GetHuman-19773: "Make a booking" was why I was trying to call.
GetHuman-19773'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.
GetHuman-19773: chat service online did not work*hard to find phone number on website*once i finally found phone number (thru this website) they are experiencing system problems and wont connect you to a representative??? wth???
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?
GetHuman-19773: 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-19773: 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?
GetHuman-19773: For that I would say two out of five.
GetHuman: And finally- any advice for other Korean Air customers?
GetHuman-19773: 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 GetHuman-19773 taken from his Korean Air customer service problem that occurred on November 17th, 2017.