VRBO: I called * times and had to stay on hold each t...
Una recensione del cliente VRBO da parte dell'utente GetHuman GetHuman-37658 da novembre 21º, 2017
Background on GetHuman-37658's case
GetHuman: GetHuman-37658 - can you tell our other VRBO customers when your case took place?
GetHuman-37658: Yup. It was middle of the night, on novembre 14º.
GetHuman: Did you reach out to VRBO, and if so, how?
GetHuman: And which of these common VRBO customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-37658 a list of common VRBO problems)
GetHuman-37658: "Refund a Charge" was why I was trying to call.
GetHuman-37658's review of VRBO customer service
GetHuman: So how would you sum up your experience for GetHuman's VRBO 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-37658: I called * times and had to stay on hold each time for ** minutes. People who WORK cannot do this* we have no time for such. With thousands of homes on VRBO, it would appear this company could hire people to answer the phone from the persons supporting the business!!
GetHuman: Let's quantify your experience contacting VRBO. On a scale of 1 to 5, how easy is it go get help on a VRBO problem?
GetHuman-37658: 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?
GetHuman-37658: I'd give them a four out of five on communication.
GetHuman: And what about VRBO's ability to quickly and effectively address your problem?
GetHuman-37658: For that I would say three out of five.
GetHuman: And finally- any advice for other VRBO customers?
GetHuman-37658: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per VRBO sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-37658 taken from his VRBO customer service problem that occurred on novembre 14º, 2017.