AirBnB: Very fast response time. Friendliest cust. serv...
Una recensione del cliente AirBnB da parte dell'utente GetHuman ~mountaingirl da novembre 23º, 2017
Background on ~mountaingirl's case
GetHuman: ~mountaingirl - can you tell our other AirBnB customers when your case took place?
~mountaingirl: Sure. It was late at night, on novembre 20º.
GetHuman: Did you reach out to AirBnB, and if so, how?
GetHuman: And which of these common AirBnB customer issues best describes the reason you wanted to talk to them?
(Shows ~mountaingirl a list of common AirBnB problems)
~mountaingirl: "Update account information" was why I was trying to call.
~mountaingirl's review of AirBnB customer service
GetHuman: So how would you sum up your experience for GetHuman's AirBnB 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.
~mountaingirl: Very fast response time. Friendliest cust. service rep I've EVER spoken to! She answered all my questions & even gave me tips*shortcuts that proved very helpful! (I never would've found that info, if it wasn't for her kindly telling me!) A*
GetHuman: Let's quantify your experience contacting AirBnB. On a scale of 1 to 5, how easy is it go get help on a AirBnB problem?
~mountaingirl: 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?
~mountaingirl: I'd give them a five out of five on communication.
GetHuman: And what about AirBnB's ability to quickly and effectively address your problem?
~mountaingirl: For that I would say five out of five.
GetHuman: And finally- any advice for other AirBnB customers?
~mountaingirl: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per AirBnB sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~mountaingirl taken from his AirBnB customer service problem that occurred on novembre 20º, 2017.