NearSync Help

Operations

Booking: Event Types How to define what people can book, how long it takes, where it happens, and who it goes to.

Operations, Setup, Booking Engine. Five sections down the left: Event Types, Availability, Teams, Routing and Insights. This article covers Event Types - the definition of what someone can actually book.

Creating An Event Type

  1. Title and slug. The title is what the booker sees; the slug is the link. Keep the slug short and stable - it goes in emails and on your site.
  2. Duration. Thirty minutes by default. Be honest rather than optimistic: a "30 minute" call that always runs 45 wrecks the rest of the day for whoever takes it.
  3. Description. What the booker should expect. This is also where you set expectations about preparation.
  4. Location. Google Meet, a Zoom link, or a physical address.
  5. Buffer time. Minutes held after the meeting, so back-to-back bookings do not leave someone with no gap.
  6. Maximum bookings per day. A cap so a single busy day cannot be filled entirely.
  7. Assignment logic. How the platform picks who takes it - round robin distributes fairly across the team.
  8. Auto-confirm. Whether bookings confirm automatically or wait for acceptance.
  9. Require phone. Whether the booker must give a number.
  10. Department. Which team this belongs to.
  11. Internal. Mark it internal if it is for staff rather than customers.

The Settings That Matter Most

Buffer time is the most under-used. Without it, a full day of back-to-back calls has no room to write notes, and the notes never get written.

Maximum bookings per day protects the calendar from a good marketing day. Without a cap, one campaign can consume a week of someone's time.

Auto-confirm is a trade. On, and booking is frictionless but you accept whatever lands. Off, and you control the calendar but add a step and a delay. Auto-confirm suits high-volume, low-stakes bookings; leave it off for anything expensive.

Tip

Create fewer event types than you think you need. Every type is a decision the booker has to make, and a page with seven options gets fewer bookings than one with two. Start with one or two and split only when the difference genuinely changes duration or who takes it.

Topics

An event type can carry topics - the reasons someone is booking - each with a label and an icon. The starting set covers Platform Demo, Pricing and Scope, Tech Audit and Partnership, and you can define your own.

Topics do two jobs: they tell whoever takes the call what it is about before they join, and they feed routing. A booker choosing "Pricing and Scope" can be sent somewhere different from one choosing "Tech Audit". See Booking: Availability, Teams and Routing.

Location

Google Meet generates a link automatically. Zoom uses a link you supply. Physical address is for in-person, and the address is shown to the booker.

For in-person bookings, set buffer time generously. Travel is not free and the calendar does not know that.

Internal Event Types

Marking a type internal keeps it off customer-facing pages. Useful for interview slots, internal reviews and office hours - things that need booking but not publishing.

  1. Book it yourself from a private browser window.
  2. Check the confirmation arrives and reads correctly.
  3. Check it lands on the right person's calendar.
  4. Check the meeting link works.
  5. Check the buffer actually holds the following slot.

Five minutes, and it catches nearly everything.

Common Questions

Can one event type route to different people? Yes, that is what assignment logic and routing are for. See Booking: Availability, Teams and Routing.

Can I take payment? Payment sits with the booking add-on. Check what your plan includes.

Can I change duration later? Yes, and it applies to new bookings. Existing bookings keep their original duration.

Does a booking record anything? If the meeting is recorded, it is analysed against its meeting type. That is configured separately - see Meeting Types and Frameworks.

9 minUpdated 28 July 2026

Did this answer your question?

No, ask a person