Back to app
Event types

Event types

Define reusable meeting templates for booking links, including duration, buffers, location, and default behavior.

Reviewed OperatorVertiqa 1.54+

An event type is a reusable template for meetings booked through a booking link. It controls the duration, buffers, location type, video provider, and default settings that Vertiqa applies when someone books time with you.

Event types are personal to you. This page lists your own templates, and each teammate keeps their own — your first event type automatically becomes your default, so new booking links have a template to start from. Team owners and admins can manage a teammate's event types when needed, but the default view for everyone is "my event types."

What you can do here

  • Create event types for different meeting formats, such as discovery calls, renewal reviews, implementation check-ins, or support follow-ups.
  • Set one event type as default so new booking links can start with a sensible meeting template.
  • Edit duration and buffers without changing existing meetings already on the calendar.
  • Choose a location type such as call, video, or in-person, and add location details when needed.
  • Deactivate old event types when you no longer want them offered for new booking links.

Every booking link points at one event type. When a client opens the link, Vertiqa uses that event type to decide which slots to show and how long the meeting should be.

If you already have a default event type, the booking-link form preselects it. You can choose a different event type before creating the link.

Deleting event types

You can delete an event type only when no booking links reference it. This protects active and historical booking links from losing the meeting template they need to render public booking slots.

If an event type is still attached to a booking link, either update the link to use another event type or delete the booking link first.

Tips

  • Keep event type names specific enough that operators know which one to choose, for example "30m discovery call" or "60m implementation review".
  • Use buffers on event types instead of asking operators to remember prep or wrap-up time manually.
  • Prefer deactivating an event type when you want to stop using it but still need to preserve the context for existing booking links.
Was this helpful?