# Deep work & Cooldown modes

<figure><img src="/files/X040zQNUXrDXhniVcdFS" alt=""><figcaption></figcaption></figure>

## Cooldown & Deep work mode

Both modes were designed with responder well-being in mind, offering much-needed breaks and uninterrupted work time. By allowing responders to rest or focus without being constantly alerted, these modes support better mental clarity and reduce alert fatigue.

While these modes currently operate independently, we may consider grouping them into a unified "Do Not Disturb" mode in the future. The goal is to give responders the flexibility to control when and how they receive alerts without sacrificing incident response quality.

### Deep Work Mode

Deep Work Mode is intended for responders who need uninterrupted time for focused work. When enabled, this mode temporarily suppresses all non-critical incident alerts (except SEV1) for either 4 or 8 hours. These options are preset and cannot be edited. During this time, you can focus on your work without the distraction of lower-severity alerts.

You will receive critical incident (SEV1) alerts.

{% tabs %}
{% tab title="Setup on desktop" %}

* Access the dropdown from the header that says `Select a mode`
* Enable **Deep Work Mode** for either 4 or 8 hours with a single click.
  {% endtab %}
  {% endtabs %}

***

### Cooldown Mode

Cooldown Mode is designed for responders who need a break after handling incidents, such as an overnight shift. This mode pauses all alerts for either 12 or 24 hours, depending on the option selected. During this period, responders will not receive any incident alerts, allowing them to rest and recharge.

You will receive critical incident (SEV1) alerts.

{% tabs %}
{% tab title="Setup on desktop" %}

* Access the dropdown from the header that says `Select a mode`
* Select **Cooldown Mode** for either 12 or 24 hours with a single click.
  {% endtab %}
  {% endtabs %}

***

#### Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Resolved incident alerts</strong></td><td>Alerts when incidents are resolved</td><td><a href="/pages/tcItPmwLUl0mWX7hXPRN">/pages/tcItPmwLUl0mWX7hXPRN</a></td><td><a href="/files/i02pHCAcjjxEDvLvnL2g">/files/i02pHCAcjjxEDvLvnL2g</a></td></tr><tr><td><strong>During office hours</strong></td><td>Custom routing of alerts during office hours</td><td><a href="/pages/kby7JcfG1pXkgf8Ous1f">/pages/kby7JcfG1pXkgf8Ous1f</a></td><td><a href="/files/Op8TdsJtI6CglwNLrbaJ">/files/Op8TdsJtI6CglwNLrbaJ</a></td></tr><tr><td><strong>Out of office</strong></td><td>Step away confidently by scheduling Out of office</td><td><a href="/pages/z6JBKPPBPBlr6lmjsAGu">/pages/z6JBKPPBPBlr6lmjsAGu</a></td><td><a href="/files/0UUQeewHIUzNsP1o13I5">/files/0UUQeewHIUzNsP1o13I5</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.spike.sh/alerts/personal-alerts-management/deep-work-and-cooldown-modes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.