I had a guest instant book for a checkin today. We have a st...
Latest reply
I had a guest instant book for a checkin today. We have a strict 4pm checkin time & they showed up at 2:15 saying they chose ...
Latest reply
Sign in with your Airbnb account to continue reading, sharing, and connecting with millions of hosts from around the world.
So, A guest inquired to stay 10-15, and I replied that I had made a mistake and that the 15th wasn't supposed to be available on the calendar. I offered her to check late on the 14th, or come in a day earlier, on the 9th. She replied that it wouldn't work. Then, later that same day (before the 24h period) I replied that I was abe to make it work and accepetd her reservation as it is 10-15. She got back to me that she had already booked with someone else (before we finalized our conversation)and asked to be refunded.
I was trying to cancel and refund her but I read it and I get to pay fee, (maybe fee waived if it is the 1st time) and how it would affect my listing. So I'm asking her to cancel on her end.
I want to be fair to both of us.
Opinions?
You made the mistake - you pay. But make your guest make the cancellation and then refund the airbnb fees through the resolution center. If you cancel a confirmed booking - the dates will be blocked and your superhost status gone.
I don't agree. The guest made the mistake, because she booked another place but did not cancel this reservation request.
Hummm.. so a guest can make as many requests as possible? how can they be booked without her accepting??
The first booking must have been booked? and she didnt see this before she booked another place?
Im confused?
If it was instant book and she booked straight away then that i understand but it didnt read that way...
But if she made a request and was told 15 th is not possible how did it get booked without her accepting, when guests write to me on my instant book, i send invite after and they have to accept.
Mala
Maybe it was booked using instant book and since turned off ?
Anyways, the situation seems a bit unclear. What is very clear though, is that the calendar was not up to date at the time of request and this caused the situation initially. The rest seems to be a string of misunderstandings.