> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md).

# How open times are calculated

How dCal decides which times a booking page offers: your hours, minus busy times in your calendars, minus your bookings and pending requests, shaped by the event's length, slot interval, buffers, mini

When a guest opens your booking page, dCal works out which start times to offer. This page explains that calculation, so you can predict what your guests will see and fix it when a time you expected is missing.

***

## The short version

An open time is a time that is inside your hours and not busy, with room for the meeting and its buffers.

1. **Start with your hours.** The event follows your working hours, a saved schedule with its date overrides, or its own custom weekly hours. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md).
2. **Take out what is busy.** Busy times in your connected calendars that have **Check for conflicts** on, your bookings in dCal, requests waiting for your confirmation, and times other guests are holding right now.
3. **Fit the meeting.** Offer each start time where the whole meeting fits inside one range of your hours, and where the meeting plus its buffers does not touch anything busy.
4. **Apply the limits.** Nothing sooner than the event's minimum notice, and nothing later than its booking window or, on the booking page, 60 days from today.

***

## What counts as busy

| Busy, blocks a time                                                                     | Not busy, does not block                                          |
| --------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Events in a connected calendar with **Check for conflicts** on                          | Events in a connected calendar with **Check for conflicts** off   |
| Your confirmed bookings in dCal, including team bookings where you are one of the hosts | Cancelled and declined bookings                                   |
| Requests waiting for your confirmation                                                  | All-day events in Outlook (see [All-day events](#all-day-events)) |
| A time another guest is holding while they fill in the form                             | Events in Google Calendar shown as free                           |

A request that waits for your confirmation already blocks its time, so nobody else books it while you decide. See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md).

> **💡 Tip:** If a personal event uses its own **Calendars for this event**, only those calendars count as busy for that event, whatever the **Calendars** page says. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md#use-different-calendars-for-one-event).

***

## The event settings that shape the times

Each event has a few settings that decide how its times are cut out of your hours. Open the event in **Events** and select **General**. **Duration** is in **Basics**, **Minimum notice** is in **Availability**, and buffers, seats, slot interval and booking window are under **Advanced settings**. See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).

