> For the complete documentation index, see [llms.txt](https://calcom.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://calcom.gitbook.io/docs/core-features/event-types/requires-confirmation.md).

# Requires confirmation

Managing your meetings and calendar events can be quite stressful, especially if you don't know if the upcoming event is something that requires your attention at all. Luckily, if you set the event type to require your confirmation on each booking, you can reduce your workload by confirming or declining the booking in question. 

<figure><img src="/files/Qpn32Z0803qK1tPQwKYY" alt=""><figcaption></figcaption></figure>

You will still receive an email but it's in the form of booking request. The booking needs to be manually confirmed before it is pushed to the integrations and a confirmation mail is sent.

Cal.com also offers an **Requires Confirmation Threshold** where you have the capabilities to decide a time-frame where a booking requires confirmation only when it is made within that time-frame. You can learn more about [How to set up requires confirmation](/docs/how-to-guides/how-to-set-up-requires-confirmation.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://calcom.gitbook.io/docs/core-features/event-types/requires-confirmation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.