FlightHub: I booked a flight with my visa debit and found...
A FlightHub customer review by GetHuman user ~123456 from November 24th, 2017
Background on ~123456's case
GetHuman: ~123456 - can you tell our other FlightHub customers when your case took place?
~123456: Yup. It was middle of the night, on November 22nd.
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 ~123456 a list of common FlightHub problems)
~123456: "None of those really matches why I wanted to call FlightHub that day." was why I was trying to call.
~123456'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.
~123456: I booked a flight with my visa debit and found out later that they don't accept this type of payment. However, they still took the funds out of my account but I didn't get the reservation. Told to call my bank, bank has to do an investigation that will take up to ** days. Will never use this booking company again.
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?
~123456: I'd give them a one 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?
~123456: I'd give them a two out of five on communication.
GetHuman: And what about FlightHub's ability to quickly and effectively address your problem?
~123456: For that I would say three out of five.
GetHuman: And finally- any advice for other FlightHub customers?
~123456: 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 ~123456 taken from his FlightHub customer service problem that occurred on November 22nd, 2017.