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

# Let your Dapta agent book

Let your Dapta Text Agents and Voice Agents offer your real open times and book on your dCal events during a chat or a call. See what the agent does, how to get your event ready, and what you see in d

Your Text Agents and Voice Agents in Dapta can book meetings straight into dCal. They read the same open times as your booking page, offer the ones that are free, and book the time the customer picks, without sending a link.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-304961966869155be5f25221589c8100c4950c05%2Fdcal-dapta-agents-01-agent-booking-in-list.png?alt=media" alt="The Bookings page with the Intro call booking of Thu, Oct 22 boxed under Upcoming, next to the Workshop and Demo bookings, with the same Cancel button and accepted label as any other booking"><figcaption><p>A booking made by an agent lands in <strong>Bookings</strong> like any other.</p></figcaption></figure>

***

## What the agent does

| The agent…              | What happens                                                                                                                                                                                          |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Checks availability** | Reads the open times of one of your dCal events: your working hours, minimum notice and buffers, minus the busy times on your connected calendars. These are the same times your booking page offers. |
| **Offers times**        | Names real free times in the chat or out loud on the call.                                                                                                                                            |
| **Books**               | Once the customer confirms a time, books exactly that slot with their full name and email. A phone number is optional.                                                                                |

In the Dapta app, the action calls your dCal events *meetings*: the **Meeting** you pick when you set it up is one of your dCal events.

***

## Set it up in your agent

You add one action to the agent in the Dapta app, and you need to be an admin or owner of your dCal workspace. The setup guides walk you through it:

| Agent       | Action in the Dapta app                     | Guide                                                                                                                                            |
| ----------- | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Text Agent  | **Schedule appointments (Dapta Calendars)** | [Schedule Appointments with dCal](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/schedule-appointments-with-dapta-calendars.md) |
| Voice Agent | **Dapta Calendars Scheduling**              | [Schedule Appointments with dCal](https://docs.dapta.ai/ai-voice-agents/agent-actions/schedule-appointments-with-dapta-calendars.md)             |

{% content-ref url="/pages/EGxycIJov1VqFsw4RUdY" %}
[Schedule Appointments with dCal](https://docs.dapta.ai/ai-text-agents/setting-up-your-text-agent/schedule-appointments-with-dapta-calendars.md)
{% endcontent-ref %}

{% content-ref url="/pages/YpahcN0m9n2lVoeGmx0T" %}
[Schedule Appointments with dCal](https://docs.dapta.ai/ai-voice-agents/agent-actions/schedule-appointments-with-dapta-calendars.md)
{% endcontent-ref %}

***

## Get your event ready in dCal

The agent books on one event. A few settings on that event decide how smoothly it goes:

1. **Set working hours** on the days you want the agent to book. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md).
2. **Connect your calendar**, so your busy times block agent bookings too. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).
3. **Leave Requires confirmation off.** With it on, every agent booking arrives as a request: the customer gets a request email, and the booking waits under **Pending confirmation** in **Bookings** until you confirm it. See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md).
4. **Keep the event visible on your booking page.** A hidden event cannot take bookings from an agent.
5. **Keep extra questions optional.** dCal refuses any booking that leaves a required question unanswered, agent bookings included. The agent collects the customer's name and email, so make any other question on that event optional. See [Booking questions](https://docs.dapta.ai/dcal/events/booking-questions.md).

***

## What you see when an agent books

| Where                | What happens                                                                                                                                            |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Bookings**         | The booking appears under **Upcoming**, like one made on your booking page.                                                                             |
| Your inbox           | You get the **New booking** email with the customer's details and answers, unless an admin switched that email off in **Settings** > **Notifications**. |
| The customer's inbox | The customer gets the confirmation with a calendar invite and the link to reschedule or cancel.                                                         |
| Your calendar        | The meeting is added to your connected calendar.                                                                                                        |
| HubSpot              | If your workspace connected HubSpot, the customer becomes a contact with a meeting. See [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md).  |
| Webhooks             | `booking.created` fires, as for any other booking. See [Webhooks](https://docs.dapta.ai/dcal/integrations/webhooks.md).                                 |

> **💡 Tip:** dCal does not mark which bookings an agent made: they look like any other booking. To tell them apart, give the agent an event of its own, such as "Intro call (phone)". The event name travels with every booking: in **Bookings**, in your emails, on the HubSpot meeting and in the `booking.created` webhook. That event also shows on your booking page.

***

## Rescheduling and cancelling

The agent books; it does not move or cancel bookings. The customer reschedules or cancels from the link in their confirmation email, and you can cancel from **Bookings**. See [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md).

***

## One dCal workspace for every agent

All the agents in your Dapta workspace book on the same dCal workspace, against the same open times. A time an agent books is no longer offered on your booking page, and a time someone books on your page is no longer offered by the agent.

For an external assistant connected over MCP, the event editor's **AI Agents** tab shows the event ID after saving, a sample request and the connection guide. The Dapta booking action described here books an event type; MCP [create\_event](https://docs.dapta.ai/dcal/developers/mcp-tools.md#create_event) puts an event directly on the host's calendar.

## Related

* [Start here](https://docs.dapta.ai/dcal/dcal.md): what dCal is and how to sign in.
* [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md): the event your agent will book.
* [Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md): if you keep **Requires confirmation** on.
* [Workspaces](https://docs.dapta.ai/dcal/account/workspaces.md): how dCal and the Dapta app share a workspace.


---

# 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/dapta-agents.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.
