Aer Lingus: Are Lingus lost my bag between JFK and Paris...
Un Aer Lingus avis client de l'utilisateur GetHuman GetHuman-312989 de novembre 23, 2017
Background on GetHuman-312989's case
GetHuman: GetHuman-312989 - can you tell our other Aer Lingus customers when your case took place?
GetHuman-312989: Yes. It was evening, on novembre 14.
GetHuman: Did you reach out to Aer Lingus, and if so, how?
GetHuman: And which of these common Aer Lingus customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-312989 a list of common Aer Lingus problems)
GetHuman-312989: "Make a booking" was why I was trying to call.
GetHuman-312989's review of Aer Lingus customer service
GetHuman: So how would you sum up your experience for GetHuman's Aer Lingus 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-312989: Are Lingus lost my bag between JFK and Paris. I finally found my bag myself at the Paris airport lost luggage room. Are Lingus never replied to a single email. Will not fly EI again.
GetHuman: Let's quantify your experience contacting Aer Lingus. On a scale of 1 to 5, how easy is it go get help on a Aer Lingus problem?
GetHuman-312989: 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-312989: I'd give them a three out of five on communication.
GetHuman: And what about Aer Lingus's ability to quickly and effectively address your problem?
GetHuman-312989: For that I would say four out of five.
GetHuman: And finally- any advice for other Aer Lingus customers?
GetHuman-312989: 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 Aer Lingus pour savoir qui vous êtes.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-312989 taken from his Aer Lingus customer service problem that occurred on novembre 14, 2017.