> 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/require-confirmation.md).

# Require confirmation

Turn bookings on a dCal event into requests you confirm or decline. Learn how to switch Requires confirmation on, what guests see and receive, how the request holds the time, and what happens when you

With **Requires confirmation** on, a booking on the event is not final straight away. It arrives as a request, the time is held for the guest, and nothing goes to your calendar until you confirm it. Use it for meetings you want to screen first: a new client consultation, an interview, a demo for a large account.

***

**Step 1:** Open **Events** and click **Edit** on the event. In **General** > **After booking**, tick **Requires confirmation** and click **Save changes**.

On the Events list, the event's second line now ends in **needs confirmation**, so you can tell these events apart at a glance.

> **💡 Tip:** Guests are not told in advance that you confirm each booking. Say so in the event's **Description**, for example "I confirm every request within one working day."

***

**Step 2:** Here is what the guest experiences. The booking page works as usual: they pick a time, fill in their details and click **Confirm booking**. Instead of **Booking confirmed**, they see **Booking requested** with a clock icon and the line "Awaiting the host’s confirmation. We’ll email {their address} once it’s confirmed."

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-80ab8c7b2a754da21020174ea92628f7d8eb625a%2Fdcal-require-confirmation-02-booking-requested.png?alt=media" alt="The Booking requested screen for a Consultation, with a clock icon, the boxed title, the line Awaiting the host&#x27;s confirmation and the Add to calendar and Manage your booking buttons"><figcaption><p>The guest sees the request was received, not a confirmed meeting.</p></figcaption></figure>

If the event has a [Redirect after booking](https://docs.dapta.ai/dcal/events/event-settings.md#redirect-after-booking), requests redirect too: the guest goes to your page instead of this screen.

The guest then gets a **Request received** email, with no calendar invite, and a **Manage your request** button that lets them cancel the request. Their emails are in the language of the booking page they used.

> **⚠️ Note:** The link to manage the booking arrives in the **Request received** email. Ask guests to keep that email: it is the one they use to cancel or reschedule, also after you confirm. A guest who wants a different time for a pending request cancels it and books again.

***

**Step 3:** You get a **New booking** email marked **Needs your OK**, with the guest's details, their answers to your questions, and a **Confirm or decline** button. The button opens the request in dCal (sign in if asked).

In dCal, requests wait at the top of **Bookings**, under **Pending confirmation**, each with **Confirm** and **Decline** buttons.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-8d4c492954c1fb73ae63aaeedf240d2dc4a1d38b%2Fdcal-require-confirmation-03-pending-section.png?alt=media" alt="The Bookings page with the Pending confirmation (1) section boxed, showing one Consultation request with Confirm and Decline buttons and a pending label"><figcaption><p>Requests stay here until you answer them.</p></figcaption></figure>

How to answer, step by step: [Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md).

***

## The request holds the time

From the moment the guest sends the request, the time is blocked: nobody else can book it, on this event or on your other events.

A request waits until you confirm or decline it. It does not expire on its own, so answer requests promptly, or the time stays held.

***

## What happens next

| You         | The guest gets                                                                         | On your side                                                                                                                                                                                                             |
| ----------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Confirm** | The confirmation email with the calendar invite. Reminders are scheduled from then on. | The meeting is added to your calendar, with an online meeting link if the event uses one. You get a **New booking** email for the confirmed booking. If your workspace connected HubSpot, the booking is sent to it now. |
| **Decline** | A **Not accepted** email.                                                              | The time is free again for others.                                                                                                                                                                                       |
| Nothing     | Nothing more: the request stays pending.                                               | The time stays held.                                                                                                                                                                                                     |

While a request is pending, nothing is written to your calendar, no reminders are scheduled and nothing is sent to HubSpot.

***

## Team events

**Requires confirmation** applies to your own events. Bookings on team events are confirmed right away, even if the box is ticked, so leave it off on team events.

## Related

* [Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md): answer requests from Bookings or from the email.
* [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md): every email in a request's life.
* [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md): what guests can change, and how.
* [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md): the other options on the event form.


---

# 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/require-confirmation.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.
