China Eastern Airlines: All Operators were busy for more than twenty mi...
A China Eastern Airlines customer review by GetHuman user ~disgusted from November 24th, 2017
Background on ~disgusted's case
GetHuman: ~disgusted - can you tell our other China Eastern Airlines customers when your case took place?
~disgusted: Yeah. It was morning, on November 16th.
GetHuman: Did you reach out to China Eastern Airlines, and if so, how?
GetHuman: And which of these common China Eastern Airlines customer issues best describes the reason you wanted to talk to them?
(Shows ~disgusted a list of common China Eastern Airlines problems)
~disgusted: "Complaint" was why I was trying to call.
~disgusted's review of China Eastern Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's China Eastern 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.
~disgusted: All Operators were busy for more than twenty mintues while typing this I am still holding after twenty minutes
GetHuman: Let's quantify your experience contacting China Eastern Airlines. On a scale of 1 to 5, how easy is it go get help on a China Eastern Airlines problem?
~disgusted: 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?
~disgusted: I'd give them a one out of five on communication.
GetHuman: And what about China Eastern Airlines's ability to quickly and effectively address your problem?
~disgusted: For that I would say five out of five.
GetHuman: And finally- any advice for other China Eastern Airlines customers?
~disgusted: Call them early in the day or late. Don't forget any personal or account information you might need for China Eastern Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~disgusted taken from his China Eastern Airlines customer service problem that occurred on November 16th, 2017.