Booking

Booking turns a flow into a scheduling experience: visitors pick a time, the slot is reserved, and a calendar invite goes out. It runs on a real booking engine, and it shares the same flow model as forms — so everything you know about building forms applies.

How booking works

A booking flow lets a visitor:

  1. answer any qualifying questions you add (the same typed fields as a form),

  2. choose an available time slot,

  3. confirm — the slot is held and then booked, and both sides get a calendar invite.

Behind the scenes, availability, slot holds, bookings, and calendar invites are handled for you. Reschedules, cancellations, and no-shows flow back automatically.

Where booking renders

Like forms, a booking flow renders at the canonical URL:

https://<your-site>/f/<flow_id>

You can also embed a booking widget directly inside a SpiderPublish page using the {% booking %} tag, so visitors can schedule without leaving the page.

Building a booking flow

Create the flow as a booking type, add any qualifying questions, set it up, and publish. Publishing provisions the scheduling pieces automatically the first time. After that, the booking page is live at its /f/<flow_id> URL.

Submissions and your CRM

Bookings are captured like form submissions and flow into your CRM, so a booked meeting becomes a contact and a record you can follow up on. You see bookings in the flow's responses, the same place form submissions appear.

Tips

  • Keep qualifying questions short. A couple of fields before the calendar is plenty; long forms reduce bookings.

  • Set a clear thank-you. Tell people what happens next after they book.

  • Embed where intent is high. A {% booking %} widget on your pricing or contact page captures interest at the moment it peaks.

Next steps