Held until 14:32 — the calendar that locks itself, and lets go

A guest taps book at 14:17. From that second, one promise appears right in the booking flow: your price and dates are held for 15 minutes. Until 14:32, those nights and that price belong to this guest — and to nobody else. This is the small piece of machinery that promise stands on.

What the guest sees

Before the payment step, the booking card says it plainly: the price and the dates are held for 15 minutes once you continue to payment. No fine print, no "subject to availability" hedge at the end. The number the guest saw is the number the guest pays, and the dates cannot be taken by someone else mid-payment.

What actually happens

The moment payment starts, a 15-minute hold is placed on those dates. Not before: while anyone is browsing dates or checking a price, nothing is held and nobody is blocked. The hold is enforced at the database level — the calendar can be held by exactly one party at a time. It is not a policy or a best effort; a second booking attempt for the same nights is refused by the same machinery that stores the first one.

The same hold travels outward. Your calendar is connected to the external booking platforms through a two-way API connection, so the dates close there as well while the payment is in progress. One guest, one hold, one calendar — regardless of how many places the stay is listed.

Then one of two things happens. The payment completes: the stay is confirmed, and the nights are booked everywhere. Or the guest walks away: the hold expires on its own, and the calendar reopens — on your website and on the platforms — automatically. You never clean up after an abandoned checkout.

What an AI agent holds — and what it doesn't

An agent that is only looking holds nothing at all. Asking your website for a price is a read: it returns a signed offer carrying its own validity time — how long that exact price is guaranteed — and touches no calendar. A hundred agents can price the same week in the same second without closing a single night to anyone. The validity time is a promise about the price, not a claim on the dates.

The hold begins where it should: at payment. When an agent pays on a guest's behalf, the same database rule applies — one party at a time, and no double-booking window to reason about. Because an agent's payment goes through instantly, rather than a person typing card details, its hold is shorter: around two minutes, against fifteen for someone at a checkout page. Agents get the same guarantee and hand the calendar back sooner.

August 2026: the sync went direct

This month the calendar connection reached the point the promise depends on. The sync with the external booking platforms is a direct two-way API connection: a booking made on a platform blocks your website within seconds, and bookings on your website close the platform calendars within minutes. Turnaround days around each stay close automatically, your minimum-stay rule applies everywhere, and the price you set applies everywhere — the platforms' own costs are added on top automatically, so your direct price stays your direct price and you never adjust anything by hand.

That is what "your own booking website" should mean: you set the rules once, and they are true everywhere — for guests who find you directly, for guests who come through a platform, and for the AI agents in between. Direct guests pay your real price, at 0% commission.