Have something to say?

We want to hear from you! Tell us your thoughts and help us make Book That In the best it can be.

Session-level waiting lists (not block-level)

Summary: Allow waiting lists to operate at an individual session level, rather than only activating when all sessions in a block are full. Current behaviour At present, the waiting list only becomes available once all sessions within a block are fully booked. This works well for block or term-based classes, but not for PAYG providers. Problem For PAYG providers who only allow customers to book one session at a time, this setup is limiting. If a single session within a block is full, customers cannot join a waiting list for that specific date unless every session in the block is full. This means: Customers cannot express interest in a specific date they want to attend Providers miss the chance to capture and understand demand for popular individual sessions Requested behaviour Enable waiting lists to be configured per individual session, so that: If a specific session is full, a waiting list appears for that session only Customers can clearly join a waiting list for a particular date and time Providers can notify customers about a particular date in a block, if a space comes available

bookthatin 29 days ago

1
💡

Feature Request

Planned

Auto Re-enrolment – Include Late Bookings Automatically

Problem Auto re-enrolment is a hugely valuable feature, as it flips renewals from opt-in to opt-out, reduces admin, and eliminates payment chasing. However, auto re-enrolment currently only applies to customers who are booked onto the current or previous term at the moment the new term is created. Any customers who book after that point are excluded from auto re-enrolment, even if they are attending the same classes. This creates a bit of friction for some businesses, as they are incentivised to delay creating new terms until the very last moment to ensure everyone is captured. This is manageable for term-based businesses with natural breaks, but causes real issues for businesses using auto re-enrolment for rolling or monthly payments. For example, one client wants to charge on the 1st of the month while giving customers a week to opt out, but cannot do this reliably if classes run up to the 31st, forcing late charges and unnecessary complexity. Proposed Solution Add an option for auto re-enrolment to dynamically include any new bookings made into the current/previous term, after re-enrolment has been set up. This would allow businesses to create new terms earlier, confidently capture all eligible customers, and run cleaner renewal and payment cycles. This enhancement would make auto re-enrolment significantly more powerful for monthly and rolling payment models, while preserving its simplicity and time-saving benefits for term-based providers.

bookthatin About 1 month ago

💡

Feature Request