You shouldn't be answering "is the class full?" in the middle of teaching it.
Teaching is the whole reason the studio exists — and it's the thing that keeps getting interrupted. "Is it full? Can you put me on the waitlist?" is admin, and admin is exactly what a small studio can hand off.
01 The pain
Run a small studio and you're the teacher, the front desk, and the waitlist all at once. The messages land mid-class — is this one full, can I get in, am I on the list — and answering them means stepping out of the very session you're leading.
Cash is tight and it's easy to assume automation is a big-company thing. But the cost here isn't money — it's your attention, pulled off the mat every time a DM comes in.
02 Where your software stops
Your booking page shows the count, but it doesn't coordinate. It won't watch for a cancellation, offer the open spot to the next person waiting, and tell them it's theirs — that all falls back on you, usually while you're teaching.
The real-time waitlist choreography that would handle it isn't in most small-studio tools, or it's bundled into a tier built for a chain.
Software stops at "shows the count." The real gap is "a spot opened — who's next, and tell them."
03 Why you can't just offshore it
A remote service won't build for a studio with a handful of staff and a local regular base. They don't know your class culture, your members, or the warm tone your waitlist note needs to keep.
04 The gap I fill
I build the waitlist and full-class layer that runs quietly on top of your booking tool — moving people up when a spot frees, drafting the "you're in" note, flagging a class that's about to fill so nobody's left guessing.
And it doesn't message members on its own. You approve the note before it sends. Every spot offered is tied to a real opening in your schedule — if there isn't one, it says "not found" instead of promising a place that isn't there.