Agiled Docs

Use this checklist when public booking pages do not show the expected times.

No Times Are Showing

Check these items:

The booking page is active.
At least one active event type is selected on the booking page.
The event type is active.
Availability is turned on for the selected day.
Start and end times leave enough room for the event duration.
The booking window allows the selected date.
Lead time or minimum notice is not blocking the time.

Test the exact public booking link in a private window. Admin sessions can make it easy to miss inactive pages, wrong slugs, or visitor timezone behavior.

Also test a date inside and outside the booking window. This confirms whether the missing slots are caused by availability rules or by the public page itself.

Test The Exact Scenario

When a customer reports missing availability, reproduce the same scenario before changing settings:

Open the exact public link they used.
Select the same event type.
Set the same timezone when possible.
Check the same date range.
Compare direct page behavior with embedded page behavior if the link is on a website.

This separates real availability problems from old links, website embed issues, or timezone confusion.

Times Are Too Close Together

Review the event type duration, buffer before, buffer after, and start time increment. Increase buffers or start time increment when the schedule needs more space between bookings.

Busy Times Are Still Available

Open Scheduling > Calendars and confirm the calendar is active and Check conflicts is turned on. Also confirm the busy event is on a connected calendar that Agiled can read.

If the busy event was just created, wait for provider sync and test again. Also confirm the event is marked busy in the provider calendar, not free or tentative when your provider treats those states differently.

Check the calendar connected to the event type, not just any calendar connected to the workspace. Conflict checks only work when Agiled can read the relevant calendar.

Times Are in the Wrong Timezone

Review the event type timezone and the visitor timezone shown during booking. The visitor may see times converted to their local timezone.

When a customer reports a wrong time, ask for the exact booking link, selected time, their timezone, and confirmation email. Compare those against the event type timezone and the appointment record.

Paid Booking Is Not Working

Confirm the event type is marked paid, the price and currency are correct, and the payment provider is connected.

After fixing a paid booking issue, complete one internal test booking and compare the appointment, payment record, and provider transaction before sending the link back to customers.

After Fixing Availability

After changing availability, buffers, calendars, or payment settings, create a test booking from the public page. Then confirm the appointment, calendar event, confirmation email, and payment record if applicable.

Do not consider the issue resolved until the customer-facing booking path creates the expected internal records.

Keep A Known Test Slot

When troubleshooting a busy booking setup, create one controlled test slot with known availability, no conflicting calendar events, and simple event settings. Use that slot to separate calendar conflicts from buffers, lead time, payment, custom questions, or timezone problems.

Remove the test appointment and test calendar event after verification so they do not block real customers.

Troubleshoot Availability