Why Your Gym Or Studio Should Let Customers Book And Pay Online

I run CageList. It's a marketplace where players book batting cages and facility owners get paid, and I built the whole thing myself — the booking flow, the payments, the reminder texts, all of it. I'm also the one who answers when something breaks. So when I tell you a gym or studio should let people book and pay on the website instead of over text, that's not a guess I'm making from the outside. It's what I've watched happen on a system I operate every day.

Here's the case, one piece at a time.

A text is easy to miss

If booking your gym means texting you, then every booking depends on you seeing that text, at a time when you're free to answer it, and then replying before the person moves on to something else. That's three things that all have to go right. Miss any one of them — you're coaching, you're asleep, your phone is face down on the desk — and the booking doesn't happen. Not because the person didn't want it. Because the message sat there.

A booking form on a website doesn't have that problem. It doesn't need you to be looking at your phone. It just takes the booking and holds it, whether you're free or not.

A booking without payment isn't a commitment

This is the one that took me longest to really see, because it's not obvious until you've run a system where money is on the line. When someone texts "can I get the cage at 6pm Thursday" and you text back "sure, see you then," what you have is an intention, not a booking. Nothing has actually happened. No card is on file. There's nothing stopping either side from just not following through, and no record of who said what if it goes sideways.

Take the payment at the time of booking and something changes. The person has now put something down. They've told you, with money and not just words, that they intend to show up. That's a different kind of commitment than a text thread, and it changes how seriously both sides treat the appointment.

Reminders work because nobody has to remember to send them

CageList uses Twilio to send a reminder text before a booking. I didn't build that because it's a nice feature — I built it because forgetting to send reminders was a real failure mode when reminders were something a person had to remember to do by hand. Automating it took that failure mode off the table entirely. The reminder goes out the same way every time, because a computer doesn't get busy and forget.

I don't have a clean number for how much this moves no-shows, and I'm not going to invent one. If you want a real answer, track your own no-show rate before you make the switch and after, and compare them yourself. What I can tell you is the mechanism: a reminder that fires on its own, tied to a booking that already has a card attached to it, is a very different thing than hoping someone remembers an appointment they made over text three weeks ago.

Chasing payment costs you time you don't get back

If you take bookings by text and collect payment in person — cash, a tap on a card reader, whatever — you're doing two jobs instead of one. You're running the session, and you're also the person who has to remember what was owed, follow up when it wasn't paid, and sort it out if someone disputes what they were charged. I use Stripe on CageList for exactly this reason. The charge happens at booking, it's recorded, and neither side has to reconstruct what was agreed to after the fact.

None of that is complicated. It's just work that doesn't need to be yours anymore.

What this actually looks like

It's not one big feature. It's three small ones, working together: a booking form that takes the request, a payment that's collected at the time of booking instead of chased down later, and a reminder that goes out automatically without anyone having to remember. Each one on its own helps a little. Put together, they take a process that used to run through your personal phone and turn it into something that runs on its own, whether or not you're free to answer a text right then.

The honest trade-off

Setting this up takes more work up front than just handing out your cell number. You have to pick a payment processor, connect it to your booking flow, and decide what your cancellation policy actually is before you can enforce it automatically. That's real setup, and I'm not going to pretend it isn't.

But once it's built, it runs without you. That's the actual trade: a bit of upfront work in exchange for not being the single point of failure in every booking your business takes. I've been on both sides of that line — running things by text and running things through a system that handles it — and I'd rather be a text message away from my customers by choice, not because it's the only option I've given them.