> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/events/event-settings.md).

# Length, location and timing

Reference for the timing and location settings of a dCal event: length, location types and what guests see, the online meeting link, slot interval, minimum notice, buffers, availability schedule, cale

These settings decide what guests read about your meeting, which times your booking page offers, and what happens once someone books. They all live in the event form: open **Events**, then **New event** or **Edit** on an event. Use **General** for these settings. Buffers, seats, slot interval and booking window live in **Advanced settings**. **Reminders** and **CRM Connection** have their own tabs.

For the step-by-step creation flow, see [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md). This page explains each setting in depth and ends with a [reference table](#field-reference) of every field.

***

## Length

**Duration** is how long the meeting lasts. Choose **15 min**, **30 min**, **45 min**, **60 min**, or **Custom** for another whole number from 1 to 1,440 minutes. A new event starts at 30 minutes.

Each event has one length, and guests do not pick a duration. To offer the same meeting in two lengths, create two events, for example `consultation-30` and `consultation-60`.

Guests see the length on your profile page (for example **30 min** next to the title) and on the event's booking page.

***

## Location

**Location** tells guests where the meeting happens. Pick one option from the menu; three of them add a detail field.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-fa9fba3e309607f3dd6602c15f7b7be82779460c%2Fdcal-event-settings-01-location-menu.png?alt=media" alt="The Location menu open, showing Not specified (selected), Online meeting, In person, Phone call and Custom"><figcaption><p>Five options. In person, Phone call and Custom ask for a detail.</p></figcaption></figure>

| Option                      | Detail field              | What guests see                                                                                                                                                    |
| --------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Not specified** (default) | None                      | No location line. The meeting counts as online: it gets a meeting link when your calendar can create one. See [The online meeting link](#the-online-meeting-link). |
| Online meeting              | None                      | **Online meeting**, and a link to join once the booking is confirmed. See [The online meeting link](#the-online-meeting-link).                                     |
| **In person**               | **Address**               | **In person · {your address}**                                                                                                                                     |
| **Phone call**              | **Phone number**          | **Phone call · {your number}**                                                                                                                                     |
| **Custom**                  | **What to tell invitees** | Exactly your text, with no prefix.                                                                                                                                 |

For **In person**, **Phone call** and **Custom**, the editor requires a detail before you can save. It can have up to 500 characters. Switching to another option clears it.

Guests see the location on the booking page before they book, on the confirmation screen, on their manage page, in their emails and in the calendar invite.

> **💡 Tip:** Everything you type in the detail field is public on your booking page. Share a full street address or a direct phone number only if you are happy for anyone with the link to see it.

Each booking keeps the location it was made with. Changing the location later applies to new bookings only.

### The online meeting link

On your own events, the online meeting option in the menu can carry the name of the video tool your calendar uses. On a team event it always reads **Online meeting**. Guests always read **Online meeting** on your booking page.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-f3c366a5140cb03a9d4b33d77d7061a97f29ebb8%2Fdcal-event-settings-02-online-meeting-hint.png?alt=media" alt="The Location menu set to Online meeting with the hint A meeting link is created automatically when the booking is confirmed. boxed below it"><figcaption><p>No detail to fill in: the link is created for you.</p></figcaption></figure>

* On your own events, the form says **A meeting link is created automatically when the booking is confirmed.** dCal asks the connected calendar that receives your bookings (the one set to **Add events here**) to create one link per booking.
* An event left on **Not specified** gets a link the same way, with no hint in the form. **In person**, **Phone call** and **Custom** never get one, so choose one of them for a meeting that should have no link.
* If none of your connected calendars is set to receive events, the form warns: "No calendar is connected yet, so no meeting link can be created." and offers **Connect a calendar**. You can still save, and bookings still go through, but they have no meeting link. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).
* On a team event, one location serves every host. The hint starts with **This location applies to every host.** and says the link comes from the calendar where the assigned host receives new events (round-robin), or where one of the booking's hosts does (collective and fixed round-robin). Instead of the warning above, the editor warns when bookings would get no meeting link: it names the hosts who have no calendar set to receive new events, or says that no host has one, depending on the method. It has no button: each host turns on **Add new events here** on one of their own calendars, in **Calendars**. You can still save. See [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md).
* Guests find the link as **Join the meeting** in their confirmation email, in their reminders and on their manage page. The calendar invite in their emails carries it, and so does the **Add to calendar** file on the confirmation screen once it is ready.
* dCal holds the confirmation email for up to about half a minute so it can include the link. If the link is not ready in time, the email goes out without it, and the link still appears on the guest's manage page once it is created.
* On an event that uses [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md), the link is created when you confirm the request.

***

## Slot interval

**Slot interval (min)**, in **General** > **Advanced settings**, sets how far apart the start times on your booking page are. Start times are counted from the beginning of each block of hours, and a time is offered only if the whole meeting fits before the block ends.

With hours from 9:00 to 12:00:

| Length | Slot interval | Start times offered                                     |
| ------ | ------------- | ------------------------------------------------------- |
| 30     | 30            | 9:00, 9:30, 10:00, 10:30, 11:00, 11:30                  |
| 30     | 15            | 9:00, 9:15, 9:30 and every 15 minutes up to 11:30       |
| 60     | 60            | 9:00, 10:00, 11:00                                      |
| 60     | 30            | 9:00, 9:30, 10:00, 10:30, 11:00                         |
| 60     | empty         | 9:00, 10:00, 11:00 (an empty field steps by the length) |

> **Tip:** The slot interval starts at 30 minutes and follows the duration while they match. If you choose a different interval, changing the duration keeps that interval. An empty interval steps by the duration.

A booked time disappears for others, together with any start time that would overlap it. So with a 60-minute meeting every 30 minutes, booking 10:00 also removes 9:30 and 10:30.

***

## Minimum notice

**Minimum notice** is how soon from now a guest can book. Choose **1 hour**, **2 hours**, **6 hours**, **12 hours**, or **1 day** through **5 days**. A new event starts at **2 hours**. If an existing event has another saved value, including 0 or 30 minutes, the editor keeps it as an extra choice so saving does not change it.

The notice only removes times that are too soon. It does not shift the other start times.

***

## Buffers

**Buffer before (min)** and **Buffer after (min)** keep free time around a meeting. Both start at 0.

dCal offers a time only when the meeting, plus its buffer before and its buffer after, fits around everything that is already busy: your other bookings, times someone is holding while they fill in the form, and busy times on the calendars you check for conflicts.

Each new booking keeps its own buffers clear of what is already busy. So to keep a gap on both sides of every meeting, set both fields: **Buffer before (min)** protects the time after your previous commitment, and **Buffer after (min)** protects the time before your next one.

***

## Availability schedule

In **General** > **Bookable hours**, a personal event can use:

* **My working hours**: follows your default hours on **Availability**. Use **Edit working hours** to change them.
* **A saved schedule**: choose a reusable schedule from **Availability**, for example "Evenings". This choice is unavailable when you have no saved schedules.
* **Custom hours for this event**: set this event's own weekly ranges and time zone here. Choose a single day, **Weekdays**, **Weekends** or **Every day**, enter **from** and **to**, and use **Add hours** for another range. End must be after start, and ranges on the same day cannot overlap. Keep at least one range.

Custom hours start from your weekly working hours when you first choose them; date overrides do not carry over. They are private to this event and are not added to **Availability**. Editing them does not change another event's hours. To reuse a schedule or apply date overrides, choose **A saved schedule** instead.

The hours source's time zone decides when you are open. Guests see those times in their own time zone. On a team event, each host's own working hours apply; custom event hours are not offered. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md) and [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md).

***

## Calendar event text

In **General** > **In the calendar**, set **Calendar event title** and **Calendar event description**. The title is used in your calendar, the guest's calendar and booking emails. It does not rename the title on your public booking page. The description is written into the calendar event.

Leave the title empty to use the event's title. Leave the description empty for no description. Click a variable to insert it where your cursor was, drag it into either field, or type it as `{{event_title}}`. The palette follows the field you last selected, and the **Example** below the field uses sample values.

| Use                                  | Example                                        |
| ------------------------------------ | ---------------------------------------------- |
| Recognize the guest in your calendar | `{{event_title}} with {{attendee_name}}`       |
| Include an answer from Booking form  | `Company: {{form.company}}`                    |
| Include the host and meeting facts   | `{{host_name}}: {{event_name}} ({{duration}})` |

The palette groups guest, host, event and time variables, plus your booking-form answers. The description also accepts details such as the host's email, time zones and booking reference. Use the variables offered for the selected field: a meeting URL, manage link or other email-only variable cannot be saved in calendar text.

A group event with seats shares one calendar event, so its title and description cannot contain one guest's name, contact details or booking answers. The palette hides those variables, and the editor refuses a template that uses them. Use the event, host and time variables instead.

Unknown variables, unavailable variables or answers to a question that no longer exists need correction before saving. The error summary points to the field. Templates apply to new bookings; editing them does not rewrite past calendar invitations.

***

## Calendars for this event

On your own events, **Calendars for this event** lists your connected calendars with two choices each:

* **Check for conflicts**: tick every calendar whose busy times should block this event.
* **Add events here**: pick the one calendar that receives this event's bookings and creates the online meeting link.

The section starts with the choices from your **Calendars** page; **Manage calendars** takes you there. With no calendar connected, the section says bookings will not check your real availability and offers **Connect a calendar**. Team events do not have this section: each host's own calendars apply. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md) and [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md).

***

## Reminders

The **Reminders** tab of the event editor holds this event's reminder emails and its follow-up.

* A new event starts with two reminders switched on, 1 day and 1 hour before it starts, and a follow-up 1 hour after it ends, switched off.
* You can have up to 10 reminders plus the follow-up. Each one is sent between 5 minutes and 28 days from the meeting.
* Leave **Subject** and **Message** empty to use the standard wording, or write your own.

Who receives them, the variables you can use and the timing rules are in [Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md).

***

## How far ahead guests can book

**Booking window (days)**, in **General** > **Advanced settings**, sets how many days ahead guests can book this event. Leave it empty (it reads **No limit**), or type a whole number from 1 to 730. Events start with no limit.

* **How the days count.** Today is day 0, in the time zone of the event's schedule (on a team event, in each host's own). With 14, the last day a guest can pick is 14 days from today, at any hour of that day.
* **Where it applies.** Your booking page, team pages, one-off invite links, the page where your guests reschedule, and AI agents and integrations that look for times or book through dCal. A time past the window is treated like a time you do not offer.
* **What it does not limit.** A booking you make yourself with **Any time (outside availability)** in **Bookings**, and a booking an integration creates with an API key through `POST /v1/machine/bookings`.
* A number outside 1 to 730 shows "Use a whole number from 1 to 730, or leave it empty." and the event is not saved until you fix it.

