Set in the Availability step of the service builder.
Weekly schedule
A day-by-day list where you mark each day as unavailable or add one or more time windows (up to 5 per day). This is what actually controls which start times a guest can pick — the guest booking screen only ever shows times inside these windows. Defaults to Monday–Friday 08:00–20:00, weekends unavailable.
Advance notice (lead time)
This is meant to set how much notice you need before a booking starts (e.g. “2 hours”).
This isn’t enforced as a booking cutoff today. A guest can technically still book a slot that starts sooner than your configured advance notice — nothing in the app currently blocks it. The one place this setting does show up: it’s used to calculate the cancellation deadline shown to the guest (e.g. “cancel by this time for a refund”). Don’t rely on it to prevent last-minute bookings — keep an eye on new requests instead, and reach out directly if timing is tight.
Time between bookings (buffer)
Meant to block out recovery/travel/setup time after a booking (e.g. a 60-minute service with a 30-minute buffer would block 90 minutes total).
This also isn’t enforced today. It’s stored on the service, but nothing currently uses it to prevent overlapping or back-to-back bookings. If your provider needs real recovery time between jobs, manage that manually when assigning requests for now.
Bottom line
Today, your weekly schedule is the only setting that actually limits what a guest can book. Advance notice and buffer time are there for when stricter enforcement ships — treat them as notes to yourself, not guarantees, for now. 