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

# Calendars and availability

Distro offers a time only when the event and required hosts allow it.

Connect calendars and review working hours before activating a queue or sharing a scheduling journey.

## Set up each host

1. Connect a calendar and choose the primary calendar for bookings.
2. Set the correct timezone and working hours.
3. Review notice periods, meeting buffers, and out-of-office time.
4. Connect the conferencing account used by the event.
5. Confirm the host is active in the relevant queue.

A queue member without a connected primary calendar may still receive record assignments, but is skipped for meeting hosting.

## Understand the times offered

For **Pre-picked member**, routing selects the host first and the scheduler shows that member's times.

For **Any available member**, the scheduler offers times where a qualifying pool member is free, then selects the host for the booked slot.

Required co-hosts must also be free. Optional co-hosts and fixed invitees do not limit the times offered.

A fallback host handles an unusable primary source according to the configuration; it is not permission to ignore that fallback person's working hours.

## Troubleshoot no times

Check these in order:

1. The effective event type and host source.
2. Active queue and member status.
3. Connected primary calendars.
4. Timezone, working hours, out-of-office blocks, and busy events.
5. Notice period, buffers, and event booking range.
6. Required co-hosts.
7. Profile settings that exclude members.

Use the workspace's availability preview or troubleshooting controls where available.

## Verify with a real booking

Simulation does not query live calendars. Use controlled guest details to verify a real offered slot, calendar event, and conferencing link.

A provider delivery problem should be investigated in the booking or workflow details. Changing rotation rules does not repair a disconnected calendar.


---

# 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/scheduling/availability.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.