Help / Event types

Booking questions

Every event type has a booking form, the short form an invitee fills in after they pick a time. It always collects the basics, and you can add your own questions on top.

What it is

• Standard fields: the invitee's name and email are always asked. The Booking Form tab also has a Name Format option, an Autofill toggle, an Allow guests toggle (extra email addresses on the booking), a Disable rescheduling by guests toggle, a Hide from my profile toggle, a Hide from search engines toggle (keeps this event type's booking page out of search results, though the link itself keeps working), and a Show SMS opt-in toggle (see SMS opt-in below).
• Custom questions: questions you add yourself. Each has a label, a type, and whether it's required:
  • One line / Multiple lines: short or long free text.
  • Number: numeric answers.
  • Phone number: a phone field.
  • Radio / Dropdown: pick one from a list of options you define.
  • Checkboxes: pick any number from a list.

The answers are saved with the booking and shown to the host (on the meeting details, in the confirmation email, and, if you use a calendar title template, they can be pulled into the calendar event title).

Zoom

SMS opt-in

Turn on Show SMS opt-in when a workflow sends texts to invitees of this event type. The booking page then shows a Send me text messages about this booking checkbox, with the note "Message and data rates may apply." It works the same on personal and team booking pages.

• Where it appears. If the form has a Phone number question, the checkbox sits right under the first one, and ticking it makes that question required. If it has none, ticking the checkbox reveals a required Mobile phone field.
• Always unticked. The checkbox starts unticked on every visit, and autofill never ticks it for a returning invitee. Consent is given per booking.
• A valid number is required. The phone must be a real number in international format (with the country code). Invitees who tick the box without one are asked to enter it before they can book.
• What it controls. SMS to invitee workflow steps text only invitees who ticked it. Email is not affected, and guests never get texts.
• Stopping later. An invitee who opted in sees a Stop texts button on the booking's cancel and reschedule pages.

On a managed event type the toggle comes from the template and can't be changed on the copy.

When to use it

• Qualify the meeting up front: "What would you like to discuss?", "What's your company?", "Team size?".
• Collect something you need before the call: an account ID, a phone number, a link to review.
• Keep it short, because a long form hurts conversion. If you want to route people to different places based on their answers, that's a job for a routing form, not a pile of booking questions.

How to do it

1. Open the event type from Event Types and go to its Booking Form tab (see the editor overview).
2. Add a question: set the label, choose the type, and for radio / dropdown / checkboxes, list the options.
3. Mark it required if the invitee must answer it.
4. Reorder questions by drag (the order is the order invitees see them).
5. Set the form options at the top of the tab (name format, allow guests, SMS opt-in, etc.) as needed for this event type.
6. Save, and the new form is live on that event type's booking page immediately.

Common pitfalls

• Form too long → fewer bookings. Ask only what you genuinely need before the meeting. Everything else can wait until you're talking.
• Required questions block booking. A required question with no good "n/a" option can stop people who don't have an answer. Make it optional, or add a catch-all choice.
• "Hide from search engines" is not access control. It asks search engines not to index the booking page (a noindex signal), but anyone who has the link can still open it and book. To take a page out of circulation, turn the event type off instead. (Event types marked "hide from my profile" are already kept out of search results automatically.)
• Questions that qualification rules depend on. If this event type has qualification rules, turning a question off makes every condition that uses it stop applying, and deleting the question blocks the save until you remove those conditions.
• Using questions for routing. Booking questions don't change where someone goes; everyone who opens the link books the same event type. To send people to different places based on their answers, use a routing form.
• SMS workflow set up, but no invitee gets texts. Show SMS opt-in is off, so nobody can give consent. Turn it on here.