> 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/inbox-zero-on-weekends.md).

# Inbox Zero on weekends

Template: Auto-archive non-urgent emails on weekends.

**Inbox Zero on weekends** is a **Missive rules template** designed for people that want to keep any weekend emails clear of their inbox until Monday. With this rule, you’ll be able to have disruption-free weekends while ensuring an up-to-date inbox on Monday morning.

#### When enabled:

* The rule will snooze any incoming emails received during the weekend until the following Monday where they will show up in your inbox.

#### Here’s how it works:

* You need to determine what timeframe counts as the weekend
* You need to determine when you'd like to snooze until

***

### Incoming email rule: Inbox Zero on weekends

This rule is meant to automatically clear your inbox of any incoming emails during the weekend, and resurface them on Monday when you're back at work.

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

#### There is one condition and one action to make this rule work.

{% stepper %}
{% step %}
If an email is received during the "weekend" **reception time**...
{% endstep %}

{% step %}
It will automatically **snooze** that email until **8am of the next weekday**. By snoozing, the rule will also remove that email from your inbox and unassign you.

Once Monday at 8am hits, the rule will move that snoozed email back to your inbox.
{% endstep %}
{% endstepper %}

<div data-with-frame="true"><figure><img src="https://3242897856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1If7JwIQhfz5wGM9LiIU%2Fuploads%2FWJp4ftow7KvdaakSBulh%2FSnooze-weekend.png?alt=media&amp;token=b5abd570-bfec-4d6e-b811-33aa48ddb464" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="220.484375">Component</th><th>Value</th></tr></thead><tbody><tr><td>Condition</td><td><strong>Reception time</strong> is not within Mon-Fri 9am-6pm</td></tr><tr><td>Action</td><td><p><strong>Snooze</strong> until Monday 8am</p><p><br></p></td></tr></tbody></table>


---

# 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/inbox-zero-on-weekends.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.