Do not book through Webjet. The customer servic...
A Webjet customer review by GetHuman user ~old bushy from November 6th, 2017
Background on ~old bushy's case
GetHuman: ~old bushy - can you tell our other Webjet customers when your case took place?
~old bushy: Yes I can. It was morning, on November 5th.
GetHuman: Did you reach out to Webjet, and if so, how?
GetHuman: And which of these common Webjet customer issues best describes the reason you wanted to talk to them?
(Shows ~old bushy a list of common Webjet problems)
~old bushy: "Baggage problem" was why I was trying to call.
~old bushy's review of Webjet customer service
GetHuman: So how would you sum up your experience for GetHuman's Webjet 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.
~old bushy: Do not book through Webjet. The customer service is non existent. I booked * tickets through Webjet, then had to cancel my wifes ticket * weeks prior to departure. Was refused the refund of taxes. Taxes are not paid by the airline if a ticket is not used so Webjet pockets the tax portion as additional profit. Customer service is not service.
GetHuman: Let's quantify your experience contacting Webjet. On a scale of 1 to 5, how easy is it go get help on a Webjet problem?
~old bushy: 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?
~old bushy: I'd give them a five out of five on communication.
GetHuman: And what about Webjet's ability to quickly and effectively address your problem?
~old bushy: For that I would say four out of five.
GetHuman: And finally- any advice for other Webjet customers?
~old bushy: Call them early in the day or late. Don't forget any personal or account information you might need for Webjet to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~old bushy taken from his Webjet customer service problem that occurred on November 5th, 2017.