Checkout offer
Shown on your booking engine the moment a guest hesitates at checkout.
Converstay follows up with every guest who leaves your Cloudbeds booking engine, with the room, dates and rate they chose, in their language. Then it shows you each booking that came back.
These guests chose a room, picked dates and typed their email. Cloudbeds shows the nights as empty. Converstay shows who almost filled them, and follows up.
Shown on your booking engine the moment a guest hesitates at checkout.
Guests who aren't ready save the stay to their inbox. You keep a way to reach them.
From your domain, in the guest's language, with their exact stay and a link back to it.
This is the dashboard your team gets, with sample data. Each recovered booking is matched to its Cloudbeds reservation; cancellations and bookings we can't match are shown, never counted.
The Converstay dashboard with sample data. Click around: the sidebar, guests and bookings all open.
Three ways a hotel can handle the guests who leave its booking engine.
| Compared on | Do nothing | Generic cart email | Converstay |
|---|---|---|---|
| Follows up with guests who leave | Nobody does | A generic “you forgot something” | Their exact room, dates and rate |
| In the guest's language | — | One language | Spanish, English and more |
| Counts only real bookings | — | Cancellations counted as wins | Matched in Cloudbeds |
| On the booking engine itself | — | Nothing | Checkout offer and Send My Stay |
| Cost a month | About $72,000 in lost bookings | A fee, plus what it misses | $199 flat |
Most guests who start a booking leave before paying: SaleCycle put it at 84.6% for hotels in 2019. Your booking engine keeps no trace of them, and the ones who come back through an OTA cost you 15–30%. Put in your own numbers.
Run Converstay on your own guests for a month. If the dashboard doesn't show more in recovered bookings than it costs, walk away.
$199per hotel, per month after the trial. No setup fee, no contract.