US Airways: I was on hold for **.** minutes when battery on...
A US Airways customer review by GetHuman user ~Never Answered 47 Min. from November 24th, 2017
Background on ~Never Answered 47 Min.'s case
GetHuman: ~Never Answered 47 Min. - can you tell our other US Airways customers when your case took place?
~Never Answered 47 Min.: Yes I can. It was late at night, on November 16th.
GetHuman: Did you reach out to US Airways, and if so, how?
GetHuman: And which of these common US Airways customer issues best describes the reason you wanted to talk to them?
(Shows ~Never Answered 47 Min. a list of common US Airways problems)
~Never Answered 47 Min.: "Baggage problem" was why I was trying to call.
~Never Answered 47 Min.'s review of US Airways customer service
GetHuman: So how would you sum up your experience for GetHuman's US Airways 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.
~Never Answered 47 Min.: I was on hold for **.** minutes when battery on phone started going out. Never got to talk to anyone!
GetHuman: Let's quantify your experience contacting US Airways. On a scale of 1 to 5, how easy is it go get help on a US Airways problem?
~Never Answered 47 Min.: 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?
~Never Answered 47 Min.: I'd give them a three out of five on communication.
GetHuman: And what about US Airways's ability to quickly and effectively address your problem?
~Never Answered 47 Min.: For that I would say four out of five.
GetHuman: And finally- any advice for other US Airways customers?
~Never Answered 47 Min.: Call them early in the day or late. Don't forget any personal or account information you might need for US Airways to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Never Answered 47 Min. taken from his US Airways customer service problem that occurred on November 16th, 2017.