Most academies do not have a booking problem, they have a collision problem: the coaching session and the public hire are sold from different diaries, so the pitch goes out from under the squad and somebody spends Monday morning apologising. Putting coaching on the same calendar as every court, pitch and resource removes that class of mistake rather than reducing it. This page is specific about what we do here — and equally specific about what we do not.
Not all of them are software problems. These are the ones that are.
When coaching lives in its own diary, nothing stops the public side selling the same surface at the same time. One calendar covering courts, coaches, classes and resources means the session occupies the space and the space is simply not offered — and booking-window control decides when slots open in the first place.
Selling one session at a time suits nobody: the customer re-books every week and you carry the admin. A class pack or credit balance is bought once and drawn down as sessions are booked, and the same balance works on a court hour, so a coaching customer who also plays socially has one wallet rather than two relationships.
Attendance marked on paper and typed up later is attendance that does not get typed up. Recording it against the session as it happens means it exists the same evening, which matters because who has stopped turning up is the earliest warning you get that a customer is about to leave.
An academy rarely loses customers in a dramatic way; people simply stop rebooking. Booking history plus segmentation puts the lapsed group in front of you as a list, and the growth layer drafts the message to bring them back — cheaper than replacing them with strangers.
Four steps, all of it standard configuration rather than a bespoke build.
Courts, pitches and halls as resources, each with its own slot lengths, rate card and booking window.
Each group as a class with its own capacity, on the calendar that holds the space it uses.
A coach calendar connected to the class or resource, with team access scoped by permissions.
Sell a block as a class pack or credit balance; mark attendance against each session.
Written down because finding this out after a migration is worse for you than losing the signup is for us.
There is no account that holds several participants under one paying adult with a single invoice. The paying adult is the customer; use custom forms to capture which child a booking is for. If one payer with several participants is the centre of your business, this is a real gap and you should weigh it before moving.
Second- and third-child pricing is not a rule that applies itself. You can achieve the discount with a scoped promo or voucher code, capped by use, but somebody has to hand it out — it will not attach automatically because two customers are related.
There is no "term" that enrols a participant for a dated block and renews itself next season with holidays excluded from schedule and price together. A course is sold as a pack of sessions instead, which covers the commercial job — buy once, attend many — without the term calendar around it.
Yes, through packages, class packs and credit wallets, which are on every plan including the free one. A customer buys a block of sessions once and books against the balance, and the same balance can be spent on a court hour or a class rather than being locked to one activity. Collection runs through your own payment gateway, so the money settles directly to you.
Not today, and we would rather say so here than after you have migrated. There is no family account that holds several participants under one payer with a single invoice, and no automatic sibling-rate rule. What people do instead: the paying adult is the customer, custom forms capture which child each booking is for along with anything else you need at checkout, and a discount is applied with a promo or voucher code. It works, but it is a workaround rather than a feature, and if family billing is the core of your operation you should weigh that carefully.
Yes. A session carries its attendance register, so who turned up is recorded against it rather than transcribed from paper later. Team access is controlled with custom access and permissions, so staff can be limited to what they need to see.
Coaching sits on the same calendar as everything else — one calendar covers every court, coach, class and resource, and a coach calendar can be connected to the class or resource it occupies. Because the session holds the space, the space is not available to a public booking. Booking-window control decides when slots open at all, which is the other half of the problem.
Customer records carry booking history, and segmentation groups people by how they actually behave — regulars, lapsed, one-off. Real Sports OS reads that and drafts the campaign to bring a lapsed group back, which is where an academy's revenue usually is: the family who quietly stopped rebooking, not the one who never signed up.
Free to start. No card needed, and bookings settle into your own payment account.