> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/esignatures/reminder-settings.md).

# Reminder Settings

### Reminder Settings

To help ensure documents are signed promptly, Docupilot lets you set up reminder settings that notify recipients at regular intervals. You can choose to:

* Use the default reminder settings configured at the account level.
* Or, disable the default and define custom rules such as first reminder date, reminder frequency, and expiry warning.

If the envelope is in Pending status, you can update the reminder settings directly from the Signature Details Page. A Send Reminder button is also available beside the History icon for quick manual follow-up.

> Note that manually sending reminder will not affect the reminder workflow. Reminders scheduled to be sent based on First Reminder, Reminder Frequency and Expiry Warning will still be sent as scheduled.

### Configuring Expiry

Set how long an envelope is valid before it expires. Once expired, recipients can no longer access or sign the document. This is useful for time-sensitive agreements or approvals.

### Default Reminder & Expiry Settings

By default the reminder and expiry settings are as follows:

1. **First reminder:** 3 days from the date a recipient recieves an envelope for signing.
2. **Reminder frequency:** 2 days - current signer will receive a reminder to sign once every 2 days after the first reminder is sent.
3. **Warn before expiration:** 5 days - current signer will receive an email 5 days before the envelope expiration.
4. **Expiry:** 30 days - envelope will expire in 30 days after it is sent.


---

# 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://help.docupilot.app/esignatures/reminder-settings.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.