Permission to Vet
How Booking.com Finally Fixed Its Trust Problem
Booking.com's "Request to Book" feature sounds like a dream for professional property managers. Screen your guests. Control your calendar. Maintain standards.
The reality is more complicated. While RTB offers genuine control benefits, the hidden costs in visibility, conversion, and ranking can devastate your Booking.com revenue if you implement it wrong.
The Control vs. Conversion Trade-Off
As of early 2026, Booking.com has fully operationalized Request to Book globally. According to Rental Scale-Up's analysis of Booking.com's Q2 2025 earnings, 70% of listings remain instantly bookable. RTB is positioned as a specialized tool, not a replacement for Instant Book.
The platform expanded RTB specifically to onboard professional managers who need to screen guests or manage complex inventory risks. But the feature comes with constraints that can kill your performance.
Get more insights like this
Weekly STR tech updates. No spam.
The 24-Hour Double Loop
The RTB process on Booking.com is different from Airbnb, and the differences matter.
According to Rentals United's detailed breakdown:
- 24-Hour Host Window: You have 24 hours to accept or decline. No action means automatic expiration.
- 24-Hour Guest Confirmation: After you accept, the guest also has 24 hours to finalize. The calendar is not blocked during the initial request, leaving it open to other bookings.
- Price Recalculation: The final price is calculated at confirmation, not request. If dynamic pricing updates rates during that window, the guest may see a different price and abandon.
The Last-Minute Visibility Kill
Here's the constraint that most operators miss: according to Booking.com's API documentation, RTB properties are invisible for searches with check-in within 3 days.
If a property relies on last-minute bookings (0-3 day window), enabling RTB effectively removes it from search results for that high-intent audience.
The Ranking Algorithm Problem
Booking.com's ranking algorithm is explicitly "optimized for conversion". It prioritizes listings that turn lookers into bookers most efficiently.
RTB introduces multiple drop-off points:
- Host delay
- Host rejection
- Guest failure to confirm
A lower realized conversion rate compared to Instant Book competitors naturally results in lower organic ranking. According to Rentals United's ranking guide, if a user filters for "instant confirmation" (a common behavior), RTB properties are immediately excluded.
Where RTB Actually Makes Sense
The feature has successfully unlocked high-value inventory. Rentals United reported single bookings via RTB reaching over €78,000, proving that high-net-worth guests navigate the request friction for the right properties.
| Portfolio Segment | Recommended Mode | Rationale |
|---|---|---|
| Luxury Villas / High-End | Request to Book | High ADR justifies friction; screening is mandatory |
| Urban / Short-Stay | Instant Book | High reliance on last-minute demand; volume-based model |
| Complex / Multi-Owner | Request to Book | Prevents double-bookings; allows owner approval |
| Standard Vacation Rental | Instant Book | Maximizes ranking and conversion |
The Operational Risks
According to Hostaway's support documentation:
Response Time Failures: Missing the 24-hour window results in automatic decline, which negatively impacts your performance score and future ranking.
Price Discrepancies: A guest might request at $500, but if dynamic pricing raises the rate to $550 before they finalize, they may abandon. This creates a "silent" conversion killer unique to Booking.com RTB.
Messaging Constraints: Some API connections note that messaging a guest while a request is pending approval may return errors, limiting your ability to build trust during the decision window.
The 2026 Payment Enhancement
Looking ahead, Hostaway reports that property managers using "Payments by Booking.com" will gain the ability to request pre-authorized payments in 2026. This adds security for high-risk inventory, making RTB more viable for luxury properties.
Booking.com also shares specific guest signals to aid approval decisions:
- Years using the platform
- Past misconduct history
- Domestic vs. international trip
- Email and phone verification status
The Implementation Rules
If you're going to use RTB, do it right:
1-Hour SLA: Implement an internal response time target of 1 hour during business hours. Relying on the full 24-hour window kills conversion.
Weekend Coverage: Ensure staff availability 7 days a week. Requests expiring over weekends destroy your performance score.
Price Locking: Configure pricing tools to avoid aggressive intraday rate changes on RTB units.
Visibility Booster: Use Booking.com's Visibility Booster tool (commission override) during low-demand periods to offset the natural visibility drag.
The Test Protocol
Before full rollout, run a cohort test:
Compare RTB listings against similar Instant Book listings for 4 weeks. Monitor:
- Net Revenue: Does higher ADR on RTB offset volume loss?
- Rejection Rate: Keep below 5% to protect ranking
- Auto-Expire Rate: Must be 0%
The Bottom Line
Request to Book is a specialized tool for high-stakes inventory, not a default setting. The operators who win on Booking.com understand that control has a cost, and they deploy RTB surgically rather than broadly.
For most properties, Instant Book remains the path to maximum visibility and revenue. RTB should be reserved for luxury units where booking values justify the friction and where the 3-day visibility blackout doesn't matter.
Discussion