Early check-in and late check-out sit under one master toggle in Settings, then Upsells, and are configured with identical, mirrored controls. Scope, the acceptance window, exceptions, the night-blocking rules, pricing by extension length, proactive offers and holiday exceptions all work the same way for both, with check-out substituted for check-in.

Two things read differently for late check-out, and they are the reason this page exists.

For early check-in, blocking protects the night before arrival. For late check-out, it protects the night of departure.

That difference matters operationally. Choosing never to block carries more risk here than it does for early check-in, because a late check-out can run into the arrival of the next guest on a same-day turn. Your departing guest is still in the property while your arriving guest is on the way.

If you sell late check-out on properties that turn over frequently, the middle option, blocking only when the extension is long enough to matter, is usually the sensible setting.

The acceptance window has a cutoff for a reason: it stops your cleaners being told about an extended departure with no time left to re-plan the turnover.

If Besty is declining late check-out requests you would have accepted, the acceptance window is the setting to widen, not the pricing. This is the most common misdiagnosis on this feature. The request is not being turned down because of cost, it is being turned down because it arrived after your cutoff.

The other common reason Besty goes quiet on a late check-out conversation is that no valid option exists at all, typically because a back-to-back reservation blocks the dates.

For the full walkthrough of scope, exceptions, pricing, proactive offers and the Airbnb payment behaviour, see How do I configure the Early Check-In and Late Check-Out upsells? Everything there applies to late check-out too.

Reach out via chat or at support@getbesty.ai.