Booking Page
How the public booking page works for your clients in ChronSync.
Booking Page
The booking page is the public-facing interface your clients interact with. It is accessible at your booking URL and requires no login.
Page Layout
When a client visits your booking link, they see:
Header
- Your display name and avatar
- The event type title and description
- The duration of the meeting
Calendar View
A monthly calendar showing available dates. Dates with no available slots are greyed out. The client clicks a date to see the available time slots.
Time Slot Picker
After selecting a date, a list of available time slots appears. Slots are shown in the client's local timezone (detected automatically from their browser). Each slot shows the start time.
Booking Form
After selecting a time slot, the client fills in:
- Name (required)
- Email (required)
- Notes (optional) -- Any context or questions for the meeting
Confirmation
After clicking Confirm Booking, the client sees a confirmation screen with:
- The meeting date and time
- A summary of what they booked
- A note that a confirmation email has been sent
Timezone Handling
The booking page automatically detects the client's browser timezone and displays all time slots in that timezone. A timezone selector is also available for clients who want to view slots in a different timezone.
Mobile Experience
The booking page is fully responsive. On mobile devices, the calendar and time slots stack vertically for easy thumb navigation. The booking form adapts to smaller screens.
Confirmation Email
After booking, the client receives an email containing:
- Meeting date and time (in their timezone)
- Event type name
- Your name
- Any relevant notes
- A link to cancel or reschedule if those options are enabled
Cancellation and Rescheduling
If you allow client-initiated changes, the confirmation email includes links for:
- Cancel -- Cancels the booking and frees the time slot
- Reschedule -- Opens a new time picker to move the meeting
These links contain secure tokens and do not require the client to log in.