> 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/reminders-and-follow-ups.md).

# Reminders and follow-ups

dCal emails reminders before each meeting and, if you want, a thank-you after it. Set them per event: how many reminders, how long before the start, and your own wording with variables such as the gue

Reminders help your guests show up: dCal emails your guest, and you, before the meeting starts. A follow-up thanks your guest once the meeting is over and invites them to book again. Both live on each event, in its **Reminders** tab, not in **Settings**.

***

## What every new event starts with

| Email     | When                              | State |
| --------- | --------------------------------- | ----- |
| Reminder  | 1 day (24 hours) before the start | On    |
| Reminder  | 1 hour before the start           | On    |
| Follow-up | 1 hour after the end              | Off   |

You can change all three, add more reminders, or remove them.

***

**Step 1:** Click **Events** in the left menu and open the event. Select the **Reminders** tab. The section reads "Reminders belong to this event. Each one has its own switch, timing and wording."

***

**Step 2:** Under **Before the meeting**, set each reminder:

* Tick the box next to **Send** to switch the reminder on, or untick it to switch it off without losing its settings.
* Type a number and choose **minutes**, **hours** or **days**, then **before it starts**. A reminder can go out from 5 minutes to 28 days before the start.
* Click the **×** at the end of the row to remove the reminder.

Click **Add reminder** to add one more: it is added switched on, one hour before the start. An event can have up to 10 reminders; at that point the form says **Up to 10 reminders on one event.** When an event has no reminders at all, the section says so: your guests get no reminder before that event.

***

**Step 3 (optional):** Write your own wording. Each reminder has a **Subject** box and a **Message** box. Leave them empty to use the standard wording. Click a variable under **Variables** to insert it where your cursor is, in the subject or in the message.

| Variable             | Becomes                                                                                     |
| -------------------- | ------------------------------------------------------------------------------------------- |
| `{{attendee_name}}`  | Your guest's name.                                                                          |
| `{{attendee_email}}` | Your guest's email address.                                                                 |
| `{{host_name}}`      | Your name.                                                                                  |
| `{{event_title}}`    | The event title.                                                                            |
| `{{start_time}}`     | The start date and time, in your guest's time zone, for example `Sat, Aug 1, 11:00 AM EDT`. |
| `{{end_time}}`       | The end date and time, in the same format.                                                  |
| `{{location}}`       | The event's location.                                                                       |
| `{{meeting_url}}`    | The online meeting link, when the meeting has one.                                          |
| `{{manage_url}}`     | Your guest's link to reschedule or cancel. Empty on a booking that started as a request.    |
| `{{reminder_lead}}`  | How soon the meeting starts, for example `in 24 hour(s)` or `in 30 minutes`.                |
| `{{booking_link}}`   | The address of this event's booking page, to book again.                                    |
| `{{form.<name>}}`    | Your guest's answer to one of this event's booking questions, by the question's name.       |

Under **From this event’s questions** there is one chip for each booking question, for example `{{form.company}}`. With no questions on the event, it says **Add a question above to use its answer here.** If you later remove or rename a question a reminder uses, the form warns "These variables no longer match a question and will arrive empty:" followed by the variables concerned.

A line whose variables all come out empty is left out of the email, so a line such as `Join the meeting: {{meeting_url}}` disappears on a meeting with no link. The subject holds up to 200 characters and the message up to 5,000.

> **⚠️ Note:** Your own message goes into the plain-text version of the email. Most mail apps show the formatted version, which keeps the standard layout with the meeting facts. Your subject shows in every app, so put what matters most there.

***

**Step 4 (optional):** Turn on the follow-up. Under **After the meeting** ("A thank-you sent once the meeting is over. Off unless you turn it on."), tick the box next to **Send** and choose how long **after it ends** it goes out. You can write your own subject and message the same way. An event has one follow-up.

***

**Preview before saving:** Click the eye button (**Preview email**) on a reminder or on the follow-up. **Email preview** shows the subject, sender, recipient and formatted email for a sample booking, using your unsaved changes. It sends no email. Your custom message belongs to the plain-text version; the formatted preview keeps the standard layout. Close the preview to keep editing.

**Step 5:** Click **Save changes** (**Create event** on a new event). Reminders are saved with the rest of the event.

***

## Who receives what

|                       | Reminder                                                                                           | Follow-up                                            |
| --------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| Your guest            | Yes: your wording or the standard one, with the meeting facts and a **Manage your booking** button | Yes: a thank-you with a **Book another time** button |
| You and your co-hosts | Yes, at the same time, always in the standard wording                                              | No                                                   |

* Your guest's reminder shows **Reminder**, the event title, a line reminding them of their meeting with you, the meeting facts and a **Manage your booking** button.
* Your copy goes out at the same time, names your guest, and always uses the standard wording. Your custom subject and message apply to your guest's copy only.
* The box next to **Send** controls both copies: switching a reminder off stops your guest's copy and yours.
* Reminders and the follow-up carry no calendar file: the event is already in the calendar from the confirmation.

Your guest's reminder is written in the language they booked in and shows times in their time zone. Custom wording is sent as you wrote it, with dates in English. See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md#language-and-time-zone).

***

## When they are sent

* **Only for accepted bookings.** Reminders are scheduled when a booking is made, or when you confirm a request. A request still waiting for your OK gets none.
* **Past send times are skipped.** A reminder whose time has already passed when the booking is made is not sent. For example, a booking made 30 minutes before the start gets neither the 24-hour nor the 1-hour reminder.
* **Reschedules move them.** When your guest reschedules, the reminders and the follow-up move to the new time.
* **Cancellations drop them.** When a booking is cancelled or a request declined, its reminders and follow-up are dropped.
* **Switching off applies to booked meetings too.** Switching a reminder off, or removing it, also stops it for bookings that are already made.
* **Meeting links arrive late, reminders catch them.** A reminder reads the online meeting link when it is sent, so a link created after the confirmation still reaches your guest.

> **💡 Tip:** On a booking that started as a request, the reminders your guest receives after you confirm have no **Manage your booking** button. Your guest reschedules or cancels from their **Request received** email. See [Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md).

## Related

* [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md): every email dCal sends, with subjects in English and Spanish.
* [Customize your emails](https://docs.dapta.ai/dcal/emails/customize-emails.md): the booking emails that live in **Settings** > **Notifications**.
* [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md): the rest of the event's settings.
* [Booking questions](https://docs.dapta.ai/dcal/events/booking-questions.md): the questions behind `{{form.<name>}}`.


---

# 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/reminders-and-follow-ups.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.
