> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vorel.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Calendars

> Connect a calendar so the agent can check real availability and write real bookings.

Booking is only as good as the availability behind it. Connecting a calendar is what turns "we will
get back to you" into a confirmed appointment on the call.

## Supported

| Calendar               | Availability | Booking |
| ---------------------- | ------------ | ------- |
| Google Calendar        | Yes          | Yes     |
| Calendly               | Yes          | Yes     |
| Vorel's own scheduling | Yes          | Yes     |

Some [CRMs](/integrations/crm) also carry appointments, and where they do, bookings sync there as
well. See appointment sync on the CRM page.

## Connecting

Connect under **Settings, then Integrations**. Google Calendar and Calendly both connect by
authorising Vorel against your account, so no credentials are typed into Vorel.

Choose which calendar the agent should read and write. Most businesses point it at a single
bookings calendar rather than an individual's personal one.

## Availability

Availability combines four things:

1. **Your working hours**, including holidays, from **Settings, then Hours**
2. **What is already on the calendar**
3. **The rules from your [vertical pack](/verticals/generic)**, such as service duration and buffers
4. **Anything you configure yourself**, like minimum notice or maximum booking horizon

The agent only offers times that survive all four. It cannot offer a slot outside your hours because
a customer pushed for one.

## Duration and buffers

Service duration comes from your catalog, so a 30-minute service and a 90-minute service reserve
different amounts of time. Buffers between appointments are configured once and applied everywhere.

## Multiple resources

Where your business books against people or rooms rather than one shared calendar, availability is
resolved per resource, so the agent can offer the first slot with anyone or hold out for a named
person the customer asked for.

## No calendar connected

The agent still qualifies the customer and captures the request as a lead, and says the appointment
is requested rather than confirmed. Your team completes it.

This is a reasonable way to start. Run it for a week, see what people ask for, then connect a
calendar.

## Timezones

Everything is anchored to your workspace timezone. Day words like "next Tuesday" are resolved
against your timezone and today's date, and the agent confirms the resolved date rather than
repeating the phrase. See [Booking](/agent/booking).

## Reminders and changes

Reminders, reschedules and cancellations all run through the same connection, and each one emits an
event your [triggers](/automation/triggers) and [webhooks](/integrations/webhooks) can act on.
