> For the complete documentation index, see [llms.txt](https://docs.autentique.com.br/api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autentique.com.br/api/mutations/criando-um-documento/signature-reminders.md).

# Signature reminders

Signature reminders help keep the process moving when a signer has not yet signed the document. They are sent automatically and can follow a daily or weekly schedule.

The `reminder` field can be used when creating or updating documents.

#### Reminder Frequency

The following frequencies are available:

| Value    | Behavior                | Limit             |
| -------- | ----------------------- | ----------------- |
| `DAILY`  | Sends reminders daily.  | Up to 7 reminders |
| `WEEKLY` | Sends reminders weekly. | Up to 4 reminders |

Reminders stop when the signer signs or rejects the document, even if the reminder limit has not yet been reached.

{% hint style="info" %}
Only signers added by email will receive signing reminders. Signers added by phone number or through a signing link will not receive them.
{% endhint %}

To create a document with daily reminders:

```json
{
  "document": {
    "name": "Service Agreement",
    "reminder": "DAILY"
  }
}
```

To send reminders weekly:

```json
{
  "document": {
    "name": "Service Agreement",
    "reminder": "WEEKLY"
  }
}
```

#### Reminders and Rejection

When `reminder` is set to `DAILY` or `WEEKLY`, the API automatically enables the `refusable` field.

This allows signers to reject the document during the signing process, even if `refusable` was not explicitly provided:

```json
{
  "document": {
    "reminder": "DAILY"
  }
}
```

Internally, this configuration behaves as follows:

```json
{
  "reminder": "DAILY",
  "refusable": true
}
```

{% hint style="warning" %}
You cannot keep reminders enabled while preventing signers from rejecting the document. Enabling `reminder` automatically allows the document to be rejected.
{% endhint %}

#### Stopping the Process After a Rejection

The `stop_on_rejected` field determines whether the process should stop when a signer rejects the document.

When enabled, the remaining signers will no longer be able to sign the document after a signer rejects it.

```json
{
  "document": {
    "refusable": true,
    "stop_on_rejected": true
  }
}
```

{% hint style="info" %}
The `stop_on_rejected` field can only be enabled when `refusable` is active. Because reminders enable `refusable` automatically, both behaviors can be combined.
{% endhint %}

#### Behavior Summary

| Configuration                                    | Result                                                                                    |
| ------------------------------------------------ | ----------------------------------------------------------------------------------------- |
| `reminder: "DAILY"`                              | Sends reminders daily and enables `refusable`.                                            |
| `reminder: "WEEKLY"`                             | Sends reminders weekly and enables `refusable`.                                           |
| `refusable: true`                                | Allows signers to reject the document.                                                    |
| `stop_on_rejected: true`                         | Stops the process after a rejection.                                                      |
| `stop_on_rejected: true` with `refusable: false` | Invalid configuration.                                                                    |
| `reminder` with `stop_on_rejected: true`         | Sends reminders, allows signers to reject, and stops the process when a rejection occurs. |