Event Types and public booking

Event Types are reusable public booking definitions. A booker opens a workspace scoped address such as:

/e/<workspace-slug>/<event-type-slug>

Event Type administration requires the Events capability and Manager or Super Admin authority.

#Create an Event Type

From Scheduling, select Event Types, then New event type. Enter a title, URL slug, duration, and scheduling type.

The slug is derived from the title until you edit it. Slugs must be unique in the workspace. Use a short stable slug because changing it changes the public address you share.

After creation, the live editor opens with the booking preview beside the configuration.

The editor's sections, in the order they appear:

#Setup

Configure the event title, slug, duration, active state, description, hosts, and location. Supported location modes and details can include a meeting link, phone, physical address, or other configured option. Event Types can store multiple location choices where the editor offers them.

Select Save changes before copying the booking link. The booking link control reflects whether the Event Type is active.

#Calendar and video bookings

The Calendar card in Setup sends confirmed bookings and changes to a calendar connected by the event's host. Under Send bookings to a calendar, choose a calendar that is ready for bookings, shown by its account, with Outlook calendars marked (Outlook). Choose Do not send to a calendar to send none. If the host has no calendar ready, the card says so and offers Connect your scheduling, which opens Scheduling where the calendar can be connected. See Scheduling calendar and manual events.

A location of the video kind needs a connected calendar, because the calendar creates the meeting link:

• With a calendar chosen, each booking gets a Google Meet link from a Google calendar, or a Microsoft Teams link from an Outlook calendar. Setup names the account.
• With no calendar connected, Setup explains that a video booking needs a connected calendar to create its Google Meet or Microsoft Teams link. Connect your scheduling, or paste your own meeting link in Details on the location.
• With a calendar connected but none chosen, it asks you to choose a calendar under Calendar.

If you paste your own meeting link in Details, the booking uses it and no calendar is needed.

#Agaro branding

On Scale and above, Setup has an Agaro branding card under Calendar, with the switch Show Agaro branding. Turn it off to show only your own brand on the booking page; turn it on to show Agaro's. Until you change it, the page follows your plan (see Plans). Plans below Scale do not show the card and keep "Powered by Agaro".

#Availability

Use Availability to set enabled weekdays, start and end times, and timezone. Working Hours is the default schedule in the current editor.

Enable Optimized slots to group offered times into denser windows. Turn on Check for conflicts for a connected Google or Outlook calendar, in Scheduling under Calendars, so busy provider events remove matching availability.

Availability also respects the configured duration, slot interval, buffers, notice, future window, and supported booking limits.

#Questions

Questions controls what the booker is asked. Questions can be required or optional according to their saved definition. Configure the confirmation channel and whether a successful booking should create a CRM contact, including the supported contact kind.

Ask only for information needed to schedule and deliver the meeting. Do not collect passwords, full payment card data, or sensitive regulated data through ordinary booking questions.

#Confirmation and notifications

Use Policies for confirming, rescheduling and cancelling, and AI and automation for reminders and whether a booking creates a CRM contact. Public booking actions send supported notification email after the booking transaction succeeds.

Confirmation behavior can be automatic or require operator confirmation depending on Privacy and Security settings. A pending paid booking is not confirmed merely because the form was submitted.

#Appearance

Use Booking page to choose how the booking page looks. Pick a design: Standard (the default, a wide card), Horizontal, Focused, Minimal or Compact. The live preview beside the settings shows the real page as you change it. Changing any of the colors (page, card, text, muted text, border, accent), the corner radius, spacing, font or shadow turns the design into Custom, your own design that starts from the one you picked. Keep contrast readable; the editor warns when text is too faint.

#Embed your booking page

Select Embed in the editor's top bar or in Booking page (the event must be visible and saved). Choose how it appears on your site:

• Inline embed: the booking page inside your page. It grows to fit, so nobody scrolls inside a box.
• Floating pop-up button: a button in the corner that opens the booking page in a pop-up.
• Email embed: a few of your open times to paste into an email; each opens the booking page with that time chosen.

