Direct bookings tripled with Direct Booking Booster for SiteMinder
Starting point
Peppermint Boutique Sydney is a 42-room boutique property in Surry Hills. In early 2025 the property was running SiteMinder as its channel manager and booking engine, with an OTA share of 79% — Booking.com dominant, Expedia secondary, small tail on Agoda and Hotels.com. Direct bookings represented 21% of stays and roughly 24% of net revenue after commission.
What Rmsclaud deployed
The property activated Direct Booking Booster for SiteMinder in April 2025. The module was configured with abandoned-cart recovery via email (20-minute delay), a best-rate guarantee badge sourced from the property’s own SiteMinder-distributed OTA rates, and scarcity signals for room types with less than three units left. Activation took 11 minutes end to end via the property’s SiteMinder login. No changes were made to SiteMinder rate plans; nothing was migrated.
Result after six months
By October 2025 direct bookings had risen to 61% of stays and 68% of net revenue. The GM attributes the shift to a combination of the abandoned-cart flow (which alone recovered 187 stays in the first quarter) and the best-rate guarantee badge, which reduced the rate of OTA-referred visitors continuing on to Booking.com to complete the reservation.
“We did not change anything about how SiteMinder was configured. We added the module and left it alone for two weeks to gather data. It works.”
— Isabella Chen, GM
Numbers, at a glance
- Direct booking share: 21% → 61% of stays over six months
- Net revenue direct: +185%
- OTA commission spend: -34% in dollar terms despite growing overall revenue
- Module cost across six months: AU$234
Sync error rate cut 92% with Channel Sync Watchdog
Starting point
The Chester Norwich is a 28-room independent hotel in the historic centre of Norwich, UK. Prior to 2025 the property used SiteMinder to distribute across Booking.com, Expedia, Agoda, Hotels.com, and a local UK travel agent. Rate-plan sync errors — usually caused by out-of-band changes in the OTA extranets — were happening on average eight times per week, of which two per week were only discovered by a customer complaint or a phone call from the OTA.
What Rmsclaud deployed
The property activated Channel Sync Watchdog for SiteMinder in February 2025 with alerts routed to Slack and to the revenue manager’s mobile. Activation took under three minutes via the existing SiteMinder login. The Watchdog polls every SiteMinder-connected OTA every two minutes and raises an alert within the same window when a rate, availability, or restriction drifts out of sync.
Result after four months
Between February and June 2025 the property saw its total number of undetected sync errors fall from an average of eight per week to fewer than one per fortnight — a 92% reduction. Median detection time on residual errors dropped from about 26 hours to under 4 minutes. Booking.com support tickets fell to zero across the whole quarter.
“We used to firefight rate parity twice a week. The Watchdog put a stop to it. It is the cheapest module I have ever paid for that changed our day-to-day.”
— Harriet Blackwood, Revenue Manager
Numbers, at a glance
- Weekly sync errors surfaced by a guest complaint: 2 → 0.5
- Median detection time on residual errors: 26 h → 4 min
- Rate-parity Booking.com support tickets that quarter: 5 → 0
- Module cost across four months: £48 equivalent