Vayama: Horrible customer service, admitted that you ar...
A Vayama customer review by GetHuman user ~GS from November 18th, 2017
Background on ~GS's case
GetHuman: ~GS - can you tell our other Vayama customers when your case took place?
~GS: Yup. It was middle of the night, on November 14th.
GetHuman: Did you reach out to Vayama, and if so, how?
GetHuman: And which of these common Vayama customer issues best describes the reason you wanted to talk to them?
(Shows ~GS a list of common Vayama problems)
~GS: "Insurance claim" was why I was trying to call.
~GS's review of Vayama customer service
GetHuman: So how would you sum up your experience for GetHuman's Vayama 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.
~GS: Horrible customer service, admitted that you are "taking a gamble" by buying tickets with Vayama. They do not make any of their fare change policies clear, and when confirmed with the actual airlines (Virgin Atlantic) they agree that Vayama is at fault for not elucidating the type of ticket being purchased. Customer Service treats you like a child, and hides behind the nebulous areas provided by their policies.
GetHuman: Let's quantify your experience contacting Vayama. On a scale of 1 to 5, how easy is it go get help on a Vayama problem?
~GS: I'd give them a five 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?
~GS: I'd give them a five out of five on communication.
GetHuman: And what about Vayama's ability to quickly and effectively address your problem?
~GS: For that I would say three out of five.
GetHuman: And finally- any advice for other Vayama customers?
~GS: Call them early in the day or late. Don't forget any personal or account information you might need for Vayama to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~GS taken from his Vayama customer service problem that occurred on November 14th, 2017.