Booking pages

Define the kinds of meetings people can book — each with its own length, location, availability, buffers, and intake questions.

Updated 4 min read

A booking page (event type) is a kind of meeting people can book with you — a "30-minute intro call," a "60-minute strategy session," a "15-minute demo." You can have as many as you need, each configured independently. Create and edit them from your scheduler settings.

Configuring a booking page (event type)

The essentials#

Each booking page has a name, a subject (which can include the invitee's name), a description, a duration, and a color. Toggles control whether it's active and whether it's listed on your public page.

Web address#

Every booking page has its own web address — the last part of the link people use to book it, shown right under the name as you edit. A new page takes its address from its name (an "Intro Call" becomes …/book/you/intro-call) until you type your own; lowercase letters, numbers and hyphens are allowed. Renaming a page later never changes its address, so links you've already shared keep working.

You can change the address on purpose at any time. When you do, the old link stops working — anyone holding it needs the new one, and an embed that names the page by its address needs updating too. Two of your pages can't share an address, and an address that belonged to a page you deleted stays retired.

Duplicating a page#

Built a page with the right questions, buffers and reminders and want a 60-minute version? Use Duplicate in the page's ⋯ menu on Booking page settings. The copy carries every setting, intake question and conflict calendar, is named "… (copy)", gets a fresh web address, and starts turned off so nobody can book it before you've adjusted it. Existing bookings stay with the original.

Location#

Choose how the meeting happens:

  • In person (with a location detail), phone (you call them, or they call you), a Google Meet or Microsoft Teams link (created automatically), or a custom URL.

Availability and conflict checking#

  • Pick which availability schedule governs when this event can be booked (see Availability & settings).
  • Choose which calendars to check for conflicts, so a time you're busy on any of them is never offered.
  • Choose which calendar the booked event is written to.

Timing controls#

Fine-tune when and how often people can book:

  • Buffers before and after the meeting.
  • A minimum notice so no one books you in five minutes.
  • The slot increment (how times are spaced).
  • A date window — a rolling range, fixed dates, or indefinite.
  • A daily cap on how many of this meeting can be booked in a day.

Intake questions#

Add custom questions invitees answer when booking — short text, long text, a pick from a list (you type the choices, one per line — a list question needs at least one), or a phone number, each optionally required. Use them to gather what you need before the meeting (what they want to discuss, their company, a phone number).

Each question can also save its answer to the invitee's record: mobile phone, work phone, job title, LinkedIn, company name or company website. Answers only fill fields that are blank, so a booking never overwrites something your team already entered, and a phone number is added alongside any others rather than replacing them. Each field can be filled by one question per page.

Contacts and deals#

The Contacts and deals card decides what a booking adds to your records. Everything it adds is owned by you, the page's owner.

  • New invitees — Only link people who are already contacts (the default) or Add new people as contacts. A new contact gets the invitee's name and email, your mapped answers, and an optional lead status. An archived contact who books again is restored.
  • Company — Don't link a company, Link a company that already exists (the default), or Link the company, or create it. The company is found by the invitee's work email domain or by a company-name or website answer. Personal addresses such as Gmail never match or create a company. A contact who already belongs to a company keeps it.
  • Open a deal for each new booking — pick the pipeline, and optionally the stage and source. The deal is named after the company (or the invitee) and the page. If the invitee already has an open deal in that pipeline, the meeting is logged on that deal instead of opening a second one. Your pipeline's automations run for the new deal just as they do for one added by hand.

Every booking also puts the meeting on the timeline — on the deal when there is one, otherwise on the contact — and cancelling or rescheduling updates that entry. A rescheduled meeting keeps the original booking's contact and deal. Meetings booked from a ticket's scheduling link only link people who are already contacts; they never add anything.

You can only switch on what you could do by hand: adding contacts, adding companies and opening deals each need the matching permission, and you pick from the pipelines you have access to. If you later lose a permission or access, bookings stop adding those records and the Bookings list says why.

After booking#

Set a confirmation message or a redirect URL for where people land after they book, so the experience flows into your next step.

A well-configured booking page does your scheduling and your intake: the right length and buffers protect your calendar, and the questions mean you walk into every meeting already knowing what it's about.

Bring your whole services business together

Stop stitching together five tools. Run sales, delivery, support, and billing from one organization — with an AI assistant on every page.