Scheduling basics

The mental model:

• Event Type — a definition of "a bookable thing" (30-minute intro call, 45-minute demo). Lives at /:user/:slug or /team/:teamSlug/:slug.
• Schedule — a named set of availability rules ("Working Hours", "Evenings"). Weekly intervals plus date-specific overrides. Each user has a default schedule; event types can pick any.
• Booking — the materialized appointment. Has attendees, references to external systems (Google Calendar event, Zoom meeting), and a stable iCalUID across reschedules.
• Host — a user assigned to an event type. Hosts have weights and priorities for round-robin.
• Team — a group of users who can co-host event types.
• Location — where the meeting happens. Video (built-in, Zoom, Meet, Teams), phone, in-person, or custom link.

Workflows and routing forms

• Workflow — trigger + ordered steps. "Email attendee 1h before event."
• Routing Form — pre-booking form with rules that route to the right event type based on answers. Like ChiliPiper.

Public URLs

• /:user — user profile with event type list
• /:user/:slug — Booker for a personal event type
• /:user/:slug/embed — chromeless for iframe embedding
• /team/:teamSlug — team profile
• /team/:teamSlug/:slug — Booker for team event type (round-robin or collective)
• /d/:hash/:slug — private hashed-link Booker
• /booking/:uid — booking detail / manage
• /reschedule/:uid — reschedule Booker
• /forms/:formId — public routing form

Common tasks