> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/scheduling/reminders.md).

# Configure reminders and no-show follow-up

Attach reminders to an event so guests and hosts receive the right message at the right time.

## Add a reminder

1. Open the event type's messaging controls.
2. Choose the reminder template and guest or host audience.
3. Choose timing **before the meeting starts** or **after the meeting ends**.
4. Select a preset offset or **Custom…** and enter the supported number of minutes.
5. Save the event and preview the template.

Custom offsets run from five minutes to two weeks. Check the event's actual settings rather than assuming every event inherits the same reminder.

Use [Email templates](/scheduling/email-templates.md) for wording, placeholders and appearance. SMS needs Twilio and a usable recipient phone number; review the email fallback choice when offered.

## After a meeting changes

Rescheduling moves the relevant reminder timing. Cancellation and no-show outcomes affect pending messages. Check the final meeting state before troubleshooting a reminder that was intentionally stopped.

## Follow up on no-shows

Create a workflow using **Meeting lifecycle** with the appropriate no-show condition. Notify the owner or start a supported follow-up sequence after checking consent and your team's process.

Mark the meeting as a no-show from its management controls. A lack of attendance is not inferred merely because the clock reached the scheduled end.

See [Meeting messages](/scheduling/messages.md) and [No-show follow-up recipe](/guides/no-show-follow-up.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/scheduling/reminders.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 `build a script that syncs our docs to a CMS` 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.