> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/advanced-features/rules/templates/automatic-follow-ups.md).

# Automatic follow ups

Template: Send automatic follow-up reminders.

A **Missive rule template** for sales teams. Send a quote, and Missive follows up for you, up to 3 times, until the contact replies.

#### Here's how it works:

* You need a **trigger phrase** in your first email, like "Here is the quote you requested."
* You need a [**canned response**](https://missiveapp.com/docs/core-features/canned-responses) for each follow-up
* You need a **label** to track deals in progress

***

### Outgoing email rule: Automatic follow ups

<a href="https://mail.missiveapp.com/?importRule=auto-follow-up-steps_outgoing-message" class="button primary" data-icon="plus">Add to Missive</a>

| Rule or step                      | Wait   | If                                                        | Then                      |
| --------------------------------- | ------ | --------------------------------------------------------- | ------------------------- |
| **Rule:** Auto follow-up sequence | -      | Sent from your sales address, contains the trigger phrase | Add your label            |
| Follow-up 1                       | 1 day  | **Not replied** by the recipients                         | Send the first follow-up  |
| ↳ Follow-up 2                     | 2 days | **Not replied** by the recipients                         | Send the second follow-up |
| ↳ ↳ Follow-up 3                   | 4 days | **Not replied** by the recipients                         | Send the third follow-up  |

The follow-ups go out 1, 3 and 7 days after your email. As soon as the contact replies, they stop. If the customer replies on day 4, they get the first two follow-ups and never the third.

{% hint style="info" %}
Nobody answered after all that? Add a last step to label the conversation "No answer" and close it. See [Steps](/docs/advanced-features/rules/steps.md).
{% endhint %}

***

### Triggering via API

You can trigger this rule from external systems (websites, CRMs, etc.) by sending the initial email via the [Missive REST API](https://missiveapp.com/docs/developers/rest-api/endpoints#drafts).

When you send an email via API with `send: true`, outgoing rules run automatically. Include your trigger phrase in the email body to start the follow-up sequence.

See [Automated email sequences](https://missiveapp.com/docs/developers/rest-api/endpoints#use-case-automated-email-sequences) in the API documentation for implementation details.


---

# 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://missiveapp.com/docs/advanced-features/rules/templates/automatic-follow-ups.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.