> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/automations/automated-workflow-for-booking-related-events/booking-reminder-template/setting-up-time-intervals-for-booking-reminder-automation.md).

# Setting Up Time Intervals for Booking Reminder Automation

{% embed url="<https://youtu.be/Af36oTwuVsM>" %}

Timely reminders play a key role in reducing no-shows and keeping your customers engaged. With Mercuri CX, you can easily configure when these reminders are sent.

**Default Intervals:**

* A reminder is sent **24 hours (1 day)** before the appointment.
* Another reminder is sent **1 hour** before the appointment.

If preferred, you can remove one of these intervals, but at least one reminder must always be set up.

**Adding Custom Intervals:**

1. During automation setup, navigate to the Reminder Configuration section.
2. Click on “Add Another Reminder”.
3. Choose your preferred interval (e.g., 2 days before, 6 hours before, or 30 minutes before the appointment).

{% hint style="info" %}
📌 **Note:** *The reminder may be delivered up to **10 minutes earlier or later** than the exact scheduled time.*
{% endhint %}

### Best Practices:

* Always set at least one reminder (mandatory).
* Avoid overwhelming customers with too many notifications; 2 to 3 well-timed reminders are often most effective.
* Consider your customer’s time zone when scheduling reminders.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mercuri.cx/features/automations/automated-workflow-for-booking-related-events/booking-reminder-template/setting-up-time-intervals-for-booking-reminder-automation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.