> ## Documentation Index > Fetch the complete documentation index at: /help/llms.txt > Use this file to discover all available pages before exploring further. # Your booking page > A Kerux page where people pick a free time on your calendar. The meeting lands on your calendar with a video link and their campaigns stop. > [!NOTE] > > **Pro plan.** Booking pages and connected calendars are part of Pro and Agency, and of the free trial. A booking page needs a connected calendar: connecting Google Calendar is free (no email inbox needed), and the calendar of a Gmail or Outlook inbox you already connected is free too. Pages that are already live keep taking bookings on every plan. See [Plans and billing](/help/account/billing.md). A booking page is a public link, like `usekerux.com/b/intro-call`, where people pick a free time on your calendar. Kerux reads your calendar for busy times, writes the meeting on it with a video link, makes the person a contact (or finds the contact they already are), and stops their campaigns, exactly like a meeting booked any other way. ## Before you start Your calendar must be connected: in **Meetings** > **Connected calendars**, click **Connect Google Calendar** (free, see [Google Calendar](/help/integration-guides/google-calendar.md)), or **Turn on calendar** on an inbox you already connected. Outlook shows **Coming soon**: for now, connect your Outlook inbox and turn its calendar on. Then set your hours in **Meetings** > **Availability**. The first time you open **Meetings**, three steps walk you through it: connect your calendar, set your hours, share your link. See [Meetings](/help/campaigns/meetings-overview.md). ## 1. Create a booking link **1. Open Booking pages** Click **Meetings** in the menu, then **Booking pages**, then **New booking page**. **2. Say what it is** A title (for example "Intro call"), the length (15, 30, 45 or 60 minutes) and, if you like, the page address and a short description. **3. Choose who takes the meetings** **One person**: you (or a teammate) and the calendar to use. **Round robin across teammates**: each booking goes to the next teammate who is free at that time, in turn. **4. Choose when people can book** **Use the hosts' availability** (the default for a new page): each host's hours, timezone and days off from **Meetings** > **Availability**; change them there once and every page that uses them follows. Or **Hours just for this page**: its own timezone and hours per weekday, with several intervals a day (for example 9:00-12:00 and 14:00-17:00; **Add hours**). Then the rules: free minutes before and after each meeting, the minimum notice (for example 4 hours), how far ahead people can book and, if you want, the most bookings a day. A new page starts with the buffers and notice from your availability. **5. Choose the questions** Name and email are always asked. Company can be off, optional or required. Add up to 5 more questions: each answer is saved on the contact as a custom field. **6. Save and share** Copy the link from its card (**Copy link**), open it with **View page**, or put `{{links.booking}}` in a message (see below). Your first page is the **default** one. To make another one the default, click **Make default** on its card. **Taking bookings** turns a page on or off. ## 2. What the visitor sees The page looks like the booking pages people already know: who they meet, the title, the length and your description on the left; a calendar of the month in the middle, with the days that have free times highlighted; and the free times of the chosen day on the right, in **their own timezone** (found from their browser; they can change it under the calendar). It's in English unless they pick another language in the top corner. They pick a day, a time, click **Next**, fill in their name and email, and click **Confirm booking**. **Change time** takes them back. On a phone it works the same, one part under the other. Free times are your hours (your availability or the page's own, with days off) minus everything that shows you as busy on your calendar, minus the free minutes around each meeting and what is already booked. Kerux checks the calendar again right before booking, so two people can never get the same time. ## 3. What happens when someone books * The meeting is written on your calendar **once**, with them invited and a Google Meet link (Google calendars) or Teams link (Outlook). If the calendar can't add a video link, the confirmation and the email say so. * They become a contact with source **Booking page**, or are matched to the contact they already are. If the same email is on several contacts, Kerux asks you who it is in **Home > Tasks**, like any other meeting. * The meeting counts like any meeting: campaigns with **When a meeting is booked** stop for them, **Meeting booked** campaigns start, **Meeting starts soon** reminders are sent, and the contact moves on your [pipeline](/help/leads/pipeline.md). * They get a confirmation email in the language they booked in, with the time in their timezone, an `.ics` file for their calendar and a link to **reschedule or cancel**. To keep booking pages from being used to send unwanted email, a workspace sends up to 300 booking emails a day (30 during the free trial) and up to 6 a day to the same address; past that the booking still stands and the page shows it with its calendar file. * Their contact's timeline shows **Booked on a booking page**, and the webhooks `booking.created`, `booking.rescheduled` and `booking.cancelled` fire. See [Webhooks](/help/developers/webhooks.md). ## 4. Reschedule and cancel The visitor uses the link in their email to pick another free time or cancel. The calendar event moves or is cancelled once, and they get a new email with an updated `.ics`. A cancelled meeting never restarts a campaign by itself. You can cancel a booking from **Meetings** > **Calendar** (the **Cancel** button on it). ## 5. `{{links.booking}}` in your messages Write `{{links.booking}}` in any message (it is in the variable menu as **Booking link (theirs)**). Each contact gets the default booking link with their own key, so when they book, Kerux knows it is them for sure, even if they type another email. Their name and email are filled in on the page. If the workspace has no default booking link that is taking bookings (none yet, or the default one is off), the message waits instead of going out with an empty link (safe sending). If you already have a [trigger link](/help/campaigns/kerux-triggers.md#trigger-links) named `booking`, `{{links.booking}}` stays that trigger link. ## Calendar **Meetings** > **Calendar** shows the week: meetings with contacts from your connected calendars and booking tools, and bookings from your booking pages, each with its contacts. Kerux keeps only meetings with contacts: your other events stay private and only count as busy time. ### "Needs a check" If your calendar didn't answer while Kerux was writing a booking, Kerux never writes it a second time. It reads the calendar to see whether the meeting is there; when it can't tell, the booking shows **Needs a check** and you get a notification. Look at your calendar, then click **Check again** (it's there: the booking is confirmed and the person gets their email) or **It's not on the calendar** (the time is free again). ## Good to know * Busy times are read again at most every couple of minutes and within an hourly limit per calendar, so the page stays fast and your calendar isn't read too often. * Only start and end times of your other events are used, never their titles or guests. * Through the API: `GET` / `POST /v1/booking-links` (`use_schedule: true` follows the hosts' availability), `GET` / `PATCH` / `DELETE /v1/booking-links/{id}`, `GET /v1/booking-links/{id}/availability`, `GET /v1/bookings`, `POST /v1/bookings/{id}/cancel` and `POST /v1/bookings/{id}/review`. See [API](/help/developers/api.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.