Messaging
Change a reservation, from ask to answer
A traveler asks for a change from their reservation sheet: new dates, a different party size, even a move to another of the same host's properties — with a live price quote before sending. The request lands in the host's thread as a structured card.
The host's answers
- Accept applies the request as asked — but the price is re-quoted against the live calendar at that moment. The traveler's quote is context; the calendar is the authority.
- Decline leaves the reservation exactly as booked and says so in the thread.
- Send your own — a host who wants something different sends their own change from Manage reservation → Change reservation. It replaces the guest's ask, and the guest accepts or declines it.
On the host's side, Accept and Decline appear only for teammates allowed to take, change and cancel bookings.
Every outcome is narrated to both sides automatically. If an accepted change makes the stay cheaper, what the guest paid over the new total goes back to their card straight away; if dearer, the guest owes the difference.
Extra nights that answer themselves
A host can let a guest's ask for more nights go through without them. Under Settings → Defaults → Requests, or on one listing under Availability → Instant book, choose what happens when a guest asks for extra nights:
- Ask me: it waits for you, and ends after 48 hours unanswered.
- Approve when it expires: unanswered after 48 hours, it goes through.
- Approve right away: it goes through as soon as the guest asks.
It only covers more nights at the same place for the same guests. A shorter stay, other dates, another place or a different party always waits for you. It is the same accept as your button, so it never approves nights that are no longer free, a party the place can't hold, or a price that has changed since the guest asked. When it can't go through, you're told why.
The thread says Accepted automatically, and your team gets an email saying so.
Changing your mind
A traveler can change their own pending request — sending again replaces the earlier ask, which stays in the thread marked *Replaced by a newer request* — or withdraw it with Take back. Once the host has answered, the card wears its outcome: Accepted or Declined.