> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/alerts/personal-alerts-management/out-of-office.md).

# Out of office

<figure><img src="/files/t0MjTUT5gzT4929sd67H" alt="Out of office mode in Spike"><figcaption><p>Schedule Out of office and offload duties to a teammate.</p></figcaption></figure>

## Out of office

Heading out of the office? You can schedule or instantly set up **Out of Office**, so your duties including on-call responsibilities and incident alerts are covered by a colleague.

Out of Office mode is designed to support better work-life balance. **While you're away, Spike will not send you any alerts**. You can even schedule this ahead of time, and an email will be sent to the admins in your organization, keeping everyone informed.

### Offloading Duties

When setting up Out of Office, you can offload your responsibilities to a selected team member. Spike takes care of everything automatically—there’s no need to manually move members in the on-call schedule or add overrides. Your on-call shifts and incident alerts will be temporarily rerouted to the designated member.

{% hint style="info" %}
Although optional, we recommend offloading your duties to make sure incidents are addressed in your absence and you are not disturbed.
{% endhint %}

#### Set up

{% tabs %}
{% tab title="From settings on Desktop" %}

* Navigate to `Your account settings` ([Dashboard link](https://app.spike.sh/settings/personal-modes#vacation-mode))
* Click `Modes`
* Scroll down to **Out of office**
* Add **Starts on** and **Ends on**, then click `save`

*Optionally, select a member to offload duties*
{% endtab %}

{% tab title="From the header on Desktop" %}

* From the header, click `Select a mode`
* Select **Out of office** from the dropdown
* Add **Starts on** and **Ends on**, then click `save`

*Optionally, select a member to offload duties*
{% 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>Deep work and Cooldown modes</strong></td><td>Catch a break with our 2 modes</td><td><a href="https://github.com/spikehq/gitbook-docs/blob/main/alerts/personal-alerts-management/deep-work-and-cooldown-modes.md">https://github.com/spikehq/gitbook-docs/blob/main/alerts/personal-alerts-management/deep-work-and-cooldown-modes.md</a></td><td><a href="/files/rVQIhr3z9gdMPnbTePhS">/files/rVQIhr3z9gdMPnbTePhS</a></td></tr></tbody></table>