HomeAway.com: terrible service. i am out of the country tryi...
HomeAway.com Ulasan pelanggan oleh pengguna GetHuman ~markpapucho dari November 26, 2017
Background on ~markpapucho's case
GetHuman: ~markpapucho - can you tell our other HomeAway.com customers when your case took place?
~markpapucho: Yes. It was middle of the night, on November 22.
GetHuman: Did you reach out to HomeAway.com, and if so, how?
GetHuman: And which of these common HomeAway.com customer issues best describes the reason you wanted to talk to them?
(Shows ~markpapucho a list of common HomeAway.com problems)
~markpapucho: "Make a booking" was why I was trying to call.
~markpapucho's review of HomeAway.com customer service
GetHuman: So how would you sum up your experience for GetHuman's HomeAway.com 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.
~markpapucho: terrible service. i am out of the country trying to access website and unable to. a verification code is being sent to my home in wisconsin where it does me no good. tool long of waits on the phone.
GetHuman: Let's quantify your experience contacting HomeAway.com. On a scale of 1 to 5, how easy is it go get help on a HomeAway.com problem?
~markpapucho: 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?
~markpapucho: I'd give them a four out of five on communication.
GetHuman: And what about HomeAway.com's ability to quickly and effectively address your problem?
~markpapucho: For that I would say three out of five.
GetHuman: And finally- any advice for other HomeAway.com customers?
~markpapucho: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk HomeAway.com mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~markpapucho taken from his HomeAway.com customer service problem that occurred on November 22, 2017.