> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atonom.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Meeting Types
> Create and manage meeting types in Atonom, and understand how they work with calendar booking.
Meeting types are reusable booking templates that define how a schedulable meeting behaves—duration, slot spacing, lead times, reminders, and visibility. Every calendar booking in Atonom references a meeting type, whether the booking comes from a profile page, Cloud Employee, chat, form, or the API.
Before users can book meetings, your organization needs at least one meeting type configured, and each user who will receive bookings needs a connected calendar. See [Calendar Setup](/integrations/calendar-setup) for connecting Google or Microsoft and configuring personal meeting preferences.
## Meeting types vs personal calendar settings
Atonom separates **what kind of meeting** is being booked from **whose calendar** it lands on.
| | Meeting type | Personal calendar settings |
| ----------------- | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Scope** | Organization (tenant) | Individual user |
| **Configured in** | Org Settings → Meetings | My Settings → My Calendar |
| **Examples** | Duration, slot interval, meeting-type lead time, max booking window | Personal meeting link, buffer time, personal lead time, weekly availability, selected calendars |
At booking time, Atonom combines both. For example, availability uses the **longer** of the meeting type's minimum lead time and the user's personal lead time, plus the user's buffer time and weekly hours. See [How lead time is applied](/integrations/calendar-setup#how-lead-time-is-applied) in the calendar setup guide.
```mermaid theme={null}
flowchart TD
MT[MeetingType tenant template] --> Book[Booking flow]
CS[User calendar settings] --> Book
Book --> Cal[Google or Microsoft calendar]
MT --> CE[Cloud Employee]
MT --> PP[Profile page]
MT --> API[Schedule Meeting API]
```
***
## Creating meeting types
1. Go to **Org Settings → Meetings** ([`/#/settings/v2/meeting_types`](https://app.getsignals.ai/#/settings/v2/meeting_types))
2. Click **Add Meeting**
3. Fill in the meeting type fields (see below)
4. Click **Save**
You can edit or delete existing meeting types from the same page. Deleted meeting types are soft-deleted and no longer appear in booking flows.
Org Settings → Meetings requires the Calendar plan component on your tenant.
### Meeting type fields
| Field | Description |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Meeting Name** | Label shown to visitors when choosing a meeting (for example, "Product Demo" or "30-Minute Consultation") |
| **Meeting Duration** | Length of the booked event: 15, 30, 45, or 60 minutes |
| **Time Slot Interval** | How often available start times appear (every 5, 10, 15, 30, or 60 minutes). Defaults to 15 minutes |
| **Reminder Time** | Calendar reminder for the host before the meeting: 15 min, 30 min, 1 hour, 2 hours, 12 hours, or 1 day before |
| **Minimum Lead Time** | Earliest a meeting can start after it is booked. Options from 15 minutes up to 2 days |
| **Maximum Lead Time** | How far in advance slots can be offered, in days (1–21; defaults to 14 days) |
| **Meeting Description** | Details included on calendar invitations |
| **Visibility** | **Available company-wide** — any user in the org can see and use this type. **Private to me** — only visible to the user who created it |
| **Allow use on agent profile pages** | When enabled, users can add this meeting type to their public profile page |
Minimum lead time on the meeting type is compared against each user's **personal lead time** in My Calendar. Atonom always applies whichever value is **longer**.
***
## Where meeting types are used
Once created, meeting types can power bookings across Atonom:
| Surface | How the meeting type is selected |
| --------------------------- | ---------------------------------------------------------------------------------------- |
| **Profile pages** | User adds types to **Agent Page Meetings** on My Profile; visitors pick from those types |
| **Cloud Employees** | Meeting booking capability references a specific meeting type |
| **Comm Agents / workflows** | Calendar book-meeting tool configured with a meeting type |
| **Chat & forms** | Calendar drop or form field tied to a meeting type |
| **Schedule a Meeting API** | `meeting_type_id` in the API request |
Each surface validates that the meeting type exists, is visible to the booking user, and (for profile pages) is enabled for agent pages.
***
## Profile pages and meeting types
Profile page booking is optional and separate from other flows. See [Profile page meeting booking](/integrations/calendar-setup#profile-page-meeting-booking-optional) for the full setup.
When profile booking is enabled, users manage two lists under **My Settings → My Profile → My Meetings**:
### Agent Page Meetings
Meeting types currently shown on the user's public profile page. Anyone with the profile link can schedule one of these types.
* Use **Copy link** next to a meeting type to get a direct URL that opens the profile page with that type pre-selected (`?m_id=`)
* Use **Remove** to take a type off the profile page without deleting the meeting type itself
### Available Meetings
Meeting types the user is allowed to add to their profile. A type appears here when it is:
* **Available company-wide**, or **Private to me** and created by the current user, **and**
* Has **Allow use on agent profile pages** enabled in Org Settings
Click **+** to add a type from Available Meetings to Agent Page Meetings.
A meeting type must have **Allow use on agent profile pages** checked when it is created or edited in Org Settings → Meetings, or users will not be able to add it to their profile.
***
## Scheduling rules at book time
When a visitor or Cloud Employee books a meeting, Atonom applies rules from the meeting type and the host's personal calendar settings:
| Rule | Source |
| ------------------------ | ------------------------------------------------------------------------ |
| Event duration | Meeting type duration |
| Slot spacing | Meeting type time slot interval |
| Minimum notice | **Longer of** meeting type minimum lead time and user personal lead time |
| Booking window | Meeting type maximum lead time (days) |
| Gap after prior meetings | User buffer time (My Calendar → Meeting Settings) |
| Bookable hours | User weekly availability grid (My Calendar → Availability Settings) |
| Conflict checks | User selected calendars |
| Meeting link in invite | User personal meeting link (My Calendar → Meeting Settings) |
| Calendar reminder | Meeting type reminder time |
***
## Cloud Employee meeting booking
To let a Cloud Employee schedule meetings on behalf of users:
1. Create meeting types in **Org Settings → Meetings**
2. Ensure target users have connected calendars and configured availability — see [Calendar Setup](/integrations/calendar-setup)
3. On the Cloud Employee, enable the **Meeting booking** capability and select a meeting type
4. Configure routing so the employee knows which user's calendar to book against
The Cloud Employee uses the selected meeting type's duration, interval, and lead-time rules when offering and confirming slots. It does not require the host to enable profile page booking.
See [Build Your First Cloud Employee](/get-started/quickstart) for capability setup steps.
***
## Troubleshooting
| Issue | What to check |
| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| No meeting types in dropdowns | Create at least one type in Org Settings → Meetings |
| Type not in Available Meetings on profile | Confirm **Allow use on agent profile pages** is enabled; confirm visibility (company-wide or private to creator) |
| No meetings shown on profile page | User must enable profile booking, connect calendar, and add types under Agent Page Meetings |
| Slots start too soon or too late | Compare meeting type minimum lead time with user's personal lead time — the longer value wins |
| No slots far in the future | Check meeting type **Maximum Lead Time** (days) |
| Slots too close together or far apart | Adjust meeting type **Time Slot Interval** |
| Booking succeeds but no meeting link | User must save a personal meeting link in My Calendar → Meeting Settings |
Contact [support@atonom.ai](mailto:support@atonom.ai) if you need assistance.
***
## What's next
Connect Google or Microsoft, and configure personal meeting and availability settings
Google and Microsoft scopes and admin setup
Book meetings programmatically with a meeting type ID
Enable the meeting booking capability on a Cloud Employee