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

# Bookings

Every dCal booking has a status: pending, accepted, cancelled or rejected. Learn where your bookings live, what each status means, and who can confirm, decline, reschedule or cancel a booking.

A booking is made each time someone picks a time on one of your booking links, and each time you book a time for someone yourself. This section shows where your bookings live in the dashboard, what each status means, and how you and your guests change a booking once it exists.

***

## Where your bookings live

Click **Bookings** in the left menu, or go to [app.dcal.ai/admin/bookings](https://app.dcal.ai/admin/bookings). The page lists the bookings you host in up to three parts: **Pending confirmation**, **Upcoming** and **Past & cancelled**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-4f935059f20a9a20e1f853743a6906488c49c778%2Fdcal-see-your-bookings-01-list.png?alt=media" alt="The Bookings page with the sections Pending confirmation (1), Upcoming (2) and Past &#x26; cancelled (2): a Consultation request, Demo and Intro call bookings, and one cancelled and one rejected booking"><figcaption><p>Your bookings, grouped by what needs your attention.</p></figcaption></figure>

***

## Booking statuses

Every booking shows its status as a small colored word at the end of its row.

| Status        | What it means                                                                                                                    | Where it appears                                        | What you can do                     |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ----------------------------------- |
| **pending**   | A request on an event that has **Requires confirmation** on. The time is already held: nobody else can book it while you decide. | **Pending confirmation**                                | **Confirm** or **Decline**          |
| **accepted**  | A confirmed booking.                                                                                                             | **Upcoming** until it starts, then **Past & cancelled** | **Cancel**, while it is still ahead |
| **cancelled** | You or your guest cancelled it.                                                                                                  | **Past & cancelled**                                    | Nothing                             |
| **rejected**  | You declined the request.                                                                                                        | **Past & cancelled**                                    | Nothing                             |

There is no "rescheduled" status. When a guest moves a booking, it stays **accepted** and takes the new time. Cancelling a booking or declining a request frees its time for other guests.

Events your AI assistant put on your calendar are listed here too, under their own title. A date of a repeating event, such as a weekly call, shows a **Repeats** mark, and its page says how it repeats. Its **Cancel** asks which dates: **Only this date**, **This and later dates** or **Every date not yet started**. Your calendar tells the people on it. See [MCP tools reference](https://docs.dapta.ai/dcal/developers/mcp-tools.md#repeating-events).

***

## Who can change a booking

You act from your dashboard. Your guest acts from the **Manage your booking** button in their emails, which is also on the confirmation screen they see right after booking.

| Action                       | You, from the dashboard                       | Your guest, from their link   |
| ---------------------------- | --------------------------------------------- | ----------------------------- |
| Confirm or decline a request | Yes                                           | No                            |
| Withdraw a request           | No: decline it instead                        | Yes, until the requested time |
| Reschedule a booking         | No                                            | Yes, until it starts          |
| Cancel a booking             | Yes, until it starts                          | Yes, until it starts          |
| Make a booking               | Yes, for someone else, with **+ New booking** | Yes, on your booking page     |

Every one of these changes emails both sides. See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md).

***

## In this section

{% content-ref url="/pages/j9nDbYDWgxP83FfkGE6P" %}
[See your bookings](https://docs.dapta.ai/dcal/bookings/see-your-bookings.md)
{% endcontent-ref %}

{% content-ref url="/pages/KkGdp6ZAWwlGVclKhM68" %}
[Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md)
{% endcontent-ref %}

{% content-ref url="/pages/cLcCuK6ezEtx6iqgZ5s0" %}
[Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md)
{% endcontent-ref %}

{% content-ref url="/pages/NdOsBkh38FORMyr6XCti" %}
[Book for someone](https://docs.dapta.ai/dcal/bookings/book-for-someone.md)
{% endcontent-ref %}

## Events created by your assistant

An assistant can also put an event directly on your calendar, with its own title and no event type or booking link. Your connected calendar sends the invitations to the attendees. See [create\_event](https://docs.dapta.ai/dcal/developers/mcp-tools.md#create_event) for how to create, read, move or cancel it.

## Related

* [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md): turn an event's bookings into requests you approve.
* [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md): the emails each change sends, to whom.
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md): the booking page and the confirmation screen.
* [Webhooks](https://docs.dapta.ai/dcal/integrations/webhooks.md): send new, cancelled and rescheduled bookings to your own systems.


---

# 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/bookings.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.
