> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/reminders-and-notifications/reminder-sequences.md). # Reminders and notification sequences How automatic reminders work, and how to replace Pipefile's stock emails and texts with your own wording. ## How reminders work Every request has a reminder frequency, set under **Reminders** when you create the request or template. Choose **Never**, **Everyday**, or every 2, 3, 4, 5, 6, 7 or 14 days. New requests and templates default to every 3 days. Pipefile sends an automated reminder once that many days have passed since the request was sent or since the last reminder. Reminders go out by email, and by text to recipients with a phone number on plans with [SMS reminders](/reminders-and-notifications/sms-reminders.md). Automated reminders stop when: * the recipient finishes: for an open-ended request, after their first upload; for a checklist, once every item is answered. If you reject an item or mark it incomplete, the request goes back to waiting and reminders resume. * you mark the request completed or archive it. * the request expires. See [Expiration, completion and reopening](/requests/expiration-and-reopening.md). Other details: * Automated reminders aren't sent overnight (roughly midnight to 8 a.m. US Eastern time). A reminder that falls due then goes out later that morning. * A recipient who has signed every field they owe on a multi-signer request isn't reminded while they wait for others. * A recipient who unsubscribed from a request's emails gets no automated reminders. A reminder you send by hand still reaches them by email. The request page shows the frequency under **Reminders** and when the last one went out. To nudge someone now, click **Send reminder** on the request. ## Notification sequences {% hint style="info" %} Available on the **Standard**, **Professional** and **Enterprise** plans. {% endhint %} A notification sequence replaces Pipefile's stock wording in the messages your recipients get. One sequence covers four moments, each with an email version and a text version: | Section | When it's sent | | ------------------- | -------------------------------------------------------------------------------------------------------------------- | | **Initial Request** | When you send a new request. | | **Reminders** | With each reminder. Add several and Pipefile picks one at random each time, so repeat reminders don't read the same. | | **Review** | When you approve, reject or mark checklist items incomplete. | | **Completed** | When you mark a request completed. | ### Create a sequence {% stepper %} {% step %} ### Open Notification sequences Go to [Settings → Notification sequences](https://pipefile.com/dashboard/settings/sequences) and click **Create sequence**. {% endstep %} {% step %} ### Name it Enter a **Sequence Name**. Recipients don't see it; it's how you pick the sequence later. {% endstep %} {% step %} ### Write each message Use the **Email** and **SMS** buttons at the top to switch between versions. For each section: * Leave **Use Default?** on to keep Pipefile's stock message. * Turn it off to write your own. Email needs a **Subject**, **Message** and **Button Text** (the **Completed** email has no button). SMS needs a **Message**. Every section you customize needs both an email and an SMS version, even if you don't text recipients. Under **Reminders**, click **Add Reminder Template** to add variations. {% endstep %} {% step %} ### Save Click **Create Sequence**. To change it later, click the pencil icon next to it on the **Notification Sequences** page and click **Save Sequence**. {% endstep %} {% endstepper %} Email messages can use Markdown, such as `**bold**` and links. Pipefile adds the request link to the initial and reminder texts automatically. ### Use a sequence When you send a request, click **Advanced** in the **Send Request** dialog and choose it under **Notification Sequence (Choose One)**. **Default Sequence** means Pipefile's stock messages. The menu appears once you have at least one sequence. Set it on a [template](/templates/create-and-edit-templates.md) the same way so every request from that template uses it. New sequences are shared with your team, so teammates can choose them too. Requests link to the sequence rather than copying it. Editing a sequence changes the messages for every request that uses it, including reminders on requests already sent. Deleting a sequence (trash icon, then **Delete Sequence**) switches those requests back to Pipefile's stock messages. ### Variables Insert details into subjects and messages with `{{ variable }}`. For example: `Hi {{ firstName }}, we still need your documents for {{ subject }}.` | Variable | Inserts | | ----------------------------------------------------- | ----------------------------------------------------------------- | | `{{ name }}` | The recipient's full name | | `{{ firstName }}` | The recipient's first name | | `{{ email }}` | The recipient's email address | | `{{ subject }}` | The request's subject | | `{{ message }}` | The request's message | | `{{ recipient0_name }}`, `{{ recipient1_name }}`, ... | A recipient's full name by position on the request, starting at 0 | | `{{ recipient0_firstName }}`, ... | That recipient's first name | | `{{ recipient0_email }}`, ... | That recipient's email address | | `{{ tag0 }}`, `{{ tag1 }}`, ... | The request's tags, by position, starting at 0 | A variable that doesn't apply, such as `{{ recipient2_name }}` on a request with two recipients, prints nothing. Variable names are case-sensitive: `{{ firstName }}` works, `{{ firstname }}` doesn't. ## Related * [Your notification settings](/reminders-and-notifications/notification-settings.md): the emails you receive. * [Send requests in another language](/requests/translations.md) * [Emails not arriving](/troubleshooting/emails-not-arriving.md) --- # 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://support.pipefile.com/reminders-and-notifications/reminder-sequences.md?ask=&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.