bookings

Booking lifecycle management tracks events through pending, confirmed, rescheduled, cancelled, and rejected states. It handles attendee management, no-shows, and reminders while preserving iCalUID references for external calendar compatibility.

Rescheduling creates a new booking entry linked to the original booking record. The system preserves the iCalUID and generates public cancel or reschedule tokens, maintaining a clear reference chain between the original and rescheduled events.

Yes, the booking system integrates with external calendars via iCalUID preservation and ICS endpoints. It references external systems including Google Calendar, Zoom, and Daily.co, allowing attendees to sync booking data across platforms.

Attendee management tracks no-shows and sends reminders as part of the core booking lifecycle. The system manages attendee lists directly within pending, confirmed, or cancelled states, ensuring accurate attendance records.

Yes, cancellation and rescheduling require public tokens generated by the booking system. These tokens secure the action and link the original booking to any rescheduled entry, preventing unauthorized modifications.

iCalUID preservation maintains calendar compatibility when bookings are rescheduled. By keeping the original identifier, external systems like Google Calendar can update existing events instead of creating duplicates.