> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/event-types/create-an-event-type.md).
# Configuration
Create event types for your routers and personal meeting links.
Create an event type, configure its booking experience, and review its existing uses before making shared changes.
## Create and configure an event type
Open **Event types**, click **New Event Type**, name it, and create it. In the editor, work through the sections that matter for this meeting:
**Internal settings** contains private notes and the availability strategy. **Default** follows the selected team or user schedule. **Custom weekly** defines recurring hours for this event type. **Event dates** limits booking to specific dates and hours.
For **Default**, choose **Team** to follow the routed team’s hours or **User** to follow the host’s hours. Personal and group links have no routed team, so they use the participants’ personal schedules when the source is Team.
For **Custom weekly**, set the timezone and recurring hours for this event type. For **Event dates**, set the timezone, location, and at least one date with a start and end time. Time periods on the same date cannot overlap. These schedules replace the usual weekly hours; calendar conflicts and booking rules still apply. Event-date bookings use the location for an in-person meeting.
**Scheduler settings** controls what guests see and when they can book. Set **Guest language**, **Time format**, **Greeting**, and **Description** for the booking page. The **Internal description** stays in the setup area; use the guest-facing description for information the prospect needs.
| Setting | Use it to |
| --------------------- | --------------------------------------------- |
| Duration | Set how long the meeting lasts. |
| Time-slot interval | Set how frequently a meeting can start. |
| Buffer before / after | Leave space around meetings. |
| Minimum notice | Prevent bookings too close to the start time. |
| Booking window | Limit how far ahead guests can book. |
Under **Booking rules**, turn on **Block other Distro meetings** to hide times that overlap a selected participant’s scheduled Distro meetings. This is an additional check alongside connected-calendar conflicts, and it is off by default for a new event type.
Under **Calendar invites**, edit **Calendar title** and **Calendar invite body**. Under **Reminders**, enable email reminders, choose **Reminder timing**, and edit **Reminder email subject** and **Reminder email body**. Use the variables offered by the editor for guest, host, meeting time, and meeting links.
Review the desktop and mobile previews, then click **Save**. The preview illustrates the booking page; use a real booking link to check live availability.
## Before changing a shared event type
Check which links and routers use it. A shared change can affect more than one booking experience. Router settings are versioned: activate a new router version when you want updated configuration used for new routing attempts. See [Publish changes to a router](/routing/router-versions.md).
New bookings keep the event settings used when they were created. Changing a link’s event type later does not rewrite those bookings’ saved settings. Older links may still have their own private event settings, which you edit from the link.
You must reassign or delete active personal and group links before deleting the reusable event type they use.
Use **Duplicate** when you need an independent event type with similar settings. Review the copied schedule, dates, location, invitation, and reminders before assigning it to links.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.distro.so/event-types/create-an-event-type.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
