Flybe: Couldnt travel due to sickness so need a no sho...
A Flybe customer review by GetHuman user GetHuman48993 from December 7th, 2017
Background on GetHuman48993's case
GetHuman: GetHuman48993 - can you tell our other Flybe customers when your case took place?
GetHuman48993: Yes. It was middle of the night, on November 29th.
GetHuman: Did you reach out to Flybe, and if so, how?
GetHuman: And which of these common Flybe customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman48993 a list of common Flybe problems)
GetHuman48993: "Complaint" was why I was trying to call.
GetHuman48993's review of Flybe customer service
GetHuman: So how would you sum up your experience for GetHuman's Flybe 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.
GetHuman48993: Couldnt travel due to sickness so need a no show confirmation for my travel insurance
GetHuman: Can you tell the rest of us a bit more from what happened on 11/29/17?
GetHuman48993: My name is Geraldine Casey my record locator is C**QJE. My husband was also meant to travel so will also need a no show receipt for him.
GetHuman: Let's quantify your experience contacting Flybe. On a scale of 1 to 5, how easy is it go get help on a Flybe problem?
GetHuman48993: 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?
GetHuman48993: I'd give them a three out of five on communication.
GetHuman: And what about Flybe's ability to quickly and effectively address your problem?
GetHuman48993: For that I would say four out of five.
GetHuman: And finally- any advice for other Flybe customers?
GetHuman48993: Call them early in the day or late. Don't forget any personal or account information you might need for Flybe to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman48993 taken from his Flybe customer service problem that occurred on November 29th, 2017.