Roadmap
Changelog
Help Center

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 customers to choose a later end date for subscription

With customers only being able to cancel exactly a month from the date they choose to cancel I am finding customers are cancelling earlier than they actually intend to. It would be good if the they could cancel with at least a months notice so they could also choose a later date. Say for example they know when they’re returning to work and could select that future date.

Courtney Coleman 8 days ago

💡

Feature Request

Allow users to set a fixed number of payments on subscriptions

Summary Allow admins to create a subscription-style payment option that automatically stops after a fixed number of payments, rather than continuing indefinitely. Use Case Some course providers offer customers the option to pay for a course in instalments, for example 2, 3, or 4 monthly payments. Currently, this is often managed manually: the customer pays an initial amount when booking, then the provider charges the balance payment(s) later manually. This can create extra admin. A fixed-payment subscription would allow providers to offer instalment plans where payments are collected automatically, reducing manual follow-up and helping customers spread the cost without needing an external “buy now, pay later” provider. Proposed Functionality When setting up a subscription payment option, allow the admin to enter a Number of Payments. For example: 2 payments of £150 3 payments of £100 4 payments of £75 The subscription should automatically cancel or stop after the selected number of payments has been collected. Requirements Admin can choose the number of payments/instalments. Payments are taken automatically at the subscription interval. Subscription automatically ends after the final payment. All instalments are the same amount. Existing ongoing subscriptions should remain the default.

bookthatin 15 days ago

💡

Feature Request

Add a grace period before registers auto-advance to the next date

It would be really helpful to have an optional grace period before a register automatically moves on to the next class date after a session has finished. 🧾 Current issue At the moment, once a class end time has passed, the register/calendar can move forward to the following week quite quickly. This means that if a coach or admin updates the register shortly after the class has finished, they may accidentally start editing next week’s register instead of the one that has just taken place. ⚽ Example If a class finishes at 10:00am and the coach updates attendance at 10:05am, 10:15am, or even a little later, it would be useful if the system still defaulted to today’s completed register rather than automatically showing the next week’s date. ⚙️ Suggested improvement Could there be an optional setting where each business can choose how long the completed register remains visible after the class finishes? For example: 15 minutes after the class ends 30 minutes after the class ends 60 minutes after the class ends Custom time set by the business 👥 Why this should be optional I understand this may not suit every business as a default, because some businesses may run back-to-back sessions and may want the next register to appear straight away. So it would be ideal if this could be a setting at company, venue, class, or event level. ✅ Why this would help This would reduce accidental edits to future registers, especially when: Training new coaches Updating attendance just after a session Checking who attended at the end of class Managing multiple weekly classes Avoiding confusion between today’s register and next week’s register A small optional grace period would make the register much safer and easier to use after each class finishes.

Munchie75 23 days ago

💡

Feature Request

Planned

Multi-Line Text Booking Questions have several blank spaces in the answer

When a multi-line booking question appears on the booking form, there are several blank spaces pre-populated as the answer. This means the booker either has to delete all the blank spaces first, or they enter their answer after the blank spaces, which can make it hard to read their answer on the register.

barryroad 26 days ago

🪲 Bug Report

Planned

Typing in a date in a date field isn't recognised correctly by the system

When a Date field is used on a booking form, if someone decides to type in the date instead of using the pop up date selection tool, the field struggles to recognise the input. e.g. if you type 15/12/2015, then the field is automatically updated to 15-Jan-0012. A couple of solutions are possible here: (Preferred) Interpret typed entries correctly Don't allow typed entries - force people to use the date selection tool to ensure correct dates are entered

barryroad 26 days ago

🪲 Bug Report

Bug - overlapping times of sessions not displaying correctly

Bug - overlapping times of sessions not displaying correctly on booking form When booking multiple sessions (ie 4) of overlapping times so time slots can’t be used. The booking form displays the ‘full’ day timings 9.00-4.00 when the sessions being booked are 9.00-1.00 and 12.00-4.00 - the confirmation is correct but the pre-booking session selection displayed on the form isn’t.

Abby about 1 month ago

🪲 Bug Report

Bug - overlapping times of sessions not displaying correctly on booking form

When booking multiple sessions (ie 4) of overlapping times so time slots can’t be used. The booking form displays the ‘full’ day timings 9.00-4.00 when the sessions being booked are 9.00-1.00 and 12.00-4.00 - the confirmation is correct but the pre-booking session selection displayed on the form isn’t.

Abby about 1 month ago

💡

Feature Request

Planned

Give option to calculate final payment for cancelled subscriptions using number of sessions before end of notice period

Summary: Introduce an option to calculate the final payment for cancelled subscriptions based on the number of sessions remaining within the notice period, rather than a pro-rata percentage of time. Current Behaviour: When a subscription is cancelled with a notice period of 1 month or more, the system always generates a final payment. This payment is taken on the next billing date (typically the 1st of the month). The amount is calculated as a pro-rata percentage of the normal subscription amount, based on the remaining time in the notice period. Example: If cancelled on 10th April, the subscription ends on 10th May. The final payment on 1st May is ~1/3 (10 days’ worth) of the monthly fee. Requested Behaviour: Add a configurable option to calculate the final payment based on the number of scheduled sessions within the notice period instead of time. The system should: Identify all sessions occurring between the next billing date and the end of the notice period. Calculate the final payment based only on those sessions. Example Scenario: Cancellation date: 10th April Notice period ends: 10th May If there are no sessions scheduled in early May (e.g. due to holidays), then: No sessions fall within the final billing period Final payment on 1st May = £0 Expected Outcome: Users can choose between: Time-based pro-rata calculation (current behaviour) Session-based calculation (new option) This provides more accurate billing for businesses with irregular schedules (e.g. school term breaks).

bookthatin about 1 month ago

💡

Feature Request

Credit Card Removal Notification & Customer Intent Visibility

🎯 Summary Introduce a notification system that alerts administrators when a customer removes their payment card from their account, along with optional context around the reason for the action. 💡 Background Currently, when a customer removes their card from the system, there is no alert or visibility from an admin perspective. This can make it appear as though the customer has abruptly left the business, when in reality there may be a valid or temporary reason (e.g. holidays, switching to pay-as-you-go, short-term pause). This lack of visibility creates confusion and can negatively impact: Payment processing (failed payments at end of month) Customer communication Retention opportunities ✅ Proposed Features 1. Card Removal Notification Trigger an automatic alert/email to the business owner/admin when a customer removes their card Include: Customer name Child’s name Class/session Date/time of removal 2. Optional “Reason for Removal” Prompt When a customer removes their card, present a simple optional dropdown or text field: Examples: Taking a short break Switching to pay-as-you-go No longer continuing Other (free text) 3. Dashboard Indicator Flag customers who have removed their card Highlight as: 👉 “Payment method removed – action required” 4. Smart Workflow Trigger Allow automation triggers such as: “Card removed” → send follow-up email “Card removed” → create admin task 🚀 Benefits For Businesses: Reduces unexpected failed payments Improves cash flow visibility Enables proactive, supportive communication Increases customer retention For Customers: Provides a clearer, more transparent experience Reduces awkward follow-up conversations Encourages open communication 💬 Real Use Case A customer temporarily removed their card due to upcoming absences and planned to return the following month. Without context, this appeared as a cancellation. A simple alert + reason field would have immediately clarified intent and avoided confusion. 🧠 Priority Level High – This directly impacts: Payment success rates Customer retention Admin efficiency

Munchie75 about 2 months ago

💡

Feature Request

Completed

Cancel subscriptions in line with Minimum Subscription period when an account is deleted

When a customer deletes their account, their subscription currently cancels immediately, applying any cancellation notice period that has been set on the subscription. For businesses, this currently means there is a loophole for customers to avoid a minimum subscription period, if you have one in place. It would be really helpful if deleting an account triggered subscription cancellation in line with any applicable minimum subscription period - meaning the subscription would end at the later of: the minimum subscription period, or the cancellation notice period This would ensure businesses are still protected and paid correctly, even if a customer chooses to delete their account. It would also be important to update the warning message shown at the point of account deletion, so customers clearly understand that their subscription will continue until the end of the applicable period.

bookthatin about 2 months ago

💡

Feature Request

Add a Print Register option without needing to download an exported file

At the moment to print a register you have 2 options: Download the register as a spreadsheet file and print it from there Print using the browser print option This item would add a ‘Print’ option to the register page which allows a nice printable version of the register to be printed off

bookthatin about 2 months ago

💡

Feature Request