Public Booking Flow
Understand what customers see when booking an appointment.
Public booking pages let customers choose an event type, select an available time, and submit their booking details.
Customer Flow
- Open the public booking link.
- Choose an event type.
- Select an available time.
- Enter required details.
- Confirm the booking.
- View the confirmation page.
Agiled creates the appointment after the booking is submitted.
Choose a View and Time Format
Depending on the event type settings, visitors can view availability by month, week, or column layout. They can also switch between 12-hour and 24-hour time format.
Use these controls when testing a booking page because a slot may be easier to see in one layout than another.
Select a Time Slot
The time slot list shows available times for the selected date. If no slots are available, the page shows a no-slots message. The booking form opens only after the visitor selects a slot.
If customers report that they cannot find a time, test the same event type in a private browser and switch layouts. Then check host availability, connected calendar busy events, booking buffers, minimum notice, maximum booking window, and timezone.
Complete Booking Details
The booking form collects:
- name
- notes
- phone, when the event asks for it
- timezone, when shown
- location option, when multiple locations are available
- recurring booking settings, when enabled
- custom question answers
Custom question types can include short text, long text, email, phone, select, and checkbox fields.
Only ask questions the team will actually use before the meeting. Too many required fields can reduce booking completion, while too few fields can leave the host without the context needed to prepare.
Recurring Bookings
If the event type supports recurring bookings, the visitor can enable Book recurring and choose interval, unit, and occurrences. Keep occurrence counts reasonable so the visitor does not accidentally create more appointments than expected.
After a recurring booking, review the created appointments as a series. Confirm each occurrence uses the expected host, location, timezone, and calendar write back.
Payment Redirects
Some booking flows require payment. When the booking API returns a checkout URL, Agiled sends the visitor to checkout instead of showing the immediate booking confirmation page.
Test paid booking flows with the same payment method configuration customers will see. Confirm the booking is not treated as complete until the payment path matches your operating process.
Test Customer Edge Cases
Before publishing a high-traffic booking link, test the cases customers are most likely to hit: no available slots, mobile booking, timezone changes, required question validation, payment cancellation, and rescheduling or cancellation links. These tests catch setup issues that a single successful booking may miss.
If the booking is embedded on another website, test both the direct Agiled link and the embedded page. A working direct link does not prove the website embed, tracking scripts, or mobile container behaves correctly.
Availability Depends On
Available slots depend on:
- Booking page status.
- Event type settings.
- User availability.
- Buffers.
- Time zone.
- Existing appointments.
- Connected calendars.
After Booking
Check that the appointment appears in Agiled and that any connected calendar receives the booking.
The confirmation page also provides calendar actions. Visitors can add the event to Google Calendar, Outlook, Apple Calendar, or download an ICS file.
If the appointment does not appear, compare the public confirmation, appointment list, calendar integration, payment status, and notification delivery before manually creating a replacement booking.