> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Request reminders and escalation

> Set the reminders a request sends to the people answering it, escalate a request that is still not submitted to someone who can chase it, write the Escalation version of the reminder email, and send a reminder by hand.

For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL.

> [!NOTE]
>
> This guide is part of the [User Guides](https://docs.coverbase.com/user-guides/overview.md) collection. It covers the **Reminders** card in the portal template editor under **Configuration → Portal Templates**, the **Schedule** tab of one request, the **Escalation** version of a reminder email template under **Configuration → Communications**, and **Send reminder now** on the work queue's **Requests** tab. Pausing and closing a request, which stop its reminders, are in [Centralized supplier portal](https://docs.coverbase.com/user-guides/centralized-supplier-portal.md#pausing-rescheduling-or-closing-one-request). The emails themselves are listed in [Email and notifications](https://docs.coverbase.com/user-guides/email-notifications.md).

A request reminds the people it was sent to on a schedule you set. Escalation adds one more email, to someone else, when the request is still not submitted after a set number of days: a General Partner, the relationship owner, a risk analyst, or a team.

The mistake people make most often is turning escalation on for a template and expecting it to reach requests already sent. A request keeps the schedule it was created with, so tick **Also apply to open requests** when you save. Requests already past their escalation day then escalate once, on the next daily run.

## Where the schedule lives

* **On a portal template.** Open **Configuration → Portal Templates**, open a template, and find the **Reminders** card. Its schedule applies to requests created from the template.
* **On one request.** Open the request's configuration drawer and go to the **Schedule** tab.

A request copies its template's schedule when it is created. Changing the template's reminders never changes requests already sent, so change those on their own **Schedule** tab. Escalation is the exception: see [Apply escalation to requests already sent](#apply-escalation-to-requests-already-sent).

## What a schedule sends

Click **Add reminder** and pick a kind:

| Kind | Sends |
| - | - |
| **Relative to due date** | One reminder a number of days before the due date, on it, or after it. |
| **After invitation date** | One reminder a number of days after the invitation was sent. |
| **Recurring** | A reminder every few days, counted from the invitation date. |
| **Recurring after due date** | A reminder every few days once the request is past due. **Stop after** caps how many it sends; leave it empty for no limit. |

**Reminder email template** picks the email the schedule sends. On inherent risk, assessment and Know-Your-Vendor schedules, each reminder can also have its own **Email for this reminder**. A schedule with no reminders says "No reminders configured. This portal will not send reminders."

Reminders go only to requests that are sent, still open and not on hold. A submitted, paused or closed request gets none.

> [!NOTE]
>
> An inherent risk or Know-Your-Vendor request that was sent before November 19, 2026 and has no assessment behind it sends no scheduled reminders. **Send reminder now** and escalation still work for it.

## Escalate a request nobody has submitted

Escalation is on the schedules of inherent risk, assessment and Know-Your-Vendor requests. It is off until you turn it on.

**1. Turn it on**

At the foot of the **Reminders** card, or of a request's **Schedule** tab, switch on **Escalation**: "Email someone else, once, when a request is still not submitted."

**2. Pick the day**

Next to **If not submitted**, enter the number of days, then pick **days after it's sent** or **days after the due date**. A new escalation starts at 14 days after the request is sent.

**3. Pick who gets it**

Next to **Email**, click **Add** and search people, groups or fields:

* **Service fields**: any person field on the service, such as a General Partner field, and the service's **Relationship owner**, which is usually the person answering the request.
* **Vendor fields**: any person field on the vendor, the vendor's **Relationship owner**, and its **Risk analyst**.
* **People** and **Groups**: named people, or every member of a user group.

A field is read on each request, so a General Partner field on the service reaches the partner for that relationship.

**4. Decide on copies and the email**

**Also copy the person who sent the request** is on by default. **Email for the escalation** picks the reminder template whose **Escalation** version is sent. Leave it empty to use the schedule's own template, or the standard wording.

**5. Save**

Save the template, or the request's schedule. With escalation on and nobody picked, saving stops with "Choose who gets the escalation."

How it behaves:

* **On that day.** The escalation goes out on the day you set. A missed day is not made up, with two exceptions: a request you apply escalation to with **Also apply to open requests** while it is already past its day escalates on the next daily run, and a request on hold on its day escalates once on the first daily run after the hold lifts.
* **Once per request.** A request escalates at most once.
* **Someone always gets it.** If a field is empty on a request, or a group has nobody in it, the person who sent the request gets the escalation instead. People who have left your organization are skipped.
* **Only after a delivered invitation.** A request whose invitation failed or bounced for every recipient is not escalated, since the respondent never received it.
* **Only for requests still waiting.** A request that is submitted or closed is not escalated. A request that is paused, or whose supplier portal is closed, waits: if it was on hold on its escalation day, it escalates once on the first daily run after the hold lifts, if it is still not submitted. Lifting one hold that covered several requests' days escalates each of them once on the next run.
* **Recorded on the request.** The request's activity records the escalation, and the **Due** column on the work queue's [Requests tab](https://docs.coverbase.com/user-guides/work-queue.md#the-requests-tab) shows **Escalated** with the date.

### Apply escalation to requests already sent

When you save an escalation on a portal template, **Also apply to open requests** appears under it if some open requests from that template do not have this escalation yet. It says how many, and how many of those are already past the escalation day, for example "37 open requests from this template don't have this escalation yet. 22 were sent at least 14 days ago and escalate on the next daily run."

Tick it and save. The escalation is added to each of those requests, and a confirmation names how many. Then:

* **Requests already past their day escalate once, on the next daily run.** Requests not there yet escalate on their day, as usual.
* **Only the escalation is added.** Each request keeps its own reminders. A request sent before November 19, 2026 still sends no scheduled reminders; only the escalation reaches it.
* **Requests that already escalated are left alone**, and applying the same rule again changes nothing.
* **Only open requests that were sent.** Submitted, closed and unsent requests are not touched. A paused request gets the escalation and escalates after it resumes, if it is still not submitted.
* **Recorded.** **Configuration → Audit Logs** records who applied it, when, and to how many requests.

The option is unticked each time you open the template, so saving a template never reaches open requests unless you tick it.

## Write the Escalation version of the reminder email

Reminder email templates (**Inherent risk questionnaire reminders**, **Assessment reminders** and **Onboarding reminders**) have one version per situation, chosen under **Version to Edit**. **Escalation** is the last one, with the hint "Only sent when escalation is on in the reminder schedule." It has its own subject and message.

Open the template from the **Templates** list on **Configuration → Communications**, pick **Escalation** under **Version to Edit**, and write to the person you are escalating to rather than to the respondent. Three variables are filled only in this version:

| Variable | Fills in |
| - | - |
| **Days Since Sent** (`{{reminder::days_since_sent}}`) | Whole days since the request was sent, in Eastern time. |
| **Sent Date** (`{{reminder::sent_date}}`) | The day the request was sent, in Eastern time. |
| **Respondent Names** (`{{reminder::respondent_names}}`) | The people the request was sent to. |

A template saved before the **Escalation** version existed opens with the standard wording in it, and sends the standard wording until you save your own. The preview fills the variables with sample values.

## Send a reminder now

On the work queue's **Requests** tab, the row menu of a request offers **Send reminder now**. It sends the email the schedule would send, to the same people, straight away, and the request's activity records who sent it. You can send one per request per day. See [Send reminder now](https://docs.coverbase.com/user-guides/work-queue.md#send-reminder-now).

## Troubleshooting

| What you see | What is happening |
| - | - |
| I changed the template's reminders and a request already sent did not change | A request keeps the schedule it was created with. Change it on the request's **Schedule** tab. |
| There is no **Escalation** switch | The request type has none. Escalation is on inherent risk, assessment and Know-Your-Vendor schedules. |
| An escalation never went out | The request was created before escalation was on its template and nobody applied it to open requests, it was submitted or closed by that day, it is still on hold, or it already escalated once. |
| The escalation went to the sender, not the General Partner | The General Partner field was empty on that request. Fill in the field on the service or vendor. |
| The escalation used the standard wording | The template has no **Escalation** version saved, or **Email for the escalation** is empty and the schedule has no template. |
| An inherent risk request gets no reminders | It was sent before November 19, 2026. Use **Send reminder now**, or rely on escalation. |
| Reminders stopped | The request was submitted, paused or closed. See [Pausing, rescheduling or closing one request](https://docs.coverbase.com/user-guides/centralized-supplier-portal.md#pausing-rescheduling-or-closing-one-request). |

## Related

> [card] [Work queue](https://docs.coverbase.com/user-guides/work-queue.md)
>
> The Requests tab, where you see every request you sent and when it escalated.

> [card] [Centralized supplier portal](https://docs.coverbase.com/user-guides/centralized-supplier-portal.md)
>
> Pausing, rescheduling and closing a request, which stop its reminders.

> [card] [Email and notifications](https://docs.coverbase.com/user-guides/email-notifications.md)
>
> Every email Coverbase sends, and conditional sections in your email templates.

> [card] [Data model configuration](https://docs.coverbase.com/user-guides/data-model-configuration.md)
>
> Adding the person fields, such as a General Partner field, that an escalation can read.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.