Skip to main content
GullySystem
Wellness

Online Booking Portal for Pilates studios

Let customers request or reserve an available service through a website.

Bookings and Appointments

Does this function belong in your operation?

Use when customers should make service or resource bookings online.

A customer chooses to book without contacting the office.

Clients book classes from the front desk or their phone, and the waitlist and cancellations are processed in order.

Bring the records the workflow depends on.

  • Bookable services
  • Availability rules
  • Required customer details

Outputs to check

  • Customer booking request
  • Confirmed or pending reservation
  • Change and cancellation history

Follow the online booking portal workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Present the offer

    Show bookable services, conditions and available times.

  2. 2. Collect the request

    Validate customer details and chosen service requirements.

  3. 3. Recheck capacity

    Confirm that the slot remains available before committing it.

  4. 4. Apply confirmation rules

    Complete required approval or payment handoffs and distinguish pending from confirmed.

  5. 5. Manage later changes

    Record cancellation, rescheduling and any separate refund decision.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

The customer

Selects a service, submits the required details and checks whether the request is pending or confirmed.

Receptionist or advisor

Works one list and not three, and confirms with a message from your number.

Owner

Compares online and staff-entered bookings and investigates cancellations or incomplete requests.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Payment succeeds but booking fails

Keep both references and route the case for reservation recovery or authorised refund.

Last slot taken concurrently

Recheck capacity before confirmation and show the customer a clear outcome.

Customer cancels

Apply the booking policy and send any refund decision to the payment process.

Can this work independently?

The portal needs a source of availability and booking rules. A local calendar can provide it, but staff scheduling, payments and messages require defined connections. Taking an online payment and confirming a reservation are separate events that must be reconciled if either fails.

Systems and records it connects with

  • Appointment scheduling: Confirmed slots, cancellations and attendance outcomes.
  • Job cards: Service findings, approved work, parts and completion records.
  • Customer records: Permitted customer identifiers and service-contact details.
  • Payment gateway: Authorised payment attempts, outcomes and settlement references.

Configure, test and introduce the workflow.

  • We list what you offer and when staff are free. You supply photographs, the map and the opening hours. A draft page returns for your comments.
  • Questions for each service are agreed, such as vehicle number or breed. You tell us what staff must know. Keep it short. The page is tied to the calendar your counter uses. A test booking shows slots closing when taken. We check it together.
  • Confirmation wording is written. A payment gateway account is connected if you want deposits, and trial payments use its test setting. The link goes on your signboard, visiting card and messages. Staff practise confirming requests. Then customers arrive.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Customers cannot reserve unavailable capacity.
  • Required details are validated.
  • A request is distinguishable from a confirmed booking.
Pilates studios

How the business operates.

Reformer, mat and private sessions are booked through Pilates Studio Management Software, which GullySystem sets up for a studio. Instructors and the front desk share one timetable. Classes hold a fixed number of places, with waitlists, session packs, client intake and health notes, attendance and invoices on the same screens. Instructor payouts follow the sessions taught.

Class timetable and capacity

Set weekly reformer, mat, tower and chair classes with an instructor, a room and a fixed number of places for each.

Booking and waitlist

Take class bookings from the desk or from a client’s phone, with the waitlist and cancellations handled in order.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Class timetable and capacity. Set weekly reformer, mat, tower and chair classes with an instructor, a room and a fixed number of places for each.
  • Booking and waitlist. Take class bookings from the desk or from a client’s phone, with the waitlist and cancellations handled in order.
  • Private and duet sessions. Book one-to-one and two-person sessions against an instructor and an apparatus, with their own pricing and notes.
  • Session packs and memberships. Sell packs, monthly plans and drop-ins, with sessions used, sessions left, validity dates and freezes recorded.

Operational bottlenecks to check

Class places are counted on a chat group

A reformer class has a fixed number of machines. When bookings arrive by message and call, one more client than the studio can seat may be promised a place.

Pack balances live in a notebook

A client buys a pack of ten sessions with a validity period. Sessions used, sessions left and the expiry date are written in a register that only the front desk can read.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and trial

    A person asks about classes by call, message or the website. The enquirer is booked into an introductory class, and the enquiry is recorded with its source.

  2. 2. Intake

    The front desk opens the client’s profile and records health notes, goals and any injury, so the instructor sees them before the first session.

  3. 3. Booking

    A client books a place in a reformer or mat class, a duet or a private session. If the class is full, the booking goes onto the waitlist.

  4. 4. Class and check-in

    Attendance is marked at the studio, and one session is taken off the client’s pack. The instructor’s count for the month goes up by one class.

  5. 5. Billing

    A pack, a monthly membership or a single drop-in is billed with its payment mode. Socks and other retail items go on the same invoice.

  6. 6. Renewal

    When a pack nears its last session or its expiry date, the client is reminded to renew. Clients who have stopped coming are listed for a call.

Industry reports to connect with

  • Class fill by day, time and instructor
  • Pack and membership balances, with expiry dates
  • Instructor classes and payouts for the month
  • Late cancellations and no-shows

Questions before implementation.

When should pilates studios consider online booking portal?

Use when customers should make service or resource bookings online. A customer chooses to book without contacting the office.

What should we bring to the requirements discussion?

Bring anonymised examples of Bookable services; Availability rules; Required customer details. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Let customers request or reserve an available service through a website. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Online payment, immediate confirmation and external calendar connections require explicit scope decisions.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Customers cannot reserve unavailable capacity. Use this check when reviewing the first working version.

Talk to us

Discuss online booking portal for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements