Configure how and when clients can book your classes
Booking Settings
Booking settings control when clients can book, how far in advance, and other rules that affect the booking experience. Booqd supports two booking modes: class-based booking (traditional schedule) and flexible booking (appointment-based).
Hierarchical Configuration
Booking settings follow a hierarchical override system. You can set workspace-wide defaults and then override them for individual service types. The system uses a cascade: service-type setting â workspace default. This means you can have different booking rules for different class types.
âšī¸
If a service type does not have its own booking settings, it automatically inherits the workspace-level defaults.
All Booking Settings
â°
Minimum Notice (minNoticeHours)
How many hours in advance clients must book. Default: 0 (no notice required). Example: set to 2 so clients cannot book less than 2 hours before a session.
đ
Max Advance Days (maxAdvanceDays)
How far ahead clients can book. Default: 30 days. Example: set to 7 to only allow booking one week in advance.
âī¸
Minimum Gap (minGapMinutes)
Minimum time gap required between a client's consecutive bookings on the same day. Prevents back-to-back overload.
âī¸
Maximum Gap (maxGapMinutes)
Maximum time gap allowed between consecutive bookings. Leave empty for unlimited.
âŽī¸
Buffer Before (bufferBeforeMinutes)
Required buffer time before each session. Accounts for travel time or preparation.
âī¸
Buffer After (bufferAfterMinutes)
Required buffer time after each session. Allows cleanup or cooldown between sessions.
đ
Waitlist
Enable or disable the waitlist for full classes. Default: enabled.
âŗ
Waitlist Timeout (waitlistTimeoutHours)
How long a waitlist offer stays valid before expiring. Default: 24 hours. If the promoted client does not respond within this window, the next person in line is offered the spot.
â
Require Confirmation
Require manual approval before bookings are confirmed. When enabled, bookings start as "Pending" and you must approve or reject them.
đ
Calendar Conflict Mode
How to handle conflicts with clients' connected calendars: **Allow** (ignore conflicts), **Warn** (show warning but allow), or **Block** (prevent booking if conflict detected).
â ī¸
When setting buffer times, the system validates that clients have enough time between sessions including the buffer. For example, if a session ends at 10:00 and bufferAfterMinutes is 15, the next booking cannot start before 10:15.
Waitlist Settings
When enabled, clients can join a waitlist for classes that are full. If a spot opens up (due to a cancellation), the first person on the waitlist is automatically promoted and notified.
â
Enabling the waitlist is recommended for popular classes. It helps you fill spots from cancellations and shows you the real demand for your classes.
Per-Class Waitlist Configuration
You can configure the waitlist setting individually for each class. This gives you fine-grained control over which classes have waitlists enabled.
â
Enabled
Waitlist is always active for this class
â
Disabled
No waitlist for this class, even if workspace default is on
đ
Workspace Default
Inherits the workspace-level waitlist setting
When a session is created from a class, it inherits the class waitlist setting. The cascade logic is: session setting â class setting â workspace default. This means you can override the behavior at any level.
Booking Confirmation
By default, bookings are confirmed automatically when a client books a class. However, you can enable Require Confirmation to manually review and approve each booking before it is confirmed.
When this setting is enabled, new bookings will have a Pending status. You will receive a notification (push, in-app, and email) for each pending booking. From the session detail view, you can approve or reject each booking individually.
1
Client Books
A client requests a booking for your class
2
Pending
The booking is created with "Pending" status
3
You Get Notified
You receive a push notification and email
4
Review
Open the session detail and approve or reject the booking
5
Client Notified
The client is notified of your decision
1
Client Books
A client requests a booking for your class
2
Pending
The booking is created with "Pending" status
3
You Get Notified
You receive a push notification and email
4
Review
Open the session detail and approve or reject the booking
5
Client Notified
The client is notified of your decision
Per-Class Confirmation Configuration
Just like the waitlist, you can configure the confirmation requirement at multiple levels. The cascade logic is: session setting â class template setting â workspace default.
â
Enabled
Confirmation required for this class, regardless of workspace default
â
Disabled
No confirmation required, even if workspace default is on
đ
Workspace Default
Inherits the workspace-level confirmation setting
â
Use the workspace-level setting as a global default, then override it for specific class templates or individual sessions where you need different behavior.
Flexible Booking Mode
Flexible booking lets clients book appointments based on instructor availability instead of fixed class schedules. This is ideal for personal trainers, consultants, tutors, and other 1-on-1 service providers.
đ
Slot Duration
Default appointment length (e.g., 60 min)
â¸ī¸
Buffer Time
Rest time between consecutive appointments
đ
Advance Booking
How far ahead appointments can be booked
đ
Minimum Notice
Required notice before an appointment
âšī¸
Flexible booking can be enabled alongside class-based booking. See the Flexible Booking Setup guide for detailed configuration.