> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/orchestration/how-to-alert-users-based-on-a-specific-date.md).

# How to alert users based on a specific date?

You can easily alert users a few days before or after a specific date. This is handy to manage expiry alerts, reminders and more.

Batch allows you to automatically send a notification to users a few days before a specific date in the future.

This is useful to alert users when their voucher, subscription, loyalty points or credit card is about to expire. You can also use that kind of campaign to send travel reminders, appointments, and more:

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FOsHiXB7HHoPBejRTLGyz%2FAppareils%20(1).png?alt=media&amp;token=7fd15088-acbc-4d8b-b3dd-366fa479845e" alt=""><figcaption></figcaption></figure>

## Pre-requisites

Batch only collects essential information on every installation (e.g. country, language, last visit date, etc).

Make sure you are sending all the additional data you need to manage your use cases. You can send custom data to Batch by tagging your app or sending data from your servers using the [Profile API](https://doc.batch.com/developer/api/cep/profiles).

You will find the list of the custom data received by Batch in **Data > Profile data**:

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2F8n2pJlYHrZvgDMSxMEm2%2FCleanShot%202025-09-05%20at%2017.24.12%402x.png?alt=media&amp;token=26f7261d-26c4-4883-a904-2231d13fdffc" alt=""><figcaption></figcaption></figure>

## 1. Targeting

Create a recurring automation, click **Add conditions** to select the attribute you will use to target the right users.

You can either use:

* **time in the future** to warn/remind users about a specific date coming up
* **time in the past** to remind users about a specific date in the past
* **time in the past occurred 0 days ago** to alert users on the D-day

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2Fi5kFfp44cbqTunlZVX2h%2FCleanShot%202025-05-07%20at%2018.01.05%402x.png?alt=media&amp;token=a6ca0d66-a0ee-4ec4-86f0-9f5d11a3db35" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
You can add a retargeting condition for users who already opened the first alert but didn't renew their subscription or for users who haven't opened it yet to remind them to make a specific action. You can even include an exclusive discount and therefore prevent churn.
{% endhint %}

## 2. Timing

Ensure you set the **Frequency** to 1 per day :point\_down:

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FyJJsAohb7npoeJFtqOhY%2FCleanShot%202025-05-13%20at%2017.19.12%402x.png?alt=media&amp;token=aa11529c-71c6-41d3-84b3-5396db1af750" alt=""><figcaption></figcaption></figure>

You won't need to set a capping for this type of automation, as this is important information and users should not trigger it often.

## 3. Message edition

Write your message by adding a title, a description and emojis.

You can even [personalize your notification](https://doc.batch.com/getting-started/features/customer-engagement-platform/message/personalization) based on the same custom data you are sending to Batch (e.g the first name, the number of loyalty points/miles/jackpot left). This will add more context to your message.

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FE3aTjecB9sWbGs4PpF6P%2FCleanShot%202025-05-14%20at%2017.19.20%402x.png?alt=media&amp;token=2ee86aed-6473-4e0b-808b-40d90754b7a8" alt=""><figcaption></figcaption></figure>


---

# 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://doc.batch.com/guides-and-best-practices/orchestration/how-to-alert-users-based-on-a-specific-date.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.