Under Customize, set the Theme (Light by default, Dark, or Match the visitor's system), the Layout (Month, Week or Column), the width, and for a button its text, colors and size, or show it as a link. The Preview shows the exact page your site will show, on Desktop or Mobile, and the embedded page uses the same theme and layout. Copy code gives the HTML to paste where it should appear.

To take booking requests without a time, replace the booking page with your own HTML and CSS, or let another website send bookings with a booking key, see Booking requests, custom booking pages and the booking key.

#The logo and the host on the public page

The top of a public booking page or event page shows a logo slot that depends on your plan.

If your plan cannot be read, the page shows the Agaro logo. A company image that fails to load is skipped, so a broken address never leaves an empty frame.

The page also shows the host, the organiser of the event, with their name and a photo. The photo is the one chosen for the Event Type, as described next. When none is chosen, it comes from the host's employee card when one exists in this workspace, and otherwise from their Users and Roles picture. With neither, or if the picture fails to load, the page shows the host's initials, or a user icon when there is no name. It never shows the Agaro logo in place of the host. Only the name and the one photo are public. Photo addresses must be secure (https) or a path on the site.

The host's photo is a rounded square, the same shape as the avatars across the platform, never a circle.

#Choose the host's picture

Setup has a Host group, described as the picture beside the host's name on the booking page, its embed, and the confirmation. The Host picture control has two choices:

• Use my profile picture, or Use the host's profile picture when you edit an Event Type that belongs to someone else. This is the default. The booking page shows the host's employee photo, or their Users and Roles picture, or their initials.
• Upload or choose an image opens Choose the host's picture. Pick an image from your Image Bank, or upload a new one. A Super Admin or Manager can upload, and everyone else can pick an existing image and sees Choose an image. Once an image is chosen the button reads Change image, and the page shows that image beside the host's name.

A small preview of the rounded square shows what the page will use. The same control is in the dialog that creates an Event Type.

An image must come from this workspace's Image Bank. If it cannot be shown on a public page, the editor says This image cannot be shown on a public booking page. Choose another one. Only the image's identity is saved. If the image is deleted or made private later, the page stops showing it and the default picture returns.

#How the page opens

A booking page opens on the calendar with the event's name, as a narrow card. When the visitor chooses a day, the card widens to show the host, the details and that day's times, and focus moves to the times. It stays open when they choose another day or go back from a held time. It opens wide at once when a time is already chosen (an emailed time) or when there is no time to choose, so the reason is seen. The card fades in once per page load; for a visitor who asked for reduced motion nothing moves.

#No Support button on public pages

A booking page belongs to your visitors, so it never shows Agaro's Support chat or its button, even when you are signed in and previewing your own page. The same holds for its manage, return, and embedded pages. See Get help with the Support button.

#When times cannot load

A booking page never guesses. If it cannot check the host's calendar, it offers no time, so nobody can book over a calendar nobody read. The booker sees one sentence, with Retry available times.

The page and its Retry available times button always say the same thing for the same cause.

The host is told in Agaro, not the booker. The host gets one notification named Your booking pages could not show times, which names the calendar and what fixes it, and which opens Scheduling where calendars are reconnected. It repeats at most once a day for the same host, cause, and calendars, so ten Event Types make one entry. The Event Type's Setup shows the same notice at the top while it is unread, with Open Scheduling. The causes are a calendar that needs reconnecting, a calendar whose access changed, a calendar the provider could not read, more than 20 calendars blocking times, or a schedule with too many items in the coming weeks.

#Paid bookings

Use Payments and Seats to enable a price, choose the currency, and configure the per slot seat count. Paid booking requires the tenant's Stripe customer payment account under Settings → Payments.

For a paid booking:

1. agaro creates a temporary pending hold for the slot.
2. The booker is redirected to hosted Stripe Checkout.
3. Signed payment evidence settles the booking.
4. Automatic or manual confirmation policy is then applied.
5. An abandoned or failed payment releases or expires the hold through the supported lifecycle.

Do not treat the initial booking form success as payment proof. The provider settlement is authoritative.

#Seats

Enable Offer seats to allow more than one attendee in the same slot. Set a value from 2 to the supported maximum, choose whether to show available seat count, and decide whether attendee information may be shared.

When seats are enabled, individual guest invites are disabled for that Event Type. Review privacy before enabling attendee sharing.

#Recurring bookings

Use Recurring to enable the saved recurring behavior supported by the public booking flow. Confirm each occurrence, total count, and availability before accepting a recurring booking.

#Limits and buffers

Configure:

• Buffer before and after
• Minimum notice
• Slot interval
• Booking frequency limit
• Total duration limit
• Future booking window
• Active bookings per booker
• First slot only behavior

Limits are enforced when public availability is calculated. A narrow future window or large buffer can correctly produce no available slots.

#Reschedule and cancellation

Choose whether bookers may reschedule or cancel, the minimum notice for each, and whether a cancellation reason is optional or required. Public manage links are token protected and apply the saved policy.

#Privacy and security

Controls include:

• Require operator confirmation
• Require email verification
• Mark the Event Type private
• Hide it from public lists
• Disable guests
• Hide notes from attendees

Private links use a random token. agaro stores only a hash and reveals the plaintext link once. Revoke a link that was shared incorrectly and create a new one.

#Webhooks

Use Webhooks to register supported booking lifecycle notifications. Webhook secrets are protected and outbound deliveries are tied to configured event triggers.

Send webhooks only to endpoints you control. Verify their signatures or shared secret according to the receiving integration, handle retries idempotently, and return a success response quickly.

#Troubleshooting

#The booking page says a calendar could not be checked

The host's calendar needs attention. The host should open Scheduling, reconnect or verify the calendar named in their notification, and then reload the page. See Scheduling calendar and manual events.

#The booking page says there were too many requests

Wait a minute and select Retry available times.

#The booking page has no available times

Check weekday hours, timezone, duration, buffers, minimum notice, future booking window, booking limits, seats, and calendar conflicts from a connected Google or Outlook calendar.

#Paid booking is enabled but checkout fails

Confirm the event has a positive price, valid currency, available slot, and ready tenant Stripe connection. The platform subscription Stripe account is not used.

#A private link cannot be copied again

The token is intentionally shown once. Revoke the old link and create a new one.

#Changes are not visible publicly

Save the specific tab and the main Event Type record, confirm the Event Type is active, then reload the public address.