Delta Airlines: very helpful lady - patient and knowledgeable...
Delta Airlines Ulasan pelanggan oleh pengguna GetHuman GetHuman-225971 dari November 26, 2017
Background on GetHuman-225971's case
GetHuman: GetHuman-225971 - can you tell our other Delta Airlines customers when your case took place?
GetHuman-225971: Sure. It was afternoon, on November 18.
GetHuman: Did you reach out to Delta Airlines, and if so, how?
GetHuman: And which of these common Delta Airlines customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-225971 a list of common Delta Airlines problems)
GetHuman-225971: "Make a booking" was why I was trying to call.
GetHuman-225971's review of Delta Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's Delta 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-225971: very helpful lady - patient and knowledgeable. working with another airline and Delta takes time. Will see what happens in the next ** hours!
GetHuman: Let's quantify your experience contacting Delta Airlines. On a scale of 1 to 5, how easy is it go get help on a Delta Airlines problem?
GetHuman-225971: 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?
GetHuman-225971: I'd give them a five out of five on communication.
GetHuman: And what about Delta Airlines's ability to quickly and effectively address your problem?
GetHuman-225971: For that I would say five out of five.
GetHuman: And finally- any advice for other Delta Airlines customers?
GetHuman-225971: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Delta Airlines mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-225971 taken from his Delta Airlines customer service problem that occurred on November 18, 2017.