> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/settings/time-off.md).

# Out of office and vacation mode

Open **Out of office** to block times when you cannot host a meeting.

## Add a block

1. Select **Add a block**.
2. Give it an optional name, such as “Conference.”
3. Set **From** and **To** in the displayed timezone.
4. Select **Add block**.
5. Preview a booking page during that period to confirm it is excluded.

The list shows whether a block was **Added here** or came from a connected calendar. Remove a manual block in Distro; manage a calendar-origin block in its source calendar.

## Turn on vacation mode

Use **Vacation mode → Turn on** to stop new bookings until you return. Select **Turn off** when you are ready to receive bookings again. Existing meetings are not automatically cancelled by this switch.

Out-of-office blocks affect scheduling. Queue exclusion also depends on the queue's routing profile. A profile configured to skip absent members leaves those members out of eligible rotation during the relevant time.

## Coordinate with your admin

If you are an important account owner, decide which fallback should handle incoming leads while you are away. A rulebook ownership match can still resolve a person whose calendar is unavailable unless the journey has a usable fallback.

See [Ownership and fallback](/routing/ownership-and-fallback.md) and [Routing profiles](/routing/profiles.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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/settings/time-off.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 `build a script that syncs our docs to a CMS` 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.