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

# Scheduling event types in Default

> How to create Quick and Team events in Default: booking pages, hosts and queue hosts, availability, booking form questions, meeting messages, reminders, and booking links.

An event in Default is a bookable meeting type with its own public booking page. You configure
it once: its name, duration, hosts, availability, booking questions, and messages.

When someone books, Default creates the meeting and writes it to the host's calendar.

> [!NOTE]
>
> In the sidebar, under **Scheduling**, select **Event Types** to open the events list.

## The events list

All event types share a single list. The table groups events by type and shows a **Favorites**
group at the top.

The table shows each event's name, **Status**, **Duration**, **Last edited**, **Last used**,
**Pre buffer**, **Post buffer**, and **Intervals**.

Select a column header to sort by it.

* The **Status** switch turns an event on or off without opening it. Turning an event off
  shows an **Event deactivated** toast with an **Undo** action.
* Hover over an event's name for a **Booking links** button (see
  [Booking links](#booking-links)).
* If you host the event, your own booking link shows below the event name. Select it to
  copy the link.
* Each row's menu has **Duplicate** and **Delete**. Deleting stops the event's booking
  links, so Default asks you to confirm.
* If workflows use the event, Default lists the workflows that you must update before you
  can delete the event.
* The toolbar has a **Search events** box and filters for **Status** and **Duration**.

## Create an event

**1. Open the dialog**

Select **Create new event**.

**2. Name the event**

Enter an **Event name**. The name is required.

**3. Choose the event type**

Choose the event type for the meeting.

**4. Create the event**

Select **Create new event** again. Default creates the event.

![The Create new event button in Scheduling](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/scheduling/events/create-new-event.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=cc126559b8fcc59569910c25a192e104)

![The New Event dialog with event name and event type options](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/scheduling/events/event-type-selector.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=7e96af0d524ff0d1455f0956003faf19)

2 event types are available today. Webinar events are coming soon:

| Type | What it is | Use it for |
| - | - | - |
| **Quick event** | 1 fixed member hosts the meeting. | A personal demo or intro-call link. |
| **Team event** | 1 or more members or queues can host the meeting. | Round-robin inbound meetings or workflow-routed bookings. |
| **Webinar event** | Coming soon. Not available to create yet. | Many hosts to many attendees, such as group office hours. |

Any member can create a **Quick event**. **Team events** require permission to create shared
events.

If you cannot select **Team event**, ask an admin for Scheduling event access.

After you create the event, Default opens the event editor. Work through its setting sections
from top to bottom.

The live preview on the right updates as you go. The editor header shows **Unsaved changes**
until you select **Save**, then **Published**.

In a narrow window the preview and the sections take turns. The **Editor** and **Preview** switch
under the header picks which one shows, and switching keeps what you typed.

If someone else edits the same event while you have it open, Default asks whether to
**Keep my edits** or **Refresh**.

![The event editor with setting sections on the left and a live booking-page preview on the right](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/scheduling/events/new-event-editor.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=1590d42d18d59d9d0fe9d8059896c0a3)

The event editor: setting sections on the left, a live booking-page preview on the right.

## Event details

Use **Event Details** to control the public booking page basics.

| Setting | What it does |
| - | - |
| **Status** | Turns the event on or off. Turn it off to stop new bookings without deleting the event. |
| **Event title** | Sets the title people see on the booking page. |
| **Description** | Adds rich-text booking-page copy. |
| **Meeting duration** | Sets the meeting length in minutes, from 1 to 480 (8 hours). |
| **Location** | Sets where the meeting happens: calendar default conferencing, Zoom, Zoom personal, in person, or a phone call. |
| **Ignore OOO** | In Person only. Lets people book over your out-of-office time, like at a conference. Other meetings still block. |
| **Auto-accept invite** | Automatically accepts the host's calendar invite after a booking. |
| **Event Identifier** | Sets the booking-page URL slug. Use a short, lowercase, dash-separated slug such as `product-demo`. |

The **Location** setting decides where the meeting happens. Choose your calendar's default
conferencing, Zoom, Zoom Personal, In Person, or Phone call. Phone call books a regular calendar
invite with no video link. Picking In Person reveals **Ignore OOO**, which lets people book over
your out-of-office time while other meetings still block.

![The Location menu in Event Details showing Calendar Default, Zoom, Zoom Personal, and In Person](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/scheduling/events/event-location.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=d41023ed2ab37049317c39fb2fbb88cb)

The Location menu: Calendar Default, Zoom, Zoom Personal, In Person, or Phone call.

> [!NOTE]
>
> Conferencing options depend on connected integrations. Calendar Default uses the host's calendar
> provider settings, and Zoom options require a connected Zoom integration.

## Hosts and attendees

Use **Hosts and Attendees** to decide who runs the meeting and who else can join.

![The Hosts and Attendees section in the event editor](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/scheduling/events/host-and-attendees-section.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=3b039621f0a079e979d82f7f4ccc7ab5)

**Quick events** use a single member picker. Choose the member who hosts the meeting.

**Team events** use the host selector to add members or queues. Choose which host is primary.

Mark each host as required or optional. Queue hosts let Routing pick a member when someone
books.

See [Queues](https://docs.os.default.com/queues.md) for how queue routing works.

| Setting | What it does |
| - | - |
| **Host assignment** | Sets the member, members, or queues that can host the meeting. |
| **Primary host** | Marks the organizer for the meeting. |
| **Required / optional host** | Controls whether a selected host must be available for a slot to appear. |
| **Allow guests to invite external participants** | When on, the booking page and confirmation show **Invite guests** (up to 10 emails). When off, that field is hidden and guest emails are rejected. |
| **Add additional participants** | Adds fixed email invitees to every booking. Each fixed invitee can be optional or required. |

## Scheduling and availability

Use **Scheduling and Availability** to control when people can book and which hours are
available.

![The Scheduling and Availability section in the event editor](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/scheduling/events/scheduling-and-availability-section.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=7b3ea9b684259899a871766d888648a6)

### Scheduling settings

The **Scheduling Settings** tab controls booking windows, buffers, notice, and slot
increments.

| Setting | What it does |
| - | - |
| **Invitees can schedule...** | Sets the booking window: **Days into the future**, **Date range**, or **Indefinitely**. |
| **Number of days** | Appears for **Days into the future**. Pick a preset or enter a custom positive number. |
| **Start date / End date** | Appears for **Date range**. People can only book inside that range. |
| **Pre-meeting buffer** | Blocks time before each meeting, from 0 to 180 minutes. |
| **Post-meeting buffer** | Blocks time after each meeting, from 0 to 180 minutes. |
| **Notice Period** | Sets minimum lead time before a meeting can be booked. Choose **Use host default** or a preset from 15 minutes to 2 weeks. |
| **Start time increments** | Sets the slot granularity people see: 5, 15, 30, or 60 minutes. |

A buffer belongs to the meeting being booked: a time is offered only when the pre-meeting buffer
before it and the post-meeting buffer after it are clear on every required host's calendar.

### Event availability

By default, the event uses each host's working hours from their availability settings. Turn
on **Set custom hours** to override that schedule for this event. A host is then bookable for
the whole of the custom hours, also outside their own working hours. Their calendar, time off
and the event's scheduling period still apply.

![The Event Availability tab with custom hours enabled](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/scheduling/events/event-availability.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=a22b9f41aa14d2c6d87e0ef49574bfd5)

| Setting | What it does |
| - | - |
| **Set custom hours** | Replaces host working hours with this event's custom schedule. |
| **Timezone** | Sets the timezone for the custom hours. Choose **Each host's own time zone** to give every host the same local hours (10:00 to 17:00 means 10:00 to 17:00 where each host works, from their working hours timezone), or **One time zone for all hosts** and pick the zone. |
| **Also keep host working hours** | Off by default. Turn it on to offer a time only when it is inside both the custom hours and the host's own working hours. Use it for a narrower window inside each host's day, for example Tuesday to Thursday only. |
| Available hours (per day) | A day-by-day grid where you toggle each day on or off and set its time ranges. |

## Booking form questions

Use **Booking Form Questions** to decide what the booker must answer before confirming a
meeting.

Default adds the Email question automatically. Email is always required to process an event
booking.

![The Booking Form Questions section in the event editor](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/scheduling/events/booking-form-questions.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=09e6a3539c857cb74cf0520d03049a74)

Select **Add Question**. Choose a person or company field.

You can search fields or filter by **All**, **Person fields**, and **Company fields**. After
you choose a field, configure the question:

| Setting | What it does |
| - | - |
| **Question title** | Sets the label shown on the booking form. |
| **Question description** | Adds helper text below the question. |
| **Question placeholder** | Adds placeholder text inside the input. |
| **Question options** | Appears for single-select and multi-select fields. Add the choices bookers can pick from. |
| **Required** | Makes the question mandatory before booking. |
| **Require work email** | Appears only for the Email question. When on, rejects free or personal addresses, so bookers must enter a work email. |

Questions can collect email, phone, URL, number, text, textarea, single-select, and
multi-select answers. The answer type depends on the field you choose.

Drag questions to reorder them.

### Phone collection for leads

Use a **Phone Number** question to collect a lead phone number during booking. The number is saved
on the lead's record, and a message can use it as `guest.phone_number`. Default does not text
leads: meeting messages go out by email or Slack, so the booking form shows no text-message
consent.

## Messages

Use **Messages** to set the calendar invite for this event's meetings. The messages Default
sends around a meeting, the booking confirmation, the cancel, reschedule, and no-show notices,
and the reminders, come from the event's [Sequence](#sequence) section instead.

### Calendar invite

Set the **Calendar event title** and **Calendar event description**. Default uses these
values on the calendar event that it creates after booking.

The values can differ from the public booking page title and description. Both fields
support scheduling variables, grouped as **Guest variables**, **Host variables**, and
**Meeting variables**.

#### Where guest variables get their values

Guest variables fill from more than 1 source. Default prefers the data it already holds
over what the guest types at booking, because your CRM and enrichment data are usually more
accurate. The Person record combines CRM data, enrichment data, and earlier form submissions.
Form answers reach these variables through that record.

| Variable | Where the value comes from |
| - | - |
| **Guest email** | The email the meeting is booked with. On a booking page, this is the email the guest enters on the form. When a workflow shows the scheduler, Default uses the contact's email from that workflow run instead. |
| **Guest first name**, **Guest last name**, **Guest full name** | The contact record Default already holds for that email, which combines your CRM data, enrichment data, and earlier form submissions. If Default holds no record, the name the guest typed on the booking form. |
| **Guest company name** | The contact record first, then enrichment that ran during the booking's workflow, then the company record linked to the guest's email domain, then the company captured by an earlier form in that workflow. Only when all of those are empty, the company the guest typed on the booking form. |
| **Guest company domain** | The company domain from the contact record: CRM and enrichment data only. This variable never uses a booking-form answer, so it can stay empty when the company name is filled from the form. |

#### Host and meeting variables

**Host variables** (**Host first name**, **Host last name**, **Host full name**, **Host display
name**, and **Host email**) fill from the profile of the meeting's primary host. **Host full
name** is the host's first and last name. **Host display name** is the display name on the
host's profile, or the full name when the profile has no display name.

**Meeting variables** fill from the event itself. **Meeting title** uses the **Event title**
from Event Details, or the event's name when the title is empty. **Meeting description**
uses the **Description** from Event Details, converted to plain text.

**When a variable is blank** lists every variable the title and description use and lets you
decide, per variable, what the invite shows when that variable has no value at booking time:

* **Use the fallback copy** replaces the whole field that contains the variable. Turn on
  **Fallback title and description** and set the **Fallback title** and **Fallback description**
  the invite should show instead. The title and description are evaluated separately, so a blank
  variable in the description never replaces a title whose variables all resolved.
* **Remove the line** drops the description line that holds the variable, so a label such as
  "Meeting Description:" does not survive on its own. A line is a paragraph, or one Shift+Enter
  line inside a paragraph. The title is one line, so there the variable is left empty instead.
* **Leave it empty** renders the variable as empty text and keeps the rest of the field as written.
* **Use another attribute** tries up to three other variables in order and uses the first one with
  a value. When every attribute is blank, the chain ends by removing the line or leaving the
  variable empty, whichever you pick.

**Preview invite** opens the invite in the side rail with a sample guest and you as the host.
Mark any variable in use as blank to see its rule applied before you save.

When **Fallback title and description** is off, a blank variable with no rule of its own renders
as empty text. Variables set to **Remove the line** or **Use another attribute** keep their rule
either way. A fully empty title falls back to the event's name.

Turn on **Include calendar links in footer** to add reschedule and cancel links below the
calendar description. Invitees can then change the meeting straight from the invite.

## Sequence

The **Sequence** section of the event's **Messages** view shows the messages this event sends around its meetings, to guests
and to hosts: the booking confirmation, the cancel, reschedule, and no-show notices, and the
reminders. An event follows a workspace sequence or keeps its own copy.

* **Choose a sequence** links the event to a published workspace sequence. **Workspace default**
  puts it back on the sequence new events get, and **Remove** takes the event off its sequence.
  An event without a linked sequence also offers **Send no messages**, even when no published
  sequence is available. These choices apply when you save the event. Picking one shows what it will do under the picker and
  marks the event **Unsaved changes**, and the **Save** button at the top applies it together with
  your other changes. **Undo sequence change** takes the pick back before then. Only bookings made
  after the save use the new sequence; meetings already booked keep the messages they were booked
  with. While a pick waits, the section's messages are read-only.
* Customize the sequence to give this event its own copy, then edit the copy's messages here
  without changing the workspace sequence. Restore it to follow the workspace sequence again.
  **Customize** and **Restore** take effect at once, and so does the section's own **Save** for
  message edits, which is separate from the event's **Save**.
* Removing a message or turning off **Send this message** stops that message for new bookings.
  Neither action sends another message in its place. Existing bookings keep their saved messages.
  An event's copy, like any sequence, needs at least one message to save; to send nothing, use **Remove**
  (or **Send no messages** when no sequence is linked).
* **Remove** makes the event send no sequence messages for new bookings until you choose a sequence
  again. If the event has its own copy, confirmation explains that saving discards the copy.
* Admins can select **New sequence** here to create and publish a workspace sequence with a starter
  booking message. The event follows it only after you select the event's **Save**. **Undo sequence
  change** cancels the pending link but leaves the new sequence available in Settings.
* An admin can edit and publish a non-default workspace sequence here when this is the only event
  following it. Changes to a shared sequence or the workspace default belong in Settings; use
  **Customize for this event** to change only this event instead.
* **Settings > Sequences** is the admin-only workspace editor for drafts and publishing. See
  [Sequences](https://docs.os.default.com/scheduling-messages.md) and
  [Reminders and no-shows](https://docs.os.default.com/scheduling/reminders-and-no-shows.md).

A host can mute any of these alerts for themselves in [My Notifications](https://docs.os.default.com/settings/notifications.md).
A muted host is skipped, and nothing else sends in the sequence's place.

## Scheduler settings

Use **Scheduler Settings**, the last section of the editor, to control how the scheduler looks
and behaves wherever the event appears.

| Setting | What it does |
| - | - |
| **Scheduler appearance** | Switches the scheduler between the **Full** and **Compact** layouts in booking links and workflows. Defaults to **Full**. |
| **Calendar Slots** | **Current Month** shows the full calendar month. **Rolling Month** starts on today and pages through a 4-week window with no past dates. Defaults to **Current Month**. |
| **Hide booking countdown** | Hides the countdown timer when a workflow with a timeout shows the event. The workflow timeout still applies. |
| **Hide close button** | Hides the close button when the scheduler is embedded in a form overlay. Direct booking links never show a close button. Programmatic dismiss still works. |

## Booking links

Booking links open in a **Booking links** drawer. Open it from the **Booking links** button
on an event row, or from **Copy Link** in the event editor's header.

### View and copy links

The drawer lists the event's links in 2 tabs:

* **Permanent** links keep working until you delete them.
* **Expiring** links stop working on their expiration date. The list shows when each link
  expires.

The **Permanent** tab starts with 1 shorthand link for each event host. The shorthand
uses the host's **Scheduling username**, or the queue's identifier for a queue host.

Select a link to copy it. If you can manage booking links, each created link also has a
menu with **Edit**, **Revoke**, and **Delete**.

Deleting a link does not affect meetings already booked through it. Default frees the
link's custom slug for reuse.

Long lists load a page at a time. Select **Show more links** to load the next page.

### Revoked links

Revoking a link stops it from accepting bookings. Revoked links are hidden from the lists by
default. If you can manage booking links, select **Show revoked links** under the tabs to list
them with the active ones, and **Hide revoked links** to put them away again. A revoked link
appears under the tab for its kind, **Permanent** or **Expiring**.

A revoked link cannot be copied, edited, or revoked again. You can only delete it.

Revoking a link keeps its custom slug reserved. To use that slug on a new link, delete the
revoked link first: deleting frees the slug. If you try to reuse a slug that a revoked link
still holds, the form tells you to show revoked links and delete it.

### Create a booking link

**1. Open the form**

Select **New** in the drawer header. The drawer shows the **New booking link** form.

**2. Set the expiration**

Choose **Permanent** or **Expiring**. For an expiring link, pick the expiration date.

**3. Choose the hosts**

Add the members or queues that host meetings booked through the link.

**4. Name the link**

Enter a **Link name**. Optionally, set a **Custom slug** for the link URL.

**5. Set the visibility**

Choose **Shared** or **Private**.

**6. Copy the link**

Select **Copy link**. Default creates the link if needed and copies it to your
clipboard. If the event already has a link with the same hosts, slug, name, visibility, and
expiration day, Default copies that link instead of creating another.

Open **Advanced** to add URL parameters and to see the **Link preview**.

A booking link can also fill in the booking form. Add `email`, `first_name`, or `last_name` to the
link, for example `?email=ada@acme.com`, and the matching booking question opens with that answer.
The guest can change it before they book. URL-encode the value, so a `+` in an email is written
as `%2B`. Default removes these three from the address bar once the page loads, so reloading the
page opens a blank form.

## After publishing

When an event is active, its booking page is available at the event slug. Copy the shareable
booking link from the Events list or from the **Booking links** drawer.

Bookings appear under [Meetings](https://docs.os.default.com/meetings.md). There you can review them, mark no-shows, and
cancel them.

You can also use events in [Workflows](https://docs.os.default.com/workflows.md) to show a booking page during an
automated flow.

To style public booking pages, use the [Scheduling editor in Branding](https://docs.os.default.com/settings/scheduler.md). To
style the emails Default sends about meetings, use the
[Emails editor in Branding](https://docs.os.default.com/branding.md#emails-editor).

Related: [Sales scheduling software from Default](https://www.default.com/product/sales-scheduling-software)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.