Payments & scheduling
Take the money and the time slot, in the form.
Most form builders stop at collecting an answer, so the booking happens over email and the deposit happens a week later, if at all. A payment question and an appointment question are ordinary blocks here: the respondent pays, picks a time, and that time is gone. Both are on Pro.
Your Stripe, your money
Connect your own Stripe or PayPal account and the money goes straight from the payer to you. We never hold it and take no percentage. Card details never touch a CrispForms page either, because checkout happens on the provider's own hosted page.
A live slot grid, not a date box
The respondent sees the times you are actually free and picks one. Nobody types a date you then have to decline. No Google Calendar to connect, no Zoom, no OAuth screen: availability lives in the block.
Hours the way you would say them
Weekly hours with more than one window a day, so a lunch break is two rows. Appointment length, a gap after each one, how much notice you need, how far ahead the calendar opens, and the dates you are simply closed.
Two clocks, always
You write your hours in your own timezone. Everyone booking sees the times on theirs, with yours named beside it. What gets stored is the instant, so nothing drifts when the clocks change and nobody turns up an hour early in March.
One appointment, or a class
Places per slot defaults to one, which is an ordinary appointment. Set it to twelve and the same block runs a workshop, a group session or a class, counting the places down as they go.
The slot is really gone
Two people submitting in the same instant cannot both get three o'clock. The database decides, not a check that ran a moment earlier, and the person who loses is told immediately with everything else they typed still in place.
A calendar file, not an integration
The confirmation carries a .ics, so the appointment lands in Google Calendar, Outlook or Apple Calendar without either of you connecting anything. It is a file. Everything opens it.
Deposits, against no-shows
Put a payment question next to the booking one and you are taking a deposit at the moment somebody decides, rather than chasing it afterwards. That single change does more about no-shows than any reminder.
Questions