Turkish Airlines: Communication was not a problem, agent spoke Am...
A Turkish Airlines customer review by GetHuman user GetHuman-71672 from November 22nd, 2017
Background on GetHuman-71672's case
GetHuman: GetHuman-71672 - can you tell our other Turkish Airlines customers when your case took place?
GetHuman-71672: Yeah. It was evening, on November 19th.
GetHuman: Did you reach out to Turkish Airlines, and if so, how?
GetHuman: And which of these common Turkish Airlines customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-71672 a list of common Turkish Airlines problems)
GetHuman-71672: "Make a booking" was why I was trying to call.
GetHuman-71672's review of Turkish Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's Turkish 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.
GetHuman-71672: Communication was not a problem, agent spoke American English without an accent. Offered helpful tips. The only negative was the long wait time.
GetHuman: Let's quantify your experience contacting Turkish Airlines. On a scale of 1 to 5, how easy is it go get help on a Turkish Airlines problem?
GetHuman-71672: 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?
GetHuman-71672: I'd give them a five out of five on communication.
GetHuman: And what about Turkish Airlines's ability to quickly and effectively address your problem?
GetHuman-71672: For that I would say two out of five.
GetHuman: And finally- any advice for other Turkish Airlines customers?
GetHuman-71672: Call them early in the day or late. Don't forget any personal or account information you might need for Turkish Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-71672 taken from his Turkish Airlines customer service problem that occurred on November 19th, 2017.