Your booking page itself shows times up to 60 days ahead at most, whatever the window:

| **Booking window (days)** | On your booking page      | For AI agents and integrations                           |
| ------------------------- | ------------------------- | -------------------------------------------------------- |
| Empty (**No limit**)      | Times up to 60 days ahead | No limit. Each search covers up to 60 days               |
| 1 to 60                   | Times up to the window    | Times up to the window                                   |
| 61 to 730                 | Times up to 60 days ahead | Times up to the window. Each search covers up to 60 days |

On the booking page, days past the window show no times, like days you are not available.

There is no daily or weekly limit on the number of bookings. To take fewer meetings on a given date, give that date shorter hours with a date override in **Availability**. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md).

***

## Redirect after booking

**Redirect after booking** sends your guests to a page of yours once they book, for example a thank-you page on your website, instead of leaving them on dCal's confirmation screen. Leave it empty to keep the confirmation screen.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-1b8c17eac9cee4b212f813fb5c49c20fd228db39%2Fdcal-event-settings-07-redirect-after-booking.png?alt=media" alt="The Redirect after booking field set to https://example.com/thanks and the Booking details on that page list set to The event, its time and the campaign (UTMs), both boxed, each with its hint"><figcaption><p>The address of your thank-you page, and the booking details dCal adds to it.</p></figcaption></figure>

