Virgin Atlantic: Appauling for **** customer service line. Cut o...
Un Virgin Atlantic avis client de l'utilisateur GetHuman GetHuman-98856 de novembre 22, 2017
Background on GetHuman-98856's case
GetHuman: GetHuman-98856 - can you tell our other Virgin Atlantic customers when your case took place?
GetHuman-98856: Sure. It was evening, on novembre 17.
GetHuman: Did you reach out to Virgin Atlantic, and if so, how?
GetHuman: And which of these common Virgin Atlantic customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-98856 a list of common Virgin Atlantic problems)
GetHuman-98856: "Flight delayed" was why I was trying to call.
GetHuman-98856's review of Virgin Atlantic customer service
GetHuman: So how would you sum up your experience for GetHuman's Virgin Atlantic 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-98856: Appauling for **** customer service line. Cut off twice on first two attempts and then had to wait over ** minutes.
GetHuman: Let's quantify your experience contacting Virgin Atlantic. On a scale of 1 to 5, how easy is it go get help on a Virgin Atlantic problem?
GetHuman-98856: I'd give them a five 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-98856: I'd give them a five out of five on communication.
GetHuman: And what about Virgin Atlantic's ability to quickly and effectively address your problem?
GetHuman-98856: For that I would say three out of five.
GetHuman: And finally- any advice for other Virgin Atlantic customers?
GetHuman-98856: Appelez-les tôt dans la journée ou tard. N'oubliez pas les informations personnelles ou de compte dont vous pourriez avoir besoin pour Virgin Atlantic pour savoir qui vous êtes.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-98856 taken from his Virgin Atlantic customer service problem that occurred on novembre 17, 2017.