View and manage every booking against your scheduling pages from one place.
A live list of bookings — Upcoming, Past, Cancelled, and Rescheduled — with cancel and reschedule actions inline.
The Bookings page (under Toolsin the main sidebar) shows every booking that touches your scheduling pages. Sales reps see their own bookings, sales managers see their team's, and admins see the whole organization. Each row shows the scheduling page, booker name and email, date and time in the scheduling page's timezone, location type, and duration. Click a row to expand the detail drawer with the full booking record and action buttons.
The four tabs across the top filter the list by booking lifecycle state.
| Field | Description |
|---|---|
| Upcoming | Confirmed bookings whose start time is in the future. This is the default tab and the one you'll spend most of your time in. |
| Past | Confirmed bookings whose start time is in the past. Use this tab to mark attendance — Mark attended or Mark no-show. |
| Cancelled | Bookings the booker or host cancelled. The cancellation reason and who cancelled (booker or host) are shown in the detail drawer. |
| Rescheduled | Old occurrences of bookings that have been rescheduled. The new occurrence appears in the Upcoming tab — both rows share the same booking series so you can audit the history. |
Quick scan from the list view, no click required.
Click any row to expand it inline.
The drawer expands inline below the row and shows everything the booker submitted plus context the CRM has on file:
http:// or https://; anything else (a phone number, an address, or a defensively-blocked stale value) is shown as plain text.What you can do from the drawer.
confirm() popups, so screen readers announce them correctly and the textarea preserves whatever you typed if you accidentally collapse the drawer.A notification that fires automatically before each booking.
When Pre-meeting briefingis enabled on the scheduling page (it is by default), a notification is sent to the host roughly 1 hour before each confirmed booking. The briefing includes recent activity with the linked person, their lifecycle stage, and any open opportunities tied to them — so you walk into the call with context, not a cold introduction.
Briefings are dispatched by a background cron that runs every 5 minutes. A booking that starts in less than 60 minutes when it's created (so the cron can't catch it before the meeting starts) doesn't get a briefing — the cron only fires for bookings whose briefing window hasn't already passed. The booking row records briefing_sent_atonce the notification ships so it's never duplicated.
How the booking was assigned to a host.
| Field | Description |
|---|---|
| Individual | Default. The scheduling page belongs to one host; every booking is assigned to that host. |
| Round robin | Multiple eligible hosts; the system picks the host with no conflicting confirmed booking + the least-recent rotation cursor and bumps the cursor atomically. Tiebreaker: weight DESC, user_id ASC. |
| Collective | All eligible hosts must be free; availability = the intersection of their schedules. The booking's primary host is the lowest user_id (deterministic anchor); the rest are calendar attendees on the provisioned event. |
| Group | Single host, but the scheduling page sets a group capacity > 1 so multiple bookers share a single slot. Each booker is a separate booking_attendees row; the row's attendee_count increments per registration. The drawer shows N attendees so you know how many people are joining. |
own / team / all) decides which bookings show up.Check that you're on the right tab (Upcoming hides past bookings, Past hides future ones). If you have own data scope on scheduler.view, you only see bookings where you're the assigned host — round-robin or collective bookings assigned to a teammate won't appear.
You don't have scheduler.edit, the booking is in the past, or the booking is already cancelled or rescheduled. Past meetings can't be rescheduled from this view — create a new booking instead.
Another booking landed on the slot you picked between the time you opened the dialog and the time you clicked Confirm. Pick a different time. The database guarantees no double-booking can slip through, even under high concurrency.
Ask them to check their spam folder. Email delivery audit columns are stored on every booking; the cancellation/reschedule pipeline retries on transient failures and logs terminal ones. For Google Meet bookings, Google also sends its own native invite-update from a Google address — that's delivered independently.