* Type a full address that starts with `https://`, up to 2,048 characters. An address that starts with `http://` or contains spaces shows "Use a full address that starts with https\://" and the event is not saved until you fix it.
* Every booking redirects, requests you still have to confirm included.
* Rescheduling or cancelling never redirects: your guests' manage page always stays on dCal.
* Only someone who books receives the address. It is never shown on the booking page before that.
* Your [tracking tags](#tracking-and-pixels) and the [embed messages](https://docs.dapta.ai/dcal/share/embed.md#messages-your-page-receives) go out before the page leaves, so the booking still counts.
* On a booking page embedded in your website, your whole website page goes to the address, not just the frame. If the browser blocks that, the confirmation stays in place with the line **Taking you to** and your site, and a **Continue** link.

### Booking details on that page

Once you type an address, **Booking details on that page** appears. It chooses what dCal adds to the address as parameters, so your thank-you page and the analytics on it can count the booking:

| Option                                                                  | Parameters added                                                                                                                                                                                                                                                                              |
| ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **None: the address as you typed it** (the default)                     | None.                                                                                                                                                                                                                                                                                         |
| **The event, its time and the campaign (UTMs)**                         | `event_type` (the event's slug), `event_type_name`, `event_start_time` and `event_end_time` (in UTC), `booking_status` (`accepted`, or `pending` for a request), `assigned_to` (the host's name), and the booking's `utm_source`, `utm_medium`, `utm_campaign`, `utm_term` and `utm_content`. |
| **The event, its time, the campaign, and the invitee’s name and email** | All of the above, plus `invitee_full_name` and `invitee_email`.                                                                                                                                                                                                                               |

* The answers to your questions, the booking's reference and its title are never added.
* A parameter that your address already has keeps your value. If your address already has any `utm_` parameter, none of the booking's UTMs are added.
* If the details would make the address longer than 2,048 characters, the guest goes to the address exactly as you typed it.
* Clearing the address also clears this choice.
* The booking's UTMs come from the link the guest booked from, or from the website page that embeds it. See [Track where bookings come from](https://docs.dapta.ai/dcal/share/your-booking-page.md#track-where-bookings-come-from).

> **⚠️ Note:** With the last option, your guest's name and email end up in your page's address and in whatever analytics runs on that page. Choose it only if that page needs them.

***

## Tracking and pixels

Owners and admins can connect their own analytics and ad tools to an event's booking page in **CRM Connection** > **Tracking and pixels**. Members do not see this section. Each tool hears the page view, the day and time the guest picks, and the booking, with the event's details and nothing about the guest.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-ef4b92bcfbf0d6dceb7a09fbfe2dc9c9e51d0a02%2Fdcal-event-settings-08-tracking-and-pixels.png?alt=media" alt="The Tracking and pixels section with its subtitle and six fields, each with its help line: Meta Pixel ID 123456789012345, PostHog project key empty, PostHog cloud set to US cloud, Google Tag Manager ID GTM-ABC1234, Google Analytics 4 measurement ID G-ABC123XYZ9 and HubSpot tracking ID 12345678"><figcaption><p>Fill in only the tools you use. A tool with no ID never loads.</p></figcaption></figure>

| Field                                 | What to paste                                                  | Format                               |
| ------------------------------------- | -------------------------------------------------------------- | ------------------------------------ |
| **Meta Pixel ID**                     | Your Meta pixel's ID                                           | Numbers only                         |
| **PostHog project key**               | Your PostHog project's API key                                 | Starts with `phc_`                   |
| **PostHog cloud**                     | Where your PostHog project lives: **US cloud** or **EU cloud** | Self-hosted PostHog is not supported |
| **Google Tag Manager ID**             | Your container ID                                              | For example `GTM-ABC1234`            |
| **Google Analytics 4 measurement ID** | Your measurement ID                                            | For example `G-ABC123XYZ9`           |
| **HubSpot tracking ID**               | Your HubSpot portal ID                                         | Numbers only                         |

Click **Save changes** and the tags start on the booking page right away. To stop a tool, empty its field and save. An ID in the wrong format shows a message under its field, for example "A Meta Pixel ID is numbers only.", and the event is not saved until you fix it.

### What each tool receives

| What the guest does    | Meta Pixel                           | Google Analytics 4      | Google Tag Manager      | PostHog                 |
| ---------------------- | ------------------------------------ | ----------------------- | ----------------------- | ----------------------- |
| Opens the booking page | `PageView`                           | Page view               | Your container loads    | `$pageview`             |
| Picks a day            | `BookingDateSelected` (custom event) | `booking_date_selected` | `booking_date_selected` | `booking_date_selected` |
| Picks a time           | `BookingTimeSelected` (custom event) | `booking_time_selected` | `booking_time_selected` | `booking_time_selected` |
| Books                  | `Schedule` (standard event)          | `booking_scheduled`     | `booking_scheduled`     | `booking_scheduled`     |

* **HubSpot** loads the HubSpot tracking code for your portal, so visits to the booking page count in HubSpot. Bookings themselves reach HubSpot through the HubSpot integration. See [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md).
* **Google Analytics 4:** mark `booking_scheduled` as a key event to count bookings as conversions. Its cookies stay on `book.dcal.ai` itself, and a booking page embedded on your website is counted too, in browsers that accept partitioned cookies, such as Chrome. A Google Analytics tag you add inside your own Tag Manager container follows that container's settings instead.
* **Google Tag Manager:** the events reach your data layer with the event's details under `dcal`, ready to use as triggers.
* **PostHog** receives the page view and these steps only: no autocapture, session recording or surveys.
* **Meta Pixel:** Meta's automatic events are off. dCal sends the steps above itself.
* Every pick counts: a guest who looks at three days sends three day events. The booking is sent once per booking, requests you still have to confirm included, and before any [redirect after booking](#redirect-after-booking).

**What the events carry.** The event's slug (`event_type`), its length (`duration_minutes`), whether it is a team event (`is_team`), the day or start time picked (`date`, `start_time`) and, on the booking, `booking_status` (`accepted`, or `pending` for a request). Never the guest's name, email or answers, and never the booking's reference.

**Where the tags load.** Only on this event's booking page: the event's own page and its one-off invite links, opened directly or embedded on a website. Never in your dashboard, the booking page studio preview, your guests' manage page, or the profile and team pages that list your events. Booking pages live on their own address, `book.dcal.ai`, apart from your dashboard on `app.dcal.ai`, where tags never load.

* On a website that still uses an older embed snippet, with `app.dcal.ai` in its address, Google Tag Manager, Google Analytics 4 and HubSpot do not load; Meta Pixel and PostHog do. Copy the snippet again from **Embed on your site** to fix it. See [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md).

> **⚠️ Note:** dCal never sends your guest's details to these tools, but some features you can turn on in the tools themselves can read the booking form: automatic advanced matching in Meta, collected forms in HubSpot, and any tag you add to your Google Tag Manager container, which runs on your booking page. Whether to turn those on is your choice and your responsibility.

***

## Field reference

The event editor fields, grouped by their purpose. The Spanish column shows the label when the dashboard is in Spanish.

| Field                            | Spanish label                           | Default                                    | Limits                                                                                                          |
| -------------------------------- | --------------------------------------- | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
| **Title**                        | Título                                  | Empty (required)                           | 1 to 200 characters                                                                                             |
| **Event link**                   | Enlace del evento                       | Filled in from the title                   | 1 to 80 characters; unique among your events                                                                    |
| **Description**                  | Descripción                             | Empty                                      | Up to 2,000 characters                                                                                          |
| **Location**                     | Ubicación                               | **Not specified**                          | Required detail for In person, Phone call and Custom, up to 500 characters                                      |
| **Calendar event title**         | Título del evento en el calendario      | Event title                                | Supported title variables or plain text                                                                         |
| **Calendar event description**   | Descripción del evento en el calendario | Empty                                      | Supported description variables or plain text                                                                   |
| **Duration**                     | Duración                                | 30                                         | 1 to 1,440                                                                                                      |
| **Slot interval (min)**          | Intervalo entre horarios (min)          | 30                                         | Whole minutes above 0; empty steps by the length                                                                |
| **Minimum notice**               | Antelación mínima                       | 2 hours                                    | 1, 2, 6 or 12 hours; 1 to 5 days; existing values preserved                                                     |
| **Buffer before (min)**          | Margen antes (min)                      | 0                                          | 0 or more                                                                                                       |
| **Buffer after (min)**           | Margen después (min)                    | 0                                          | 0 or more                                                                                                       |
| **Seats / slot (group)**         | Cupos / horario (grupo)                 | Empty (one person per time)                | 1 or more. See [Group events](https://docs.dapta.ai/dcal/events/group-events.md)                                |
| **Booking window (days)**        | Antelación máxima (días)                | Empty (**No limit**)                       | 1 to 730 days. See [How far ahead guests can book](#how-far-ahead-guests-can-book)                              |
| **Bookable hours**               | Horario para reservar                   | **My working hours**                       | Working hours, a saved schedule or custom personal-event hours                                                  |
| **Calendars for this event**     | Calendarios para este evento            | Your Calendars page choices                | Your own events only                                                                                            |
| **Scheduling method**            | Método de programación                  | **Round-robin**                            | Team events only                                                                                                |
| **Hosts**                        | Anfitriones                             | Every team member, when you save the event | Team events only                                                                                                |
| **Priority**                     | Prioridad                               | **Medium**                                 | Five levels, **Lowest** to **Highest**. Round-robin and fixed round-robin only                                  |
| **Weight**                       | Peso                                    | 100                                        | 1 or more. Round-robin and fixed round-robin only                                                               |
| **Fixed**                        | Fijo                                    | Off                                        | Fixed round-robin only                                                                                          |
| **Requires confirmation**        | Requiere confirmación                   | Off                                        | Your own events only. See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md)     |
| **Hidden**                       | Oculto                                  | Off                                        |                                                                                                                 |
| **One booking per person**       | Una reserva por persona                 | Off                                        | Counts upcoming bookings only                                                                                   |
| **One-off invite links**         | Enlaces de invitación de un solo uso    | None                                       | No limit. See [One-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md)                        |
| **Redirect after booking**       | Redirigir después de reservar           | Empty (guests see the confirmation screen) | An `https://` address, up to 2,048 characters. See [Redirect after booking](#redirect-after-booking)            |
| **Booking details on that page** | Datos de la reserva en esa página       | **None: the address as you typed it**      | Shown once a redirect address is set                                                                            |
| **Tracking and pixels**          | Seguimiento y píxeles                   | No tool connected                          | Owners and admins only. Six optional fields. See [Tracking and pixels](#tracking-and-pixels)                    |
| **Booking form**                 | Formulario de reserva                   | Name, email and notes, always asked        | No limit on your own questions. See [Booking questions](https://docs.dapta.ai/dcal/events/booking-questions.md) |
| **Reminders**                    | Recordatorios                           | 24 h and 1 h before, on; follow-up off     | Up to 10 reminders and 1 follow-up; 5 minutes to 28 days                                                        |
| **Send answers to your CRM**     | Enviar respuestas a tu CRM              | Nothing mapped                             | Up to 50 answers mapped. See [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md)                      |

## Related

* [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md): the event form step by step.
* [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md): how hours, bookings and calendars combine.
* [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md): schedules and date overrides.
* [Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md): reminder emails in detail.
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md): the booking page from the guest's side.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/events/event-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
