Virgin America: tried three separate times and still have not b...
A Virgin America customer review by GetHuman user GetHuman-323977 from November 8th, 2017
Background on GetHuman-323977's case
GetHuman: GetHuman-323977 - can you tell our other Virgin America customers when your case took place?
GetHuman-323977: Yeah. It was morning, on November 3rd.
GetHuman: Did you reach out to Virgin America, and if so, how?
GetHuman: And which of these common Virgin America customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-323977 a list of common Virgin America problems)
GetHuman-323977: "Baggage problem" was why I was trying to call.
GetHuman-323977's review of Virgin America customer service
GetHuman: So how would you sum up your experience for GetHuman's Virgin America 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-323977: tried three separate times and still have not been able to talk to a representative- need assistance immediately and can not get in contact with customer service
GetHuman: Let's quantify your experience contacting Virgin America. On a scale of 1 to 5, how easy is it go get help on a Virgin America problem?
GetHuman-323977: I'd give them a four 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-323977: I'd give them a five out of five on communication.
GetHuman: And what about Virgin America's ability to quickly and effectively address your problem?
GetHuman-323977: For that I would say two out of five.
GetHuman: And finally- any advice for other Virgin America customers?
GetHuman-323977: Call them early in the day or late. Don't forget any personal or account information you might need for Virgin America to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-323977 taken from his Virgin America customer service problem that occurred on November 3rd, 2017.