What is Request to Book?
Request to Book (RTB) is a booking mode in WanderOS that lets you review and approve guest inquiries before they're finalized. Instead of an instant reservation, guests submit a request that you evaluate against your own criteria before charging the card and confirming the stay.
Why use Request to Book?
RTB gives you greater oversight of your property operations and lets you:
Vet guest details before committing to a stay.
Ensure compliance with your house rules and property standards.
Manage high-demand dates like holidays and peak weekends with more flexibility.
Build trust by establishing a connection with new guests before confirming.
Request to Book vs. Instant Book
Feature | Request to Book | Instant Book |
Guest submits request | Yes | Yes |
Automatic confirmation | No | Yes |
Host approval required | Yes | No |
Best for | Premium luxury properties and guest vetting | Maximizing booking volume |
How do I enable Request to Book?
Log in to app.wander.com.
Click Listings in the left sidebar.
Select the specific property you want to configure.
Select Booking Type.
Under Booking Type, select Request to Book.
Note: This setting must be applied to each listing individually. There is no bulk toggle, so plan to update properties one at a time across your portfolio.
How do I manage incoming requests?
When a guest submits a request, the following workflow begins:
Notification: You receive an immediate alert via your preferred channel, including a direct email with a one-click Approve button.
Review: Go to Reservations → Requests in your dashboard to view guest information, requested dates, and pricing.
Action: Click Approve to confirm the booking (the guest is charged automatically) or Decline to reject it.
Personalization: Include a custom message to welcome the guest or ask follow-up questions before approving.
Important: You have 72 hours from the date of the request to approve or decline. If no action is taken within that window, the request is automatically voided and the guest is notified that the booking did not go through.
Best Practices
Act within 72 hours. Requests automatically void after the window closes, costing you the booking. Set up email and mobile notifications so you never miss one.
Respond promptly. Even though you have 72 hours, aim to respond within 24 hours to prevent guests from booking a competitor's property while they wait.
Set expectations. Clearly state in your listing description that bookings are subject to approval so guests aren't surprised by the extra step.
Use messaging to clarify. If anything in the request is unclear (group size, purpose of the trip, pet details), message the guest before approving.
Monitor actively. Check your dashboard daily to catch pending requests before they expire.
