> 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/steps.md).

# Steps

Run more actions later with rule steps. Build SLA flows and follow-up sequences.

A step is a little rule that runs later. It waits, looks at the conversation again, and acts if it needs to.

Use steps to chase an unanswered support email, or to follow up on a quote until the contact replies.

## Why steps?

A rule acts the moment it triggers. Steps let it come back later:

* **Wait, then check.** Did someone reply? Is the conversation still open? Who's assigned?
* **Wait, then act.** Notify, label, assign, send a response, close.
* **Do it again.** Add a step under a step to escalate after 1 hour, then 4 hours, then a day.
* **Plan for both outcomes.** Put two steps side by side: one for "we replied in time", one for "we didn't".

All of it lives in one rule.

## An example

Here's an SLA flow for a support team:

| Rule or step             | Wait    | If                                            | Then                                       |
| ------------------------ | ------- | --------------------------------------------- | ------------------------------------------ |
| **Rule:** Support SLA    | -       | **Team** is Support                           | Nothing                                    |
| Answered within the hour | 1 hour  | **Replied** by anyone in our organization     | Add label SLA · Met                        |
| Remind the assignees     | 1 hour  | **Not replied** by anyone in our organization | Add label SLA · Late, notify the assignees |
| ↳ Escalate to the team   | 3 hours | **Not replied** by anyone in our organization | Add label SLA · Breached, notify the team  |

An email lands in the Support team. One hour later, either the first step labels it as met, or the second one reminds the assignees. Still no reply 3 hours after that? The whole team hears about it.

{% hint style="info" %}
**The top rule picks the conversations. The steps do the work.**

In an SLA flow or a follow-up sequence, the rule at the top (**Support SLA** above) usually has conditions and no actions. Its conditions pick the conversations to track. The steps under it wait, check, and act.
{% endhint %}

## Add a step

1. Go to **Settings** > **Rules**.
2. On a rule, click **•••** > **Add a step**.
3. Set how long the step waits. Select business hours to skip nights and weekends.
4. Add conditions and actions, then click **Create step**.

Each step waits from the step above it. To add a step under a step, click **•••** > **Add a step** on that step.

## Good to know

* When the top rule triggers again on the same conversation, its steps start over. A new customer email restarts the SLA clock.
* Messages sent by your rules don't count as replies. Your follow-ups won't stop your own sequence.
* Steps can check the conversation, not the original message. To filter on things like **From** or **Subject**, use the conditions of the top rule.

## Related

* [Conditions](https://missiveapp.com/docs/advanced-features/rules/conditions.md)
* [SLA and response time examples](https://missiveapp.com/docs/advanced-features/rules/examples/sla-and-response-time.md)
* [Basic Service Level Agreement template](https://missiveapp.com/docs/advanced-features/rules/templates/sla-basic-templates.md)
* [Automatic follow ups template](https://missiveapp.com/docs/advanced-features/rules/templates/automatic-follow-ups.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://missiveapp.com/docs/advanced-features/rules/steps.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.
