> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/settings-1/email-notifications/reminders-for-expiring-services.md).
# Reminders for Expiring Services
## Configure Reminders for Expiring Services
The email notification for expiring services helps you inform the right people before a service reaches the end of its term.
This is useful when a service does not renew automatically and someone needs to take action before it expires. Depending on your internal process, this can mean planning a return, booking a follow-up service, reviewing the service, or preparing the next step.
You can find this notification in the email notification settings under **Expiring services**.
### Reminder timing
The field **Remaining term in days** defines when the reminder email should be sent before the service expires.
You can enter one or several day values.
For example:
`14, 7, 3, 1`
This sends reminder emails 14 days, 7 days, 3 days and 1 day before the expiration date.
Use comma-separated values to define multiple reminder points. Each number represents the number of days before the service ends.
### Reminder on the expiration date
You can also enable **Remind again on the day of expiration**.
When this option is active, equipme sends an additional reminder on the exact day the service expires. This can be useful as a final notification, especially when the service requires a return, renewal decision or follow-up action.
### Recipients
In the recipient settings, you can define who should receive the reminder email.
You can send the notification to affected employees, selected roles, or additional recipients.
Affected employees are the users connected to the expiring service. Roles are useful when a specific team should stay informed, for example an IT or operations role. Additional recipients can be used to notify individual email addresses that are not covered by the selected users or roles.
### Example
A service ends in 14 days and the reminder field contains:
`14, 7, 3, 1`
The selected recipients receive reminder emails 14 days before the expiration date, then again 7 days before, 3 days before and 1 day before the service ends.
If **Remind again on the day of expiration** is active, they also receive a final email on the expiration date itself.
### When to use several reminders
Several reminders are helpful when an expiring service needs preparation before it ends.
A single reminder can be enough for simple cases. For services that require coordination, several reminder points give the responsible people more time to react and reduce the risk of missing the expiration date.
This is especially useful for services where a return, cancellation, renewal decision or follow-up booking needs to be handled before the service expires.
---
# 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://hub.equipme.io/equipme/settings-1/email-notifications/reminders-for-expiring-services.md?ask=&goal=
```
`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.