Delta Airlines: Didn't use this number - used a different one b...
A Delta Airlines customer review by GetHuman user GetHuman-284742 from November 22nd, 2017
Background on GetHuman-284742's case
GetHuman: GetHuman-284742 - can you tell our other Delta Airlines customers when your case took place?
GetHuman-284742: Yeah. It was morning, on November 15th.
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-284742 a list of common Delta Airlines problems)
GetHuman-284742: "Flight Inquiry" was why I was trying to call.
GetHuman-284742'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-284742: Didn't use this number - used a different one but literally as soon as I pressed '*' it started ringing and someone picked up - pressing '*' really works!
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-284742: 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-284742: I'd give them a one out of five on communication.
GetHuman: And what about Delta Airlines's ability to quickly and effectively address your problem?
GetHuman-284742: For that I would say four out of five.
GetHuman: And finally- any advice for other Delta Airlines customers?
GetHuman-284742: Call them early in the day or late. Don't forget any personal or account information you might need for Delta Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-284742 taken from his Delta Airlines customer service problem that occurred on November 15th, 2017.