Online class booking system

Compare class and course booking systems on capacity, waitlists and passes. Check how a multi week course is sold and whether every date is booked separately.

7 min readYouzse TeamUpdated

Most booking software is built around one customer in one slot. A class inverts that: one slot, a dozen customers, a cap you must not exceed and a set of people who bought ten sessions in March and are still working through them. Software that models an appointment and calls it a class will fail you on the second point.

The four things a class needs that an appointment does not

A capacity, enforced. Overbooking a Tuesday reformer class with twelve machines is not a minor inconvenience. A system that lets a thirteenth person book will do it on the night you are not looking.

A waitlist that moves by itself. Cancellations in classes arrive late and cluster, so a waitlist only earns its keep if it offers the place automatically and gives the next person a deadline before moving on.

A timetable that repeats. Classes run weekly for a term, then the term changes. Rebuilding the week by hand every time is the single biggest time sink studio owners report.

Passes and blocks. Ten class cards, monthly memberships and term blocks are how studios actually get paid. They need to draw down against attendance without you keeping a tally.

Get paid before the door

Pay on the day is the reason class businesses have a no show problem. Somebody who has not paid has nothing to lose by staying home in the rain. The seat they are holding was refused to somebody else.

Payment at booking fixes most of it. So does a block of sessions bought up front, which has the added effect of committing somebody to a course rather than to one session they will judge on how they feel that week.

Have a cancellation window and hold it. Something like twelve hours is normal. Publish it, put it on the confirmation and let the software enforce it rather than deciding case by case, because deciding case by case is how a policy becomes a negotiation.

What to test before you commit

  • Set a capacity and try to exceed it
  • Cancel a booking and watch the waitlist offer move
  • Build a recurring weekly timetable and change one week of it
  • Sell a ten class pass and check it draws down on attendance
  • Take a booking from a phone the way a customer would
  • Cover a class with a different teacher
  • Print or open a register for a session

A course is not a class, and most software treats them the same

A class is one session somebody books. A course is six weeks they commit to once, in a fixed group, usually paid up front. Beginners courses, improvers terms, a four week introduction to pottery: the money and the register behave differently from a drop in timetable.

The question worth asking any system is whether one purchase puts somebody on every date. Most do not. The common pattern, and the one Youzse uses, is to publish the dates as a repeating timetable and sell a package for the number of sessions, so the balance covers the course and each date is still booked against it. You get the capacity, the register and the money up front. What you do not get is a single enrolment that silently fills all six dates, so a learner who never books week four shows as a credit unused rather than an absence.

That distinction matters when you are comparing. A studio running fixed cohorts with a closed register wants enrolment, and should test exactly that before committing. A studio running terms where people occasionally miss a week is better served by the package, because an unused credit is visible and a no show against a pre filled booking is not.

Mixed timetables

Most studios are not purely classes. There are one to one sessions, assessments, occasional workshops and room hire. They share the same space and the same diary.

A system that handles only classes pushes the one to ones into a separate calendar and double bookings follow within a month. Check that both live in the same diary and that the room or the equipment is what gets booked, not just the teacher.

Gyms and fitness studios have the sharpest version of this. A weekly timetable of classes, a membership that entitles somebody to attend them, personal training sold by the hour and inductions that are neither. Where the membership and the class register do not meet, somebody spends every Monday working out who was entitled to be in the room.

Youzse runs classes, recurring series, class packages and one to one appointments in one diary, with payment taken at booking. Plans start at £19 a month, card payments are 1.5% plus 20p with nothing added on top, and there is 0% commission on anything you take, including the new clients who find you through the marketplace.

Try the last available class place

Record or actionWhat to check
CapacityConfigure a small test class with a fixed number of places.
Final placeBook the remaining place and inspect availability.
CancellationCancel a test booking and inspect the resulting status.
WaitlistCheck what action is needed when a place becomes available.

A pass purchase is not attendance

Use one sample customer who buys your chosen offer and another who books a class place. Inspect what each action creates. Do not assume a payment reserves a place, that cancellation creates a refund or that a waitlist entry automatically becomes a confirmed booking; test those behaviours.

Clear answers before you switch

The details that usually slow down a move: setup, pricing, bookings, records and how Youzse fits into your day.

The one that enforces a capacity, runs a waitlist without you, repeats a weekly timetable and sells class passes that draw down automatically. Those four are what separate class software from appointment software wearing a class label. The fourth is the one most often missing.

We value your privacy

Cookies keep Youzse running, improve the platform and help deliver relevant content. Read our privacy policy and cookie policy.