> 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/booking-questions.md).

# Booking questions

Ask guests your own questions when they book a dCal event. See which fields every booking asks, how to add, order and require questions, which answer types to use, and where the answers reach you: ema

Every booking page asks for the guest's name and email. Booking questions let you ask more, such as their company, their phone number or what they want to talk about, so you arrive at the meeting prepared. Questions belong to one event, so each event can ask something different.

***

## What every booking asks

Three fields are built in. They appear on every booking page, cannot be removed, and show in the editor as locked rows tagged **built-in**.

| On the booking page  | Required | Limit                         |
| -------------------- | -------- | ----------------------------- |
| **Your name**        | Yes      | Up to 200 characters          |
| **Your email**       | Yes      | Must be a valid email address |
| **Notes (optional)** | No       | Up to 2,000 characters        |

Your own questions appear between **Your email** and **Notes (optional)**. Phone is not a built-in field: add a phone question if you need one.

***

**Step 1:** Open **Events**, click **Edit** on the event (or start a **New event**) and select **Booking form**. The three built-in fields are at the top, your questions follow, and **+ Add question** sits at the bottom.

***

**Step 2:** Click **+ Add question** and fill in the new row from left to right:

1. **name**: a short internal name for the answer, such as `company` or `phone`. Only letters, numbers and underscores are kept, up to 64 characters. Reminders use it to quote the answer, as `{{form.company}}`.
2. **Label**: the question your guest reads, such as `Company name`. Up to 200 characters.
3. The type: what kind of box the guest gets. See the table below.
4. For a `phone` question only, a country list: the country the guest's phone picker starts on.
5. **req**: tick it to make the question required.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-95a88ed59a598323f0b695854fe4623706b14d13%2Fdcal-booking-questions-02-question-rows.png?alt=media" alt="Two custom question rows: company with the label Company name, type text and req ticked, and phone with the label Phone number, type phone, country United States and req unticked"><figcaption><p>Each question has an internal name, the label guests read, a type and a required box.</p></figcaption></figure>

Use one of these types:

| Type       | What the guest gets                                                                                                  | What is checked                             |
| ---------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| `text`     | A one-line text box.                                                                                                 | Nothing.                                    |
| `textarea` | A text box three lines high, for longer answers.                                                                     | Nothing.                                    |
| `email`    | An email box.                                                                                                        | The answer must be a valid email address.   |
| `phone`    | A country code picker plus the number. The picker starts on the country you chose and guests can search for another. | The number must be long enough to be valid. |
| `number`   | A number box.                                                                                                        | Numbers only.                               |
| `guests`   | A text box for extra email addresses, separated by commas, semicolons or new lines.                                  | Each address must be valid.                 |

> **⚠️ Note:** A `guests` question collects addresses only. They reach you with the other answers, and dCal does not send those people an invitation. If they should attend, forward the calendar invite yourself.

> **⚠️ Note:** Fill in both the **name** and the **Label**. A question with either box empty is not saved. The names `name`, `email` and `notes` are taken by the built-in fields: the row shows a warning and the event will not save until you rename it.

***

**Step 3:** Put the questions in order with the up and down arrows (**Move up**, **Move down**). The booking page asks them in this order. The **×** at the end of a row removes the question; there is no confirmation, and the removal takes effect when you save.

Click **Create event** (new event) or **Save changes** (existing event).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-838b1404f123530c84254a943a14918b4ac0ef62%2Fdcal-booking-questions-03-reorder.png?alt=media" alt="The company and phone question rows with the Move up and Move down arrows and the remove button boxed on each"><figcaption><p>Reorder with the arrows. Changes apply when you save.</p></figcaption></figure>

There is no limit on the number of questions. Keep the list short: every extra question is one more reason to leave before booking.

***

## What guests see

After picking a time, the guest fills in **Your name**, **Your email**, your questions in your order, and **Notes (optional)**, then clicks **Confirm booking**. Required questions carry an asterisk, and leaving one empty shows **This field is required.**

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-e557f02550e850a45ce6c98ed57ef987b6725a17%2Fdcal-booking-questions-04-public-form.png?alt=media" alt="The booking page details form filled in for John Doe, with Your name, Your email, the boxed Company name (required) and Phone number questions, Notes (optional) and the Confirm booking button"><figcaption><p>The guest's view: built-in fields first, your questions, then notes.</p></figcaption></figure>

***

## Where the answers reach you

| Place                                                                    | Answers included?                                                                                                                                                                                                                                                                       |
| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Your **New booking** email, and your emails for requests and reschedules | Yes, in a **Their answers** section, labelled with your question labels. Empty answers are skipped. Up to 20 answers, each cut at 1,000 characters, 6,000 in all.                                                                                                                       |
| Reminder emails                                                          | Yes, wherever you add `{{form.<name>}}` to a reminder's subject or message. See [Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md).                                                                                                              |
| HubSpot                                                                  | Yes, once your workspace has connected HubSpot: each accepted booking's meeting in HubSpot lists your questions and answers, and **Send answers to your CRM** on the event can copy answers into contact properties. See [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md). |
| The guest's own emails                                                   | No.                                                                                                                                                                                                                                                                                     |
| Webhooks                                                                 | No. Webhook messages carry booking details such as its ID, status and times, never the answers. See [Webhooks](https://docs.dapta.ai/dcal/integrations/webhooks.md).                                                                                                                    |
| The **Bookings** page in dCal                                            | No. It shows the title, the time and the status.                                                                                                                                                                                                                                        |

> **💡 Tip:** Your email is where the answers land, so keep the host's **New booking** email switched on. Owners and admins manage it in **Settings** > **Notifications**. See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md).

***

## Changing questions later

* If a reminder quotes a question you removed or renamed, the **Reminders** tab warns that those variables will arrive empty and lists them. Update the reminder text to match.
* If the question was mapped under **Send answers to your CRM**, the mapping is dropped when you save. Map the new question again.

## Related

* [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md): the full event form.
* [Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md): quote answers in reminders.
* [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md): send answers to contact properties.
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md): the whole booking flow 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/booking-questions.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.
