FlightHub: I am still trying to find my reservation with t...
A FlightHub customer review by GetHuman user GetHuman-401305 from November 25th, 2017
Background on GetHuman-401305's case
GetHuman: GetHuman-401305 - can you tell our other FlightHub customers when your case took place?
GetHuman-401305: Yes I can. It was morning, on November 19th.
GetHuman: Did you reach out to FlightHub, and if so, how?
GetHuman: And which of these common FlightHub customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-401305 a list of common FlightHub problems)
GetHuman-401305: "None of those really matches why I wanted to call FlightHub that day." was why I was trying to call.
GetHuman-401305's review of FlightHub customer service
GetHuman: So how would you sum up your experience for GetHuman's FlightHub 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-401305: I am still trying to find my reservation with them which was billed and paid for ($****.**) on Sept **. I waited then the phone rang and noone answered. I called again and waited and they cannot find my records.
GetHuman: Let's quantify your experience contacting FlightHub. On a scale of 1 to 5, how easy is it go get help on a FlightHub problem?
GetHuman-401305: 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-401305: I'd give them a one out of five on communication.
GetHuman: And what about FlightHub's ability to quickly and effectively address your problem?
GetHuman-401305: For that I would say one out of five.
GetHuman: And finally- any advice for other FlightHub customers?
GetHuman-401305: Call them early in the day or late. Don't forget any personal or account information you might need for FlightHub to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-401305 taken from his FlightHub customer service problem that occurred on November 19th, 2017.