Declining Reservations

When a guest sends a Request to Book or an inquiry that you can't accept, you decline it directly from the Vanio dashboard. The decline is sent to Airbnb (or whichever channel the request came from), the calendar reopens, and the guest gets the message you wrote explaining why.

Quick reference: Decline reservation, reject booking, decline RTB, decline request to book, refuse booking, say no to a request, decline inquiry — all done from the dashboard reservation modal → Decline button.

Where to find it

When a Request to Book or pending reservation comes in, it shows up in your dashboard with a Pending status. Click the reservation to open the modal. The modal has a Decline button next to Accept.

(For inquiries that aren't bookable yet, you don't decline — you just reply or let them expire.)

How to decline

1. Open the pending reservation in the dashboard.
2. Click Decline. A dialog opens.
3. Pick a Reason from the dropdown:
   • Dates unavailable — the property is taken or blocked for those dates
   • Not comfortable — something about the guest, group size, or trip purpose feels wrong
   • Unsuitable for listing — the property doesn't fit what they're looking for (party, large group, pets when not allowed, etc.)
   • Maintenance issue — the property has an active maintenance problem
   • Other — anything that doesn't fit the above
4. Write a Message to the guest. This is required and limited to 500 characters. Be respectful — the guest will read this.
5. Click Decline to submit.

Vanio sends the decline + your message to Airbnb (or the originating channel). Airbnb notifies the guest. The reservation moves to "Declined" status in the dashboard. The dates that were tentatively held are released back to your calendar.

What happens after you decline

• The dates reopen. Other guests can book them again immediately.
• Your acceptance rate. Airbnb tracks how often you decline. A high decline rate can affect Superhost status and search ranking. Use it sparingly — see "When NOT to decline" below.
• The guest is notified. They see the reason category and your message.
• The conversation thread stays open. If the guest replies, you'll see it in your inbox. You can offer different dates or a different property.
• The reservation stays in your records under the Declined filter, so you can see history and patterns.

When NOT to decline

Declining is the wrong tool for some situations:

• Guest wants to change dates → Use Modify dates instead. Don't decline and ask them to rebook.
• Guest is asking questions before booking → It's an inquiry, not a request. Reply normally; no decline needed.
• You want to accept but not at this price → Use Special offer to send them a custom price quote. See Pre-approval and special offers.
• You want to block these dates from everyone for non-guest reasons → Use the calendar to block the dates BEFORE the request comes in. Once a request is in, declining is the only way to release the hold.
• You have second thoughts after accepting → That's a cancellation, not a decline. See "Cancelling an accepted reservation" below.

Cancelling an accepted reservation

Different from declining. Once a reservation is accepted (paid, confirmed), the right action is Cancel, not Decline.

Vanio has a Cancel action in the dashboard modal too. Picking it opens a separate dialog with these reasons:

• Calendar conflict
• Maintenance issue
• Unable to host
• Other

Cancellations can carry penalties from Airbnb (loss of Superhost, refund to guest, fee). Vanio doesn't decide the penalty — Airbnb does, based on their host cancellation policy. The cancel goes through, the reservation is marked cancelled by host, and any payment Airbnb collected is refunded to the guest per their cancellation policy.

For your direct booking website, cancellation works the same way but Vanio handles the refund through Stripe Connect (full or partial refund based on your set policy).

Common scenarios

"A guest with a 4.2 rating sent an RTB and I'm worried about parties." Open the request → Decline → Reason: Not comfortable → Message: "Thanks for your interest. I'm only able to host guests with a 4.7+ rating for these dates. Wishing you a great trip." Don't make excuses you don't believe; the guest can tell.

"They want to bring 8 people, my listing is for 6." Decline → Reason: Unsuitable for listing → Message: "Thanks for the request — unfortunately the property is set up to comfortably host a maximum of 6 guests. I'd recommend looking for a larger place for your group." Don't accept and figure it out later.

"They're asking for dates I already had blocked but Vanio shows them as available somehow." Don't decline yet — first check the calendar (Calendar → click those dates) and see why they're showing available. Could be a sync glitch from when you blocked them. Fix the block, then decline with Reason: Dates unavailable.

"They want to cancel a reservation they already paid for." That's a guest cancellation, not a host action. They cancel from Airbnb's side. Once they do, Vanio gets the cancellation event and updates the reservation status automatically. You don't need to do anything.

"I accepted yesterday and now I realize I can't host that week." Open the reservation → Cancel → Reason: Unable to host → write the message. Be aware Airbnb may charge a host cancellation fee depending on how close to check-in you are.

Why you decline matters

The reason you pick matters for two reasons:

1. Airbnb uses it for ranking and warnings. Picking "Not comfortable" triggers different downstream behavior than "Dates unavailable." Don't pick "Dates unavailable" if the dates ARE available — that's flagged as misleading.
2. It's logged in your audit trail. Vanio records every decline with reason, timestamp, who clicked, and the message sent. Useful when reviewing patterns later or training new team members.