Public Booking Flow
Understand what visitors see when they book a meeting.
The public booking flow is the customer-facing experience opened from a booking page link or embedded booking page.
Test it like a visitor, not like an admin. Public booking should work without workspace access, internal navigation, or hidden assumptions.
What Visitors Do
- Open the booking page.
- Choose an event type if the page has more than one.
- Pick a date and available time.
- Enter name, email, phone, timezone, notes, and any custom questions.
- Confirm the booking.
If the event type is paid, the visitor may need to complete payment before the booking is finalized.
The visitor does not need workspace access. If a public booking link asks for a workspace sign-in, check that you copied the public booking URL, not an internal workspace route.
Test this flow in a private window before sharing the link. Confirm the visitor can understand the event type, choose a timezone, answer required questions, and finish without workspace access.
If the booking page has multiple event types, test each one. Different event types can have different hosts, availability, questions, payments, buffers, and confirmation behavior.
If a booking is paid, test the payment path and the scheduling path together. Payment success without an appointment, or an appointment without payment, both need setup review.
Information Visitors Enter
Name and Email
Used for the appointment record and meeting communication.
Phone
Useful for phone calls, reminders, or quick follow-up.
Timezone
Shows the booking time correctly for the visitor.
Notes
Lets the visitor add context before the meeting.
Custom Questions
Come from the form attached to the event type.
Keep custom questions short enough to answer during booking. Long qualification forms usually work better as CRM forms before or after the appointment.
After Booking
After booking, Agiled creates the appointment and shows either a thank-you message or redirects the visitor to the configured URL.
Review the appointment inside Agiled after a test booking. Confirm the attendee, time, timezone, location, notes, custom answers, payment state, and calendar event. If any follow-up automation should run, check the related task, CRM activity, or workflow run too.
Reschedule and Cancellation Expectations
Tell visitors how to reschedule or cancel if your process requires it. If the confirmation email includes calendar details or links, test those messages before sharing the booking page broadly.
Host Preparation
After a booking is created, the host should be able to see the visitor name, email, selected time, timezone, location, notes, and custom answers. If the host needs a deal, task, ticket, payment check, or project note before the meeting, confirm that handoff is created during testing.
The public booking flow is not complete until the host has the preparation context needed to run the meeting.
If the Visitor Cannot Finish
Check active booking page status, selected event types, availability, lead time, payment setup, required questions, and calendar conflicts. Use the exact public link the visitor used when troubleshooting.
Also check whether a custom domain, embedded page, browser extension, or website script is affecting the public page differently than the direct Agiled link.
Public Booking Test Checklist
Before publishing:
- open the page in a private browser window
- confirm event type names and descriptions are customer-safe
- choose a slot in the expected timezone
- complete required questions
- test payment if the event type is paid
- confirm the appointment record, email, calendar event, and workflow follow-up