ConversaLabs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Event types, availability and buffers

Open in
View as Markdown Open in ChatGPT Open in Claude
Conversa Labs

Conversa Labs

Last updated on Jun 27, 2026

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

  1. In the Calendar, open the event types area and create a new one.
  2. Set the name, duration and location (in person, a link, or automatic Google Meet).
  3. Adjust the time rules: minimum notice, maximum advance, and the buffers before and after.
  4. Set your availability: the weekly time ranges in which you accept appointments.
  5. Add exceptions for specific dates (holidays, days off or extra hours).
  6. (Optional) Add intake questions the customer answers when booking.
  7. (Optional) Set the assigned agents and how bookings are distributed among them.
  8. Save and use the generated link on the public booking page.

Settings & options

  • Duration: how long each appointment of this type lasts.
  • 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.
  • Distribution across agents: round-robin or collective when there's more than one host.
  • 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.
  • 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.
  • Times are off: check the time zone on the calendar and on the event type.

See also