INSTANT BOOK VS REQUEST TO BOOK
Instant Book vs Request to Book: Which Should You Use?
One fills rooms faster. The other gives you the final say. Most properties need both, on different dates.
For independent hotels, homestays and resorts in India.
THE SHORT ANSWER
Which one suits your property
Instant book suits you
Standard rooms at a set rate.
Low risk if a guest is a poor fit.
You want the booking closed at 11 pm.
It depends
Mixed inventory.
Peak dates with high demand.
Rates that move week to week.
Request to book suits you
Whole-property or large group bookings.
Festive, wedding and long-weekend peaks.
You need to vet who stays.
If you only ever pick one, most small properties are better off with instant book for ordinary dates and request to book for peak ones.
WHY THIS PAGE EXISTS
The choice is usually made by default, not on purpose
Most properties never choose. They take whatever their listing platform switched on, or they leave every booking as a request because approving things feels safer. Both defaults cost something. Leaving everything on request loses the guest who was ready to pay at midnight. Leaving everything instant means a stranger can hold your best room on your busiest weekend before you have looked at the dates.
This page is about making it a decision instead of a habit, and being specific about when each mode is the wrong one.
THE SHORT VERSION
What actually separates the two
Instant book means the guest picks dates, pays, and the room is confirmed without you touching it. Request to book means the guest asks, you approve or decline, and only then does it become a booking.
Everything else follows from that one difference. Instant book trades control for speed. Request to book trades speed for control. Neither is safer in general. They are safer in different situations.
For the mechanics of each, how to set them up and what a good setup includes, see the instant booking and request to book explainers.
THE REAL TRADE-OFF
What each mode costs, in plain terms
What request to book costs you: bookings you never hear about
Every hour a request sits unanswered is an hour the guest spends looking elsewhere. Guests booking late at night, or comparing three properties at once, book whoever confirms first. The cost is invisible, which is exactly why it gets ignored. You never see the guest who moved on. Instant confirmation is also now the norm on most major listing sites serving India, so a property that makes everyone wait is going against what guests have been trained to expect.
What instant book costs you: the right to say no
The room is gone before you have seen the request. For a standard room on an ordinary Tuesday that is fine. For your best cottage on 30 December, or a group of twelve arriving for a wedding, it means you have lost the chance to ask who is coming and how many people will actually stay.
The asymmetry that decides most cases
Ask what it costs when a booking is wrong. If a poor-fit guest in a standard room is an inconvenience, use instant book. If a poor-fit booking on a peak date costs you the most valuable night of the year and cannot be resold, use request to book for those dates.
THE FOUR QUESTIONS
Four questions that decide it for your property
1. What does one bad booking cost you on this date?
On an ordinary weekday, very little. On a festive weekend, possibly the whole month’s margin. This is the question that settles most cases, and the answer changes by date rather than by property.
2. How fast can you actually answer?
Request to book only works if someone replies quickly. If requests sit until morning, you are not choosing control. You are choosing to lose the late-night booker and calling it control.
3. Are you selling a room or the whole property?
Whole-property and large-group bookings almost always deserve a look before they confirm. A single standard room rarely does.
4. Does the guest genuinely need vetting?
Some properties do, family-only homestays and quiet retreats among them. Most standard rooms do not, and adding an approval step there only adds delay.
SIDE BY SIDE
Instant book and request to book, point by point
| Instant book | Request to book | |
|---|---|---|
| Booking is confirmed | Immediately | After you approve |
| Late-night bookings | Captured automatically | Usually lost unless you reply fast |
| Control over who stays | None at the time of booking | Full |
| Best for | Standard rooms, ordinary dates | Peak dates, groups, whole property |
| Risk on peak dates | A stranger can hold your best night | You choose |
| Effort per booking | None | A reply, every time |
| Guest experience | Fastest, no waiting | Slower, some guests drop off |
| Conversion | Higher | Lower, and falls as reply time grows |
| Payment | Taken at booking | Taken after approval |
| Suits a fast responder | Not required | Essential |
| Cancellation exposure | Set by your policy | Set by your policy |
| What it does not fix | Pricing or demand | Pricing or demand |
The last row is deliberate. Neither mode creates demand. If rooms are not selling, this is not the setting to change.
TWO REAL SHAPES
The same question, answered two different ways
A five-room homestay in Coorg
Standard rooms, one rate per season, mostly couples and small families. Instant book on all ordinary dates, because the owner is not adding anything by approving a two-night stay in a standard room, and every hour of delay costs bookings. Request to book switched on for the Christmas and New Year window only, where one wrong booking costs the year’s best night.
A twelve-room property in Udaipur
Individual rooms on instant book through the quiet months. Anything that books four rooms or more, or falls inside the wedding season, goes to request to book, because a group booking needs a conversation about numbers, timings and whether the property is actually the right fit.
BEING FAIR TO BOTH SIDES
What each one gets right, and where it falls short
Instant book
Where it helps: it closes the booking at the moment the guest decided, including at midnight, and it removes a task from your day entirely.
Where it falls short: you find out who is coming after the room is committed, and on a scarce, high-value date that is a real risk.
Request to book
Where it helps: you keep the final say, which genuinely matters for groups, whole-property bookings and peak dates.
Where it falls short: it costs you bookings quietly. Every hour of delay loses guests, and if approvals wait until morning you are paying for control with revenue you never see.
AN HONEST SELF-CHECK
Signs you have the setting wrong
- Guests tell you they booked elsewhere while waiting to hear back.
- You approve almost every request without changing anything, which means the approval step is only adding delay.
- A peak date has been taken by a booking you would have declined.
- Requests routinely sit unanswered overnight.
- You run the same setting in December that you run in July.
The last one catches most properties. The setting that is right in a quiet month is often wrong in a busy one.
WHERE THIS DECISION GOES WRONG
Three things people get wrong about this choice
“Request to book is the safer option”
It is safer against one risk and worse against another. Approving every booking protects you from the guest you would have turned away. It does not protect you from the four guests who booked somewhere else while waiting. Both are real losses. Only one of them shows up in your inbox, which is why owners consistently overrate the first and ignore the second.
“Instant book means giving up control”
The control you give up is narrower than it sounds. You still set the rate, the minimum stay, the advance you collect and the cancellation terms, and those decide most of what a booking is worth to you. What instant book gives up is the say over who, not over what. On a standard room that is usually a fair trade. On your best room at New Year it is not.
“It is a setting you choose once”
This is the mistake that costs the most. The right answer changes by room and by season. A property that runs instant book all year loses control exactly when control is worth most, and a property that runs request to book all year loses bookings for eleven months to protect one.
GOT QUESTIONS?
Answers to frequently asked questions
Which converts better, instant book or request to book?
Instant book, consistently. The gap widens the longer requests take to answer, because guests comparing several properties book whoever confirms first.
Should I use both, and how do I split them?
Yes, and most properties should. A practical split is instant book for standard rooms on ordinary dates, and request to book for peak dates, group bookings and whole-property stays.
Does request to book reduce cancellations?
Not by itself. Cancellations are governed by your policy and whether you take an advance, not by who confirms the booking.
How fast do I need to answer a request?
Faster than it feels. Treat anything beyond an hour on a same-week booking as a booking you are likely to lose.
Is instant book risky for a homestay?
For standard rooms, rarely. The risk concentrates in whole-property bookings, large groups and scarce peak dates, which is exactly where request to book earns its place. The instant booking explainer covers the safeguards worth setting up.
Does the payment work differently?
With instant book the payment is taken as the booking is confirmed. With request to book it is taken after you approve, so an unapproved request holds nothing. That difference matters most on peak dates.
What happens on a busy weekend if I use request to book?
You keep control, but you have to be reachable. An unanswered request on a busy weekend is the worst of both, because you lose the booking without ever making a decision.
Which does OpenStays support?
Both, per room and per date range, so a property can run instant book through quiet months and switch to request to book for its peak window.
Pick the setting per date, not once for the year
The properties that get this right are not choosing a side. They are choosing per room and per season, and reviewing it once a year.