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

# Emails

dCal emails your guest and you at every step of a booking: confirmations, requests, reschedules, cancellations, reminders and an optional follow-up. See what is sent, where to turn each email on or of

dCal sends an email at every step of a booking, to your guest and to you. There is nothing to set up: every email except the follow-up is on from the start. This section explains who receives what, and where you change it.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-39593c3cb0e2299fc0c927051b66c85931126e27%2Fdcal-customize-emails-01-notifications-page.png?alt=media" alt="The Notifications tab with the Attendee emails section (five emails) and the Host emails section (four emails), every email switched on, each with an Edit template button"><figcaption><p><strong>Settings</strong> > <strong>Notifications</strong>: the booking emails of your workspace, each with its own switch.</p></figcaption></figure>

***

## What dCal sends

| When                                                      | Your guest receives                              | You and your co-hosts receive                         |
| --------------------------------------------------------- | ------------------------------------------------ | ----------------------------------------------------- |
| Someone books                                             | **Booking confirmed**, with the calendar invite  | **New booking**, with the guest's details and answers |
| Someone sends a request (the event requires confirmation) | **Request received**                             | **New booking**, marked as needing your OK            |
| You confirm a request                                     | **Booking confirmed**, with the calendar invite  | **New booking**                                       |
| You decline a request                                     | **Request declined**                             | **Request declined**                                  |
| Your guest reschedules                                    | **Booking rescheduled**, with the updated invite | **Booking rescheduled**                               |
| You or your guest cancel                                  | **Booking cancelled**                            | **Booking cancelled**                                 |
| Before the meeting                                        | One **Reminder** for each reminder that is on    | Their own copy of each reminder                       |
| After the meeting, when you turn it on                    | **Follow-up**                                    | Nothing                                               |

The full detail (subjects in English and Spanish, attachments, language and time zone rules) is in [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md).

***

## Where you control emails

| What you want to change                                                                 | Where                                  | Who can change it                                                                                                             |
| --------------------------------------------------------------------------------------- | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Turn a booking email on or off for the whole workspace, or rewrite its subject and text | **Settings** > **Notifications**       | Admins and owners. See [Customize your emails](https://docs.dapta.ai/dcal/emails/customize-emails.md).                        |
| Reminders before the meeting and the follow-up after it: how many, when, and their text | The **Reminders** tab of each event    | Anyone who can edit the event. See [Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md). |
| Whether bookings arrive as requests that you confirm                                    | **Requires confirmation** on the event | Anyone who can edit the event. See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md).         |

***

Use **Preview email** in an event's **Reminders** tab to check a reminder or follow-up with your unsaved changes. The preview uses a sample booking and sends nothing. See [Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md).

***

## Good to know

* **Sender.** Booking emails come from **dCal**, at `calendars@notifications-dapta.ai`, and end with one footer, in the language of the email, saying they are an automated notification from dCal and how to reach dCal support. A guest's reply goes to dCal support, `support@daptatech.com`. The sender can't be changed per workspace.
* **Two versions in one email.** Every email carries a formatted version, which most mail apps show, and a plain-text version for apps that can't show formatting.
* **Retries.** If an email can't be sent, dCal tries again automatically, waiting longer each time, for up to 24 hours. An email the mail service refuses for good, for example to an address that bounced before, is not retried: it is skipped at once.
* **Emails that no longer apply are skipped.** A confirmation, reschedule, reminder or follow-up still waiting to go out is dropped if the booking was cancelled or declined in the meantime, and a reminder that could not go out before the meeting started is not sent late.
* **Meeting links.** For an online meeting with a connected calendar, including an event whose location is **Not specified**, the confirmation waits at least 15 seconds so it can include the meeting link. If the link is still not ready after a few more tries, the email goes out without it. Reminders pick up the link when they are sent.
* **Calendar invites.** The confirmation, the reschedule and the cancellation carry a calendar file that adds, updates or removes the event in your guest's calendar. It is your guest's only invitation: your connected calendar does not send its own, except in the few cases listed in [The calendar invite](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md#the-calendar-invite).
* **Manage links.** The **Manage your booking** and **Manage your request** buttons open your guest's manage page on `book.dcal.ai`.
* **Dapta badge.** Above that footer, your guest's emails carry a **Made with dCal.ai by Dapta · Create your free calendar** line, unless your workspace hides Dapta branding. Both parts link to [dcal.ai](https://dcal.ai), and the plain-text version carries the same line with the address written out. See [The Dapta badge](https://docs.dapta.ai/dcal/design/dapta-branding.md).
* **Invitations to your workspace.** When an owner or admin invites someone from **Settings** > **Members**, dCal emails them an invitation to join. It is not a booking email: it has no switch in **Notifications**, and its text cannot be edited. See [Invite teammates](https://docs.dapta.ai/dcal/account/invite-teammates.md).

***

## In this section

{% content-ref url="/pages/oCTs0Y0GFlPh2nNiIuMd" %}
[Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md)
{% endcontent-ref %}

{% content-ref url="/pages/swe6ZSIMYvjxewKS3Ljz" %}
[Reminders and follow-ups](https://docs.dapta.ai/dcal/emails/reminders-and-follow-ups.md)
{% endcontent-ref %}

{% content-ref url="/pages/zUwASp0HMANgOpZHpZft" %}
[Customize your emails](https://docs.dapta.ai/dcal/emails/customize-emails.md)
{% endcontent-ref %}

## Related

* [Bookings](https://docs.dapta.ai/dcal/bookings.md): the statuses and changes that trigger these emails.
* [Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md): the request emails, step by step.
* [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md): the link your guest uses from their emails.
* [Webhooks](https://docs.dapta.ai/dcal/integrations/webhooks.md): get the same moments in 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/emails.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.
