# Scheduler overview

> Booking pages the AI offers in chat and on calls: define the event, share the link or pin it in the widget, and let reminders kill the no-shows.

The scheduler turns "call us to book" into a link — and into something the AI can *do*. Define an event (a consult, an estimate visit, a table), and it becomes a public booking page the AI offers in chat, texts after a call, or pins in the widget as a two-step booking card.

## Setting up an event

1. **Create the event** — Scheduler → **New event**: name, duration, availability windows, and the details to collect.
2. **Share it** — Every event has a public page at its own link — put it in texts, DMs, and email signatures.
3. **Pin it in chat** — The website widget can carry the event as a pinned booking card: pick a time, leave your details, done — without leaving the thread.

## How the AI uses it

- **In chat** — the booking [tool](/docs/ai/tools) offers real slots and books one mid-conversation.
- **On calls** — the receptionist books during the call and the confirmation text carries the details.
- **In workflows** — "missed call → SMS with the booking link" is two steps in the [editor](/docs/workflows/recipes).

## What a booking creates

A booking is a lead: it lands as a [contact](/docs/crm/contacts) and a card on the board with [attribution](/docs/crm/attribution), so the *card moved to Booked* trigger can start the [reminder cadence](/docs/workflows/recipes) — the one that cuts no-shows 30–50%.

> **ONE EVENT PER INTENT:** "New patient visit" and "cleaning" want different durations and questions. Separate events keep the AI's offer precise and the calendar readable.