Agiled Docs

Event types define the meeting itself: name, duration, location, availability, payment, reminders, and what should happen after someone books.

Create an Event Type

Open Scheduling > Event Types.
Select Create Event Type.
Enter the name and review the slug.
Add the description and location.
Set the duration, buffers, lead time, booking window, and timezone.
Set initial availability.
Add a questionnaire form if visitors should answer extra questions.
Configure payment, reminders, follow-ups, and automation if needed.
Save the event type.

Start with the simplest version of the event type, then add payment, questions, and automation after the booking flow works. This makes it easier to diagnose missing slots, wrong locations, or calendar writeback issues.

Create separate event types when duration, price, host, location, questions, or availability differ. Reusing one event type for several services makes public booking harder to understand and harder to troubleshoot.

Choose the Right Event Type Structure

Use one event type for one clear meeting offer. If two meetings need different durations, intake questions, prices, or hosts, create separate event types. This keeps public booking pages readable and makes availability easier to debug.

Examples:

15-minute discovery call
60-minute onboarding session
Paid consulting session
Support escalation call

What to Enter

Name
Use the meeting name visitors should recognize, such as “Discovery Call”.

Slug
The slug becomes part of the public booking URL for this event type.

Description
Explain what happens in the meeting and who should book it.

Location
Choose in-person, phone, Google Meet, Zoom, Teams, or custom. Add location details when visitors need a room, phone number, address, or instructions.

Duration
Set the length of the meeting in minutes.

Active
Turn the event type off when it should not be bookable.

Add Questions and Payment Last

First confirm the basic event type can be booked. Then add custom questions, payments, reminders, and follow-up automation. If several settings are added at once, it is harder to know why a visitor cannot finish booking.

For paid event types, test the payment path and confirm the appointment record shows the expected payment state.

Connect The Follow-Up Workflow

Decide what should happen after someone books the event. A sales event may need a deal task, an onboarding event may need a project note, and a paid session may need payment review. Configure reminders, follow-ups, or workflows only after the basic booking and calendar writeback are working.

Add only the intake questions needed for that follow-up. If a question does not change preparation, routing, or delivery, remove it from the booking form.

Open the booking page as a visitor and book one internal test meeting. Confirm availability, timezone, location, custom questions, payment behavior, calendar event creation, reminders, and any follow-up automation.

If the event is for a specific service or campaign, make the description clear enough that visitors know whether they should book it.

Maintain Event Types

Review event types when team members, connected calendars, prices, meeting locations, or service offers change. Disable event types that should no longer be bookable instead of leaving old links active.

Event Type Review

Before sharing:

check the public name and description
confirm the slug is customer-safe
confirm host, location, timezone, and duration
test required questions and payment settings
book one internal appointment
check the appointment, email, calendar event, and follow-up automation

Create Event Types