Overview
An event type is the template that appears on your public booking page — for example "30-min meeting" or "1-hour demo". Each event type defines the duration, the rules for when it can be booked, and what happens when someone books. Availability defines the time ranges in which you accept appointments, and buffers guarantee breathing room between one booking and the next.
The times offered to a customer are always the intersection of three things: your availability, your already-busy times (native and Google), and the configured buffers. That way the public page never offers a slot that conflicts with something already booked.
Prerequisites
- The Calendar module enabled and at least one calendar created or connected.
- A role allowed to configure event types and availability.
- (Optional, for distributing across several agents) the agents who will receive the bookings.
Step by step
- In the Calendar, open the event types area and create a new one.
- Set the name, duration and location (in person, a link, or automatic Google Meet).
- (Optional) Right below location, tick Let the customer choose the location and select two or more options (Google Meet, phone, in person or custom).
- Adjust the time rules: minimum notice, maximum advance, and the buffers before and after.
- Set your availability: the weekly time ranges in which you accept appointments.
- Add exceptions for specific dates (holidays, days off or extra hours).
- (Optional) Add intake questions the customer answers when booking.
- (Optional) Set the assigned agents and how bookings are distributed among them.
- Save and use the generated link on the public booking page.
Settings & options
- Scheduling limits (buffers, notices and horizon): each one can be left empty, in which case
it follows the account default (the hint inside the field shows which number that is), or carry a
number — including
0— which then applies to this type only. Use Use the account default, right under the field, to inherit again. Details in Account scheduling defaults and inheritance. - Minimum cancellation notice: how much warning the customer needs to still cancel — the same window applies to rescheduling.
- Reschedule limit: how many times one booking may be moved. Empty = no limit.
- Auto no-show after: minutes past the start at which an unattended appointment is marked as a no-show. Empty = never automatically.
- Duration: how long each appointment of this type lasts.
- What one booking takes off the calendar: only the chosen time (default) or the whole shift — for businesses that sell a shift rather than a slot. See Shift occupancy.
- Buffers: an automatic gap before and after each booking.
- Minimum notice: how much lead time is required before the slot.
- Maximum advance: how many days into the future a slot can be booked.
- Location / Google Meet: in person, a manual link, or automatic Meet link generation.
- Let the customer choose the location: sits right below the Location field in the event type editor. Tick two or more options (Google Meet, phone, in person or custom) so the public page shows the picker to whoever is booking. With none or only one option ticked nothing changes: the fixed Location set above applies. When the customer picks Google Meet, the video-call link is generated automatically — that requires an active Google connection.
- Distribution across agents, when there is more than one host:
- Round-robin: each booking goes to the host who has been free the longest. This is the default.
- Collective: every selected host attends the same appointment and gets the invite.
- Fixed: always the first host on the list. Use it when the event type belongs to one person.
- Intake questions: custom fields answered at booking time.
- Per-type side-effects: turn on or off, per event type, the creation of a conversation, a task, a CRM-deal link, and the sending of the confirmation.
Use cases
- Offer "30-min meeting" and "1-hour demo" with different rules.
- Block last-minute bookings with a minimum notice (for example, 2 hours).
- Guarantee 10 minutes of breathing room between meetings using buffers.
- Open extra hours on a specific date without touching weekly availability.
Tips, limits & best practices
- Use minimum notice so you aren't caught off guard by instant bookings.
- Use buffers for travel, notes or a break between sessions.
- Keep availability lean and use exceptions for one-off cases.
- When you let the customer choose the location, only tick the options you can genuinely honour — all of them show up on the public page. If you offer Google Meet, keep the Google connection active so the link gets generated.
- Always check the time zone — it directly affects the slots offered to the customer.
- For agent distribution, make sure each host has their own availability and calendar so round-robin works well.
Troubleshooting
- No free slots appear: check availability, the notice rules, and whether many times are already busy — buffers also reduce the options.
- Slots I didn't want appear: review the availability ranges and the date exceptions.
- The Meet link wasn't generated: confirm the event type has automatic Google Meet and that there's an active Google connection.
- The customer can't choose the location: the picker only appears with two or more options ticked under Let the customer choose the location — with none or one, the fixed location applies.
- Times are off: check the calendar's time zone — an event type has no time-zone field of its own; it uses the one on the calendar it belongs to.