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

# Event Types

> Create the meeting templates people can book on your calendar

## What is an Event Type?

An event type is a template for a bookable meeting — for example, a 15-minute discovery call or a 60-minute strategy session. Each event type has its own duration, location, hosts, availability, and booking link.

Event types live at the workspace level, so you can share the same event type across multiple AI assistants in your workspace.

## Creating an Event Type

<Steps>
  <Step title="Go to Event Types">
    Open **Booking > Event Types** and click **New Event Type**.
  </Step>

  <Step title="Fill in the Basics">
    Name, description, duration, and the URL slug for the public booking link.
  </Step>

  <Step title="Pick a Location">
    Choose how the meeting will happen (Google Meet, Zoom, Teams, phone, or in-person).
  </Step>

  <Step title="Add Hosts">
    Select one or more workspace members who will host this meeting.
  </Step>

  <Step title="Save and Share">
    Your event type gets a public link at `/b/[your-slug]` that you can share anywhere.
  </Step>
</Steps>

## Event Type Fields

<AccordionGroup>
  <Accordion title="Name and Description">
    The name appears at the top of the booking page. The description explains what the meeting is about and shows up under the name. Both are visible to invitees.
  </Accordion>

  <Accordion title="Duration">
    How long the meeting lasts, in minutes. Common choices: 15, 30, 45, 60. The booking page shows time slots in increments of this length.
  </Accordion>

  <Accordion title="Slug">
    The URL-friendly identifier used in the booking link. For example, a slug of `discovery-call` produces a link at `/b/discovery-call`. Pick something short and memorable.
  </Accordion>

  <Accordion title="Location Type">
    Where the meeting happens:

    * **Google Meet** — Clarky generates a Meet link automatically when the host has Google Calendar connected
    * **Zoom** — paste your meeting link or personal Zoom room
    * **Microsoft Teams** — paste your Teams meeting link
    * **Phone** — Clarky shares the invitee's phone number with the host
    * **In-Person** — provide the address or location details
  </Accordion>

  <Accordion title="Color">
    A visual identifier shown on the admin calendar so different event types are easy to scan at a glance.
  </Accordion>

  <Accordion title="Active / Inactive">
    Inactive event types stop accepting new bookings and disappear from public booking pages. Existing bookings are unaffected.
  </Accordion>
</AccordionGroup>

## Scheduling Type

If your event type has more than one host, the **scheduling type** controls how invitees are matched to hosts:

<Tabs>
  <Tab title="One-on-One">
    A single host runs the meeting. The invitee books with that one person.
  </Tab>

  <Tab title="Round Robin">
    Bookings rotate across the host pool. A time slot is offered as long as **at least one** host is free at that time. Great for sales teams or support shifts where any teammate can take the call.
  </Tab>

  <Tab title="Collective">
    Everyone joins the same meeting. A time slot is only offered when **every** host is free. Use this for panel interviews or team intros.
  </Tab>

  <Tab title="Group">
    A single host meets with multiple invitees in the same session. Use this for office hours, group demos, or webinars.
  </Tab>
</Tabs>

<Tip>
  For round-robin, set host **priority** to control the order Clarky tries to assign bookings.
</Tip>

## Booking Rules

Each event type lets you control when and how often it can be booked:

<AccordionGroup>
  <Accordion title="Minimum Notice">
    The shortest amount of time between now and a bookable slot. For example, a 4-hour minimum prevents same-day last-minute bookings.
  </Accordion>

  <Accordion title="Maximum Days Ahead">
    How far into the future invitees can book. A 60-day window is a common default.
  </Accordion>

  <Accordion title="Buffer Times">
    Block extra time before and/or after each meeting to prevent back-to-back calls. For example, a 10-minute buffer after a 30-minute call gives you time to write notes.
  </Accordion>

  <Accordion title="Maximum Bookings Per Day">
    Cap how many of this event type can happen in a single day. Once the limit is reached, the day disappears from the booking page.
  </Accordion>

  <Accordion title="Requires Confirmation">
    When enabled, new bookings start as **pending** and need a workspace admin to approve them before they're confirmed. The invitee gets a confirmation email only after you confirm.
  </Accordion>

  <Accordion title="Allow Reschedule">
    Lets invitees reschedule from the link in their confirmation email. You can also cap the number of times a single booking can be rescheduled.
  </Accordion>
</AccordionGroup>

## Custom Booking Questions

Beyond the standard name, email, and notes fields, you can add custom questions invitees must answer when booking. Use these to qualify leads, gather context, or collect information your team needs before the meeting.

Examples:

* "What's your company size?"
* "What problem are you trying to solve?"
* "Have you used a tool like ours before?"

Responses appear in the booking detail view alongside the meeting.

## Reminders

Set automatic reminder emails and SMS messages before each meeting. Configure how many hours before the meeting to send each reminder — for example, 24 hours and 1 hour before.

<Note>
  Reminders are only sent for **confirmed** bookings, not pending ones.
</Note>

## Confirmation Message and Cancellation Policy

* **Confirmation message** — what the invitee sees on the success screen after booking
* **Cancellation policy** — what the invitee sees if they try to cancel

Use plain language. These are great places to set expectations like "We'll send a Google Meet link by email" or "Please cancel at least 24 hours in advance."

## Choosing Which Event Types Each Bot Offers

Event types are workspace-wide, but you can pick which ones each AI assistant offers. Open the event types list to see a chip for every assistant in your workspace next to each event type. Click a chip to toggle whether that assistant can offer that event type in chat or voice.

<Info>
  By default, every assistant offers every active event type. Per-assistant selection is only needed if you want to scope event types — for example, a sales assistant that only offers discovery calls and a support assistant that only offers triage sessions.
</Info>

## Next Steps

<CardGroup cols={2}>
  <Card title="Set Availability" icon="clock" href="/features/booking/availability">
    Configure working hours and Google Calendar
  </Card>

  <Card title="Booking Flow" icon="check" href="/features/booking/booking-flow">
    Preview what invitees see
  </Card>
</CardGroup>