JetBlue: Hung up on after * minutes, then waited another...
A JetBlue customer review by GetHuman user GetHuman-208998 from November 6th, 2017
Background on GetHuman-208998's case
GetHuman: GetHuman-208998 - can you tell our other JetBlue customers when your case took place?
GetHuman-208998: Yup. It was afternoon, on October 30th.
GetHuman: Did you reach out to JetBlue, and if so, how?
GetHuman: And which of these common JetBlue customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-208998 a list of common JetBlue problems)
GetHuman-208998: "Cancel flight" was why I was trying to call.
GetHuman-208998's review of JetBlue customer service
GetHuman: So how would you sum up your experience for GetHuman's JetBlue 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-208998: Hung up on after * minutes, then waited another * minutes on call back. Airline changed schedule so it no longer worked for us, and refused to give cash refund, would only provide JetBlue credit...not usable on other airlines with acceptable schedules.
GetHuman: Let's quantify your experience contacting JetBlue. On a scale of 1 to 5, how easy is it go get help on a JetBlue problem?
GetHuman-208998: 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-208998: I'd give them a five out of five on communication.
GetHuman: And what about JetBlue's ability to quickly and effectively address your problem?
GetHuman-208998: For that I would say four out of five.
GetHuman: And finally- any advice for other JetBlue customers?
GetHuman-208998: Call them early in the day or late. Don't forget any personal or account information you might need for JetBlue to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-208998 taken from his JetBlue customer service problem that occurred on October 30th, 2017.