From request to confirmed booking
Workflows · Workflow 1 of 6
Last synced 2h ago
Not connected
How a client goes from the Book form to a confirmed, paid session. Vik's rule (Oct 7, 2026): he isn't involved until the deposit is paid, then he reviews every request himself. Every check runs in the Worker's tools, so the website and the assistant follow the same rules. Deposits are test payments until Square checkout is switched on.
Step (built)DecisionBooking stateEmail to the clientNot built yet
Yes / No branches◷ timing
1 · Request and private link No one waits on Vik: the client gets their link straight away.
2 · Pick a date, hold it, pay the deposit The private link only offers dates that pass every rule.
3 · Vik reviews the paid request Approve keeps it; decline cancels it and refunds the deposit.
Booking states: held (48 hours, unpaid; never past 24 hours before the session) → confirmed when the deposit lands in time, with Vik's review pending → approved, or declined (cancelled, refunded) · expired when the 5-minute cron finds the hold past its time · released when the client holds a different date or Vik cancels an unpaid hold. Picking a new date always releases their earlier hold, so a client never blocks two dates. Touch-ups don't go through here: the client messages @cozyinkz and Vik books it (
book_touchup).Wide diagram: scroll sideways, or pinch to zoom on a phone.