Booking page
Configure your public booking page at /book/<your-workspace-slug>.
Edit the question catalog, pick the page layout, write an intro, and
toggle whether bookings auto-create leads. The same page manages your
hosted lead form at /f/<your-workspace-slug>.
How do I find my booking URL?
your-domain.com/book/<slug> where slug is your workspace's URL slug (set on Settings → Workspace). The page is public — no login needed. Share it on your website, in your email signature, anywhere a prospect might click.What's the difference between single-page and multi-step?
Why would I turn off "auto-create lead"?
What timezone do prospects see the times in?
Why didn't a booking set the lead's insurance type?
insurance_type key is a text field instead of a dropdown or multiple choice. Or auto-create lead is switched off. In every case the raw answer is still saved on the appointment itself, so nothing is lost. See the policy-type question below.What's the difference between the booking page and the lead form?
/book/<slug>) makes the prospect pick a time slot and puts an appointment on your calendar. The lead form (/f/<slug>) only asks for contact details and the coverage they want, then creates a lead. Use the form where a calendar would scare people off: a Facebook bio, a QR code on a flyer, a text-message reply. See Lead form below.Can I add a file-upload question?
The question catalog
Each row is one custom question. Name + first/last name + email + phone are built in and always required — you don't add them here. Drag rows to reorder. Add a row with + Add question, picking a field type. For dropdown and multi-choice, list the options one per line. Required toggle gates the public form's submit button.
Appointment types
Exactly one row of type "appointment type" per workspace (the system enforces the limit). Its options carry both a label ("Discovery Call") and a duration in minutes ("15"). The booking page shows these as the meeting-type picker. New workspaces get a default catalog of four types (Discovery Call, Strategy Session, Policy Review, Join the Team) seeded the first time someone hits the booking URL, along with the policy-type question described below.
The policy-type question
New workspaces also get a second default question: "What kind of coverage are you looking for?" with the choices Term Life, Final Expense, Medicare, and Not sure yet. It is optional, so a prospect can skip it. When they do pick a product, the booking saves that answer as the lead's insurance type, the same field you filter the leads list on. If the lead already exists and has a type, the new answer is added to it rather than replacing it. "Not sure yet" counts as no answer and leaves the insurance type alone.
What makes this question special is its field key, insurance_type.
Any dropdown or multiple-choice question with that key behaves the same
way, so feel free to rename the question or swap the options for the
products you actually sell. Only one question per page can carry the key.
A short-text or long-text question with the key is ignored on purpose,
because typed answers would turn the insurance type field into a mess.
If your booking page predates this feature it won't have the question yet. Open Settings → Booking page and click + Policy-type question. That adds the dropdown with the key already filled in. Edit the options if you want, then save. The button greys out once any question on the page has the key.
Intro copy
Optional paragraph above the form. Use it for a quick welcome, expectations for the call, or to set a tone. Plain text, up to 2000 chars.
Layout
Single-page or multi-step. Both render against the same workspace branding (your logo, accent, brand name). Switching layout doesn't change the form fields or the submission handling — just how the page is arranged.
Tracking where bookings came from
If someone reaches your booking page from a link that carries tracking tags
(utm_source, utm_campaign and so on, or a Google
Ads click ID), those tags are saved on the lead their booking creates. The
trackable links in Marketing studio captions
work this way, which is how Marketing → Results can tell you which posts
brought in leads. Nothing is saved when auto-create lead is off.
Lead form
The second card on this page, Lead form, gives you a public
page at your-domain.com/f/<slug>. It asks for first and
last name, email, phone, the kind of coverage the person wants (your own
insurance-type list plus "Not sure yet"), and an optional message. There is
no calendar step; whoever fills it in becomes a lead in your pipeline right
away.
The card has three settings. A Lead form is live checkbox, on by default; untick it and the link shows a "Form not found" page until you turn it back on. An intro of up to 2,000 characters shown above the fields. And a thank-you message of up to 500 characters shown after someone submits; leave it blank and the page says "Thanks — we'll be in touch shortly." All three save with the same Save booking page button as the rest of the page.
Each submission creates a lead (or updates the existing one if the email
is already in your workspace) and tags it with the hosted_form
source. The coverage pick lands on the lead's insurance type unless it was
"Not sure yet". The message is saved as a note on the lead. The person is
added to your email subscribers, you get the new-lead notification, and
they get the confirmation email. Workflows that fire on
lead_created or on the hosted_form source run as
usual. Tracking tags on the link (utm_source,
utm_campaign and so on, or a Google Ads click ID) are saved on
the lead the same way the booking page saves them.
Bot protection matches the booking page: a hidden trap field, a per-address rate limit, and Turnstile when your deployment has it configured. Submissions count toward your plan's lead quota like API leads do. Once the quota is used up, the page tells visitors to try again later rather than silently dropping what they typed.
What the page does
When someone submits: the system validates the answers, creates an appointment row, optionally creates or updates a matching lead, picks an available agent (Team plans), creates the Google Calendar event, sends the confirmation email to the booker, and sends a notification email to the agent. A confirmation page renders without redirecting (so refresh doesn't re-submit).