Reserve a Court

Use this page when you need the public court-booking capability overview rather than a route map or internal operator explanation.

What this experience is for

SyncReserve supports a guest booking experience that can take a customer from availability search to confirmed reservation in one structured flow.

For clubs evaluating the platform, the important point is not the exact screen order. It is that the booking experience can support:

self-serve reservations from the public site
member and non-member booking paths
pricing, review, and policy acknowledgement in the same flow
payment handling that matches the club's booking rules
confirmation that fits repeat guest and member behavior

How the booking experience usually works

The reserve flow behaves like a guided booking experience rather than a static form.

At a high level, guests usually:

choose the kind of reservation they want
review available times that match the club's rules
confirm guest details when needed
review price, policies, and due-now terms
complete payment if the club requires it
receive confirmation

That structure gives clubs room to support simple bookings for casual guests as well as more policy-driven reservations for members, groups, or premium inventory.

What can vary by club

Not every club exposes the exact same booking experience.

some clubs lead with court-first availability
some need sport or activity selection first
some support larger groups, add-ons, or bundled items
some require payment immediately, while others allow different due-now policies
some show member-aware pricing or access conditions during the flow

That flexibility matters because SyncReserve is intended to support different club operating models without forcing the same booking experience everywhere.

What clubs can communicate in the booking flow

The booking experience is also where clubs can make commercial and policy decisions visible at the right time.

price and payment timing
promo or member pricing context
waivers, agreements, or policy acknowledgements
cancellation and booking terms
any extra items tied to the reservation

What this page is not

This page is a capability summary.

It is not:

a complete step-by-step booking tutorial
a description of every booking rule branch
a breakdown of internal booking-state logic