How holds, deposits, and bookings work — and how Autotelic books a date

A hold reserves something — a date, a room, a time slot — for a short window without full payment, so someone has a chance to confirm before the reservation is given away. A deposit or a fixed-price booking goes further: it turns a quoted service into a paid commitment on both sides, at a price set in advance rather than negotiated after the fact. Both patterns only work if the system enforces its own promises — a hold that never expires isn't really a hold, and a fixed price that changes at the register isn't really fixed.

A newer pattern is letting an AI agent book directly, not just a person clicking through a page — which only works safely if the agent's tools are narrow and read-only where it counts: it can see what's available and reserve it, but it should never see or move a card number itself.

Autotelic's booking system holds a slot for a set window, generates a Stripe-hosted pay link for anything requiring payment, and tracks orders through that pending state until they're paid or the hold expires. For AI agents specifically, a documented set of tools exists to list rooms, list open slots, place a hold, and generate a pay link — with no card fields ever passing through the agent's hands.

Booking a BARna room — Autotelic’s own venue — works this way live today, and a handful of fixed-price service SKUs, like a Level 2 EV charger install, are bookable the same way regardless of project type.

The booking system itself doesn’t care what kind of project it’s attached to — an ADU, a home remodel, a new build, a commercial tenant finish or a venue can all use a fixed-price SKU where one exists; venue bookings are simply where it runs most fully today, because BARna’s rooms are Autotelic’s own to book.