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

# FAQ

Short answers to what hosts ask most about dCal: price and premium extras, Google and Outlook, how far ahead guests can book, time zones, confirmation, rescheduling, reminders, languages, teams, embed

Quick answers, each with a link to the page that covers the topic in full.

***

## Plans and account

### Is dCal free?

Yes. Events, calendar connections, bookings, emails and reminders, teams with every scheduling method, the design studio and brand kit, members, HubSpot, webhooks and the API are all free. Only two extras come with a paid plan; see the next answer.

### What comes with a Dapta AI subscription?

Two extras, both switched on by a workspace owner or admin:

* **Hiding the Dapta branding**: the "Made with dCal.ai by Dapta" badge and the free calendar invitation on your public pages and in your guests' emails. See [The Dapta badge](https://docs.dapta.ai/dcal/design/dapta-branding.md).
* **A custom link**: a name of your choice in place of the 6-character code in all your workspace's links. See [Custom link](https://docs.dapta.ai/dcal/share/custom-link.md).

### Do I need a Dapta account?

You do, to host: you sign in at [app.dcal.ai](https://app.dcal.ai) with your Dapta account. Your guests need nothing at all: they open your link and book. See [Sign in and set up](https://docs.dapta.ai/dcal/getting-started/sign-in.md).

### Is dCal the same as Dapta Calendars?

Yes. dCal is the new name of Dapta Calendars, and the dashboard, booking pages and emails now say dCal. A few technical names keep the old one, such as `data-dapta-calendars` in the embed code; they keep working as they are.

### Can I use dCal in Spanish?

Yes, in English or Spanish. The dashboard starts in your browser's language; to change it, pick **English** or **Español** under **Language** at the bottom of **Settings** > **General**, and the choice is saved in that browser. Your booking pages follow each guest's browser language, or the `?lang=es` or `?lang=en` you add to a link, and a guest's emails are written in the language of the page they booked on. See [Language and appearance](https://docs.dapta.ai/dcal/account/language-and-appearance.md).

***

## Calendars and availability

### Which calendars can I connect?

Google Calendar and Outlook / Microsoft 365. You can connect several accounts, mixing both. Each one can be checked for conflicts, and one of them receives your new bookings. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).

### Do I have to connect a calendar?

No, bookings work without one. But then dCal only knows your dCal bookings: it cannot see your other meetings, cannot add bookings to your calendar and cannot create online meeting links. Connect one before you share your links.

### How far ahead can people book?

Up to 60 days from today on your booking pages, or fewer when you set **Booking window (days)** on the event: with 14, the last day a guest can pick is 14 days from today. The earliest time offered is now plus the event's **Minimum notice**, which starts at 120 minutes (2 hours) on a new event. See [How far ahead guests can book](https://docs.dapta.ai/dcal/events/event-settings.md#how-far-ahead-guests-can-book) and [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md).

### Can I limit how many bookings I get per day?

Not today: there is no daily or weekly cap. To control your load, narrow your hours, add buffers before or after meetings, or raise the minimum notice. See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).

### How do I take a day off?

A date override replaces your hours on one date, but it always needs at least one time range, so it cannot clear a whole day. Instead, add a timed event that covers your hours that day, shown as busy, to a calendar dCal checks for conflicts. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md#take-a-day-off).

### Which time zone do my guests see?

Their own. Your booking page opens in the time zone the guest's browser reports, and the event panel names your time zone as **the host's time**. If the browser reports UTC or a zone the page cannot use, the page opens in your time zone instead. Guests can pick any other zone in the time zone picker next to the times, and the zone they book in is saved for their emails. See [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md).

***

## Events and bookings

### Can one event offer several meeting lengths?

No, each event has one length. To offer 15, 30 and 60 minutes, create three events; your profile page lists them all. See [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md).

### Can I approve each booking before it is confirmed?

Yes, on your own events. Turn on **Requires confirmation** on the event. Guests then see **Booking requested**, the time is held for them, and you confirm or decline from **Bookings**. A request does not expire, so review them regularly. See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md).

### Can several people book the same time?

Yes. Set **Seats / slot (group)** on the event to the number of people per time. Guests see how many seats are left on each time, and **Full** when none are. See [Group events](https://docs.dapta.ai/dcal/events/group-events.md).

### Can I send a link that works only once?

Yes. In the event, click **Create invite link** under **One-off invite links**. Each link books the event once and then stops working. Mark the event **Hidden** to make those links the only way to book it. See [One-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md).

### What happens if two people pick the same time?

Only one gets it. On your personal one-to-one events, picking a time holds it for 10 minutes while the guest fills in the form, and other visitors stop seeing it. dCal also checks the time again when a guest confirms, so if two people still confirm the same time, the second sees **That time was just taken.** and picks another one.

### Where do I see who booked and what they answered?

In the email dCal sends you for each new booking: it carries the guest's name, email, phone and answers. The **Bookings** page lists each booking's event, time and status. See [See your bookings](https://docs.dapta.ai/dcal/bookings/see-your-bookings.md).

### Can I book a meeting for someone else?

Yes. In **Bookings**, click **+ New booking**, pick the event and a time, and enter the guest's name and email. The guest gets the usual confirmation. You can also pick any time outside your hours. See [Book for someone](https://docs.dapta.ai/dcal/bookings/book-for-someone.md).

***

## Your guests

### Can guests reschedule or cancel?

Yes, with the **Manage your booking** link in their emails and on their confirmation screen, at any time before the meeting starts. Each reschedule sends a new link and the old one stops working. When you confirm a request, the guest keeps managing it from the link in their **Request received** email, so ask them to keep that email. See [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md).

### Do guests get reminders?

Yes. A new event sends a reminder 24 hours and another 1 hour before the meeting, to the guest and to you. Each event can have up to 10 reminders with your own wording, plus a thank-you email after the meeting, which is off until you turn it on. See [Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md).

### Do guests get a calendar invitation?

Yes, one. The confirmation email carries a calendar invitation, a reschedule sends an updated one and a cancellation removes it. Your connected calendar does not send its own as well, so your guest is not invited twice. If dCal's email can't reach your guest, your calendar sends its invitation instead. The confirmation screen also has an **Add to calendar** button. A request that still needs your confirmation gets its invitation once you confirm it. See the exceptions in [The calendar invite](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md#the-calendar-invite).

### Who sends the booking emails?

**dCal**, from `calendars@notifications-dapta.ai`. Ask guests to allow that address if your emails land in spam. A guest who replies to one reaches dCal support at <support@daptatech.com>, not you. See [Emails](https://docs.dapta.ai/dcal/emails.md).

***

## Teams and sharing

### Can my team share bookings?

Yes. A team event can rotate bookings among hosts (**Round-robin**), book everyone at once (**Collective**), or always include your fixed hosts plus one rotating host (**Fixed round-robin**). Workspace admins and owners create teams. See [Teams](https://docs.dapta.ai/dcal/teams.md).

In round-robin, each host has a **Priority** level, from **Lowest** to **Highest** (everyone starts at **Medium**): among the hosts free in their own working hours, the one with the highest priority gets the booking, and **Weight** shares bookings among hosts at the same level. To share a round-robin event's bookings evenly instead, set its **Distribution** to **Equal distribution**: priority and weight then do not apply. Teammates who have not joined yet, or who have no working hours, are never assigned a booking. One location applies to every host of a team event; for an online meeting, each booking's link comes from a host's own calendar. See [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md).

### Can I put my booking page on my website?

Yes. Click the **Embed on your site** icon on an event, copy the code and paste it into your page. It sizes itself as guests move through it. See [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md).

### Can I use my own domain, or change my link?

Your links live on `book.dcal.ai`. To show booking on your own domain, [embed it](https://docs.dapta.ai/dcal/share/embed.md) on your site. You can change your handle in **Settings** > **General** and an event's slug in the event, but links you already shared with the old handle or slug stop opening, so share the new ones. A [custom link](https://docs.dapta.ai/dcal/share/custom-link.md) replaces the code at the start of every link and keeps your old links working.

***

## Links, tracking and thank-you pages

### Why do my links say book.dcal.ai?

Booking pages have their own address, `book.dcal.ai`, apart from your dashboard at `app.dcal.ai`. That keeps any tracking tags you add to your booking pages away from your dashboard. Every link dCal gives you uses it: copy buttons, the embed code, emails and AI agents. Links you already shared that start with `app.dcal.ai` keep working and send guests to the same page on `book.dcal.ai`, with the same address and query, UTMs included.

### Can I send guests to my own thank-you page after they book?

Yes. Set **Redirect after booking** on the event to a full address that starts with `https://`. After they book, requests included, guests go to that page instead of the confirmation; rescheduling or cancelling never redirects. With **Booking details on that page**, the address can also carry the event, its time and the campaign (UTMs), so your page can count the booking. See [Redirect after booking](https://docs.dapta.ai/dcal/events/event-settings.md#redirect-after-booking).

### Can I add my Meta Pixel, Google Analytics 4 or Google Tag Manager?

Yes, per event. An owner or admin opens the event's **Tracking and pixels** section and adds a **Meta Pixel ID**, **Google Analytics 4 measurement ID**, **Google Tag Manager ID**, **PostHog project key** or **HubSpot tracking ID**. Each tag loads only on that event's booking page, embedded or not, and hears the page view, the day and time picked and the booking; dCal sends it the event's details and nothing about the guest. See [Tracking and pixels](https://docs.dapta.ai/dcal/events/event-settings.md#tracking-and-pixels).

### Do bookings keep the UTMs of my campaign?

Yes. Each booking made on your booking page keeps the `utm_source`, `utm_medium`, `utm_campaign`, `utm_term` and `utm_content` of the link the guest booked from; bookings made by an AI agent or with an API key keep none. On an embedded page they come from your page's address, as long as the embed code's `embed.js` script is on the page. You see them on the booking's own page in your dashboard, under **Campaign**: click the booking in **Bookings**. They also travel with your [webhooks](https://docs.dapta.ai/dcal/integrations/webhooks.md), the Cal.com-compatible API and the MCP tool `get_booking`, reach [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md) if you connected it, and go to your thank-you page when the event passes booking details. See [Track where bookings come from](https://docs.dapta.ai/dcal/share/your-booking-page.md#track-where-bookings-come-from).

***

## Integrations, agents and developers

### Can my Dapta agent book meetings on dCal?

Yes. Text Agents and Voice Agents can check your open times on dCal and book a meeting once the customer confirms, using the scheduling action in the Dapta app. No code needed. See [Let your Dapta agent book](https://docs.dapta.ai/dcal/dapta-agents.md).

### Does dCal work with HubSpot?

Yes. A workspace admin connects HubSpot once, and every accepted booking becomes a contact with a meeting on it. Reschedules and cancellations update the same meeting, and you can send booking answers to contact properties. See [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md).

### Can I send bookings to other tools?

Yes, two ways. A [webhook](https://docs.dapta.ai/dcal/integrations/webhooks.md) notifies your endpoint when a booking is created, rescheduled or cancelled. An [API key](https://docs.dapta.ai/dcal/developers/api-keys.md) lets your own systems read open times and create, list, reschedule and cancel bookings through the [REST API](https://docs.dapta.ai/dcal/developers/rest-api.md).

### Can I use dCal from ChatGPT, Claude or Cursor?

Yes. dCal's MCP server is available at `https://mcp.dcal.ai/mcp`, and an owner or admin connects an AI agent to it in one of two ways:

* **Sign in, no key.** Click **Connect your agent** in the left menu, pick your app (Claude, ChatGPT, Claude Code, Codex, Cursor, OpenClaw or Hermes) and follow its steps: you add the address and sign in with your Dapta account. You need to be an owner or admin of the workspace and to have opened dCal on the web there within the last 30 days. See [Connect Claude or ChatGPT by signing in](https://docs.dapta.ai/dcal/developers/connect-with-sign-in.md).
* **An API key.** For agents and scripts that run with no one to sign in, or any agent that should have narrower access, create a key in **API and webhooks** > **API keys** with only the access it needs, such as read only or one event type. See [Connect an AI assistant (MCP)](https://docs.dapta.ai/dcal/developers/mcp-server.md).

The agent can find and hold your open times, book, move or cancel meetings, answer booking requests and book with a team. Your own systems can also book through the [REST API](https://docs.dapta.ai/dcal/developers/rest-api.md), and your Text Agents and Voice Agents through [their scheduling action](https://docs.dapta.ai/dcal/dapta-agents.md).

### Is dCal open source? Can I host it myself?

Yes to both. dCal is open source under the MIT license at [github.com/Dapta-Tech/dapta-calendars-slate](https://github.com/Dapta-Tech/dapta-calendars-slate), and the repository includes a production guide. A copy you host uses your own sign-in, email provider and calendar backend instead of your Dapta account. See [Self-hosting](https://docs.dapta.ai/dcal/developers/self-hosting.md).

### What data do you keep about my guests, and can I delete it?

What the booking page collects: name, email, the time zone they booked in, notes, their answers, any phone number you ask for, other guests' emails and the language they booked in. No IP address and no device details. You can cancel a booking, but you cannot delete one from the dashboard today; for that, or any request about a guest's data, write to <support@daptatech.com>. See [Security and privacy](https://docs.dapta.ai/dcal/security-and-privacy.md#deleting-data).

## Related

* [Troubleshooting](https://docs.dapta.ai/dcal/troubleshooting.md): symptoms, causes and fixes for the problems that come up most.
* [Key concepts](https://docs.dapta.ai/dcal/key-concepts.md): the words these docs use.
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md): your booking page from the other 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/faq.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.