| Setting                   | What it does                                                                                                                                                               |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Duration**              | How long the meeting is. A time is offered only if the whole meeting fits inside one range of your hours, so the last time of a range is the last one that ends inside it. |
| **Slot interval (min)**   | How far apart the start times are. Counting starts at the beginning of each range: a range that starts at 09:15 with a 30-minute interval offers 09:15, 09:45, 10:15.      |
| **Minimum notice**        | How soon a guest can book. Nothing earlier than now plus this many minutes is offered. New events start at 120 minutes (two hours).                                        |
| **Buffer before (min)**   | Free time needed right before the meeting. A time is offered only if this stretch is free too.                                                                             |
| **Buffer after (min)**    | Free time needed right after the meeting, for example to write notes or travel. A time is offered only if this stretch is free too.                                        |
| **Booking window (days)** | How far ahead a guest can book. Empty means no limit. See [How far ahead guests can book](#how-far-ahead-guests-can-book).                                                 |

Changing **Duration** also changes **Slot interval (min)** while the interval still matches the old duration. If you set another interval yourself, changing the duration keeps that interval.

Buffers belong to the event being booked. dCal checks that the buffer around the new meeting is free; it does not add buffers around your other meetings. A buffer only has to be free of busy time, so it can run past the end of your hours.

### An example

Your schedule offers Monday 09:00 to 12:00. The event is 30 minutes long, with a 30-minute slot interval and a 15-minute **Buffer after**. Your connected calendar has a meeting from 10:00 to 10:30.

| Start time | Offered? | Why                                                                         |
| ---------- | -------- | --------------------------------------------------------------------------- |
| 09:00      | Yes      | The meeting and its buffer end at 09:45, before your 10:00 meeting.         |
| 09:30      | No       | The buffer after it, 10:00 to 10:15, runs into your 10:00 meeting.          |
| 10:00      | No       | Your calendar is busy.                                                      |
| 10:30      | Yes      | Your meeting ends at 10:30. Back to back is fine.                           |
| 11:00      | Yes      | Free.                                                                       |
| 11:30      | Yes      | The meeting ends at 12:00, inside your hours. The buffer can run past them. |

If a guest opens the page at 08:00 that Monday and the event has a 120-minute minimum notice, 09:00 disappears too: nothing starts before 10:00, so the first time offered is 10:30.

***

## How far ahead guests can book

Booking pages offer times up to 60 days from today. Each event can offer fewer with its **Booking window (days)**: with 14, the last day a guest can pick is 14 days from today. Today counts as day 0 and the whole last day can be booked. Days are counted in the time zone of the event's schedule (on a team event, each host's own). Days past the window show no times, like days you are not available. An empty field means no limit, which is how every event starts. See [How far ahead guests can book](https://docs.dapta.ai/dcal/events/event-settings.md#how-far-ahead-guests-can-book) in the event settings.

The window also applies to one-off links, the guest's reschedule page, AI agents connected to dCal and the open times the API returns. A window longer than 60 days, up to 730, does not add days to the booking page; it only sets how far ahead AI agents and the API can go, and with the field empty they have no limit. You can still book someone later than the window yourself, from **Bookings** with **Any time (outside availability)**. See [Book for someone](https://docs.dapta.ai/dcal/bookings/book-for-someone.md).

The page loads the month the guest is looking at first, and the next months as they move forward.

***

## Group and team events

* **Group events.** When an event has more than one seat per time, the bookings of that event do not block the time until every seat is taken. Each time shows how many seats are left, and a time with no seats left is no longer offered. See [Group events (seats)](https://docs.dapta.ai/dcal/events/group-events.md).
* **Team events.** Each host's own default schedule and calendars are used. **Round-robin** offers a time when at least one host is free, **Collective** only when every host is free, and **Fixed round-robin** needs every fixed host free plus one of the others. On a round-robin event with **Distribution** set to **Equal distribution**, a host with 3 or more bookings more than the least-booked host offers no times until the others catch up, so a time only that host could take is not offered. See [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md).

***

## The 10-minute hold

When a guest picks a time on a personal, one-to-one event, dCal holds that time for 10 minutes while they fill in the form. Other guests stop seeing it. The form shows **Held until** and the time the hold ends.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-d2e529bf51cf4bb16970b94ec2ef9ea8bbc5b647%2Fdcal-how-open-times-work-01-held-until.png?alt=media" alt="The details form of the Intro call booking page for Wednesday, October 21, 2026, 9:30 to 10:00 AM, with the line Held until 4:11 PM boxed"><figcaption><p>The guest has 10 minutes to finish. Nobody else can take the time meanwhile.</p></figcaption></figure>

* Going back to the times or picking another time releases the hold at once. Closing the page lets it run out after 10 minutes.
* Before placing the hold, dCal checks your calendar again for that exact time.
* There is no hold on team events and group events.
* A host can have up to 10 times held at once. If a hold cannot be placed, the guest can still try to book.
* If the hold runs out before the guest confirms, they see **Your hold expired** and pick a time again.
* An AI agent you connect to dCal can hold a time on a one-host event the same way, for about 10 minutes, and its holds count toward the same limit of 10 per host. See [MCP tools reference](https://docs.dapta.ai/dcal/developers/mcp-tools.md).

When the guest confirms, dCal checks your calendars one last time for that exact time. If the time became busy meanwhile, the guest sees **That time was just taken.** and picks another one.

***

## When your calendar cannot be read

dCal would rather show no times than wrong times.

How dCal reads your calendars:

* **To show times,** a booking page reads your busy times and shares that read with every visitor of the same calendar for 30 seconds. So a time taken somewhere else can still show for up to about 30 seconds.
* **To hold, book, move or confirm a time,** dCal always reads your calendars again, right then. If the time became busy, nothing is booked and the guest picks another time.
* **When a read fails or is slow,** with no answer after 10 seconds, the page uses the last good read of that calendar if it is less than 5 minutes old. Your guest notices nothing.
* **With no good read in the last 5 minutes,** dCal offers no times rather than a partial list that could double-book you.

What your guest sees:

* The calendar on the booking page is replaced by **We can’t read this calendar right now. Try again in a moment.** and a **Try again** button. The page also tries again on its own, five times over about half a minute. If **Try again** still finds nothing: **We still can’t read this calendar. Try again in a minute.**
* When many people are booking at once, the page shows **Lots of people are booking right now. The times will show in a moment.** and the times appear on their own.
* If the time could not be checked at the moment they confirm, they see **We couldn’t confirm this time**, the line "We couldn’t check the host’s calendar just now, so nothing was booked. Try again in a moment." and **Pick another time**. Nothing is booked.

What you see: on **Bookings**, **New booking** shows a notice that starts with **Couldn’t reach the connected calendar**, with a **Check Calendars** link.

What to do:

1. Open **Calendars** and click **Test** on each calendar with **Check for conflicts** on.
2. If a test fails, click **Reconnect**. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md#reconnect).
3. If you no longer use that calendar, untick **Check for conflicts** (on the **Calendars** page, and in **Calendars for this event** of any personal event that lists it) or disconnect it. Times come back the next time the page loads.

For team events, a host whose calendar cannot be read offers no times. If that leaves the team event with no times, its page shows the same message.

***

## All-day events

All-day events behave differently depending on the provider:

* **Google Calendar:** dCal asks Google for your busy times. Whether an all-day event blocks your day depends on whether Google shows it as busy or free. Check the event's busy or free setting in Google Calendar.
* **Outlook / Microsoft 365:** all-day events never block. dCal skips them.

To block a whole day on either provider, add a timed event that covers your hours that day, shown as busy, in a calendar with **Check for conflicts** on. A date override cannot mark a whole day as unavailable. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md#take-a-day-off).

***

## When a booking page shows no times

| Your guest sees                                                            | What it usually means                                                                                                 | What to check                                                                                                            |
| -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **No available times in this range.**                                      | Nothing is free in the days the page offers: up to 60 days ahead, or the event's booking window when it is shorter.   | Your hours, your busy calendars, and the event's minimum notice and **Booking window (days)**.                           |
| **No times are available right now. Please check back soon.**              | The event has no usable schedule: no schedule, a missing schedule, a schedule with no hours, or a team with no hosts. | The event's **General** > **Availability** > **Bookable hours**, then its working hours, saved schedule or custom hours. |
| **We can’t read this calendar right now. Try again in a moment.**          | A calendar with **Check for conflicts** on could not be read, and there is no good read from the last 5 minutes.      | [When your calendar cannot be read](#when-your-calendar-cannot-be-read).                                                 |
| **Lots of people are booking right now. The times will show in a moment.** | dCal is getting many requests at once.                                                                                | Nothing: the times appear on their own.                                                                                  |

***

## Without a connected calendar

With no calendar connected, or none with **Check for conflicts** on, your open times are your hours minus your bookings in dCal and the times being held. dCal cannot see meetings you add elsewhere, so connect a calendar before you share your links. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).

You can still book a guest outside your hours on purpose from the dashboard. See [Book for someone](https://docs.dapta.ai/dcal/bookings/book-for-someone.md).

## Related

* [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md)
* [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md)
* [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md)
* [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md)
* [Troubleshooting](https://docs.dapta.ai/dcal/troubleshooting.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 by asking a question.

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

```
GET https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.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.
