AirBnB: The operator took my negative review and was ve...
A AirBnB customer review by GetHuman user GetHuman-286357 from November 28th, 2017
Background on GetHuman-286357's case
GetHuman: GetHuman-286357 - can you tell our other AirBnB customers when your case took place?
GetHuman-286357: Yeah. It was afternoon, on November 19th.
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 GetHuman-286357 a list of common AirBnB problems)
GetHuman-286357: "Make a booking" was why I was trying to call.
GetHuman-286357'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.
GetHuman-286357: The operator took my negative review and was very nice she suggested that I ask for a partial reimbursement from the provider I felt like she heard me but I don't know that air BMB will do anything to stop other people from having the same negative experience at this
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?
GetHuman-286357: 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?
GetHuman-286357: I'd give them a three out of five on communication.
GetHuman: And what about AirBnB's ability to quickly and effectively address your problem?
GetHuman-286357: For that I would say four out of five.
GetHuman: And finally- any advice for other AirBnB customers?
GetHuman-286357: Call them early in the day or late. Don't forget any personal or account information you might need for AirBnB to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-286357 taken from his AirBnB customer service problem that occurred on November 19th, 2017.