Delta Airlines: I appreciate not having to wait long before get...
Delta Airlines Ulasan pelanggan oleh pengguna GetHuman GetHuman-49013 dari November 27, 2017
Background on GetHuman-49013's case
GetHuman: GetHuman-49013 - can you tell our other Delta Airlines customers when your case took place?
GetHuman-49013: Yup. It was morning, on November 23.
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-49013 a list of common Delta Airlines problems)
GetHuman-49013: "Complaint" was why I was trying to call.
GetHuman-49013'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-49013: I appreciate not having to wait long before getting a customer service agent. I did have to stay on hold for about * minutes for them to cancel my itinerary :)
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-49013: 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-49013: I'd give them a four out of five on communication.
GetHuman: And what about Delta Airlines's ability to quickly and effectively address your problem?
GetHuman-49013: For that I would say five out of five.
GetHuman: And finally- any advice for other Delta Airlines customers?
GetHuman-49013: 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-49013 taken from his Delta Airlines customer service problem that occurred on November 23, 2017.