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.

Allow ā€œDrop Inā€ sessions to accept bookings during a session

Bookings currently cut off at the start of the next session. This works well for classes where people book in advance and can’t book on the door. However, this can cause issues for businesses who want to take on-the-door payments via Book That In for drop-in customers, as they can’t start a booking for the current session after that session has started. Impact Businesses have to take payments using a different system (e.g. SumUp) They need to manual enter the booking later It causes extra admin and a requirement for multiple payment solutions. Proposed Solution When ā€œDrop Inā€ = YES: Use session end time as the booking cut-off When ā€œDrop Inā€ = NO: Keep current behaviour Outcome Enables real-time, in-session bookings, reduces admin, and keeps everything inside Book That In.

bookthatin 8 days ago

šŸ’”

Feature Request

Nickname Field

Currently business owners can’t change the ā€˜Participant Name’ on a booking, as that name field is pulled in from the customer’s account, and they may be using that same Participant Name for a booking with another company. The customer can change this name themselves, but this Feature Request would allow the business owner to change their view, without changing the customer’s Participant name. Add an additional field called Nickname or 'Likes to be Called' which is auto-populated with the participant’s name on registration, however it is editable (by business owners and teachers/coaches). Then this would be the name that is displayed in the register. This would also help as we often get parents adding their child’s full name for the Participant’s Name field, but the parents say they call them 'NICKNAME'. We could then log the Nickname to make sure we use that in class.

Munchie75 about 1 month ago

šŸ’”

Feature Request

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 2 months ago

1
šŸ’”

Feature Request