Most small studios don't have a front desk. They have a phone face-down on a shelf, buzzing through a 6 a.m. reformer class, and an owner who checks it between clients and answers everything in one guilty burst at 9 p.m.
That's the job Becky was built to take over. Becky is BookYourMat's AI receptionist. She works over ordinary SMS on your studio's number, and the important part is that she converses -- she reads what a client actually wrote, asks a follow-up if she needs one, and then does the thing. She books. She reschedules. She cancels. She promotes someone off the waitlist. The client never downloads an app, never taps a link, never creates a login.
That distinction matters more than it sounds. Almost every studio platform can send a triggered message -- a reminder 24 hours out, a welcome sequence, a "your package is running low" blast. Those are one-way. They fire on a schedule and they don't understand a reply. If your client texts back "actually can I move it to Thursday?", a triggered reminder has nothing to say, and the request lands in your lap anyway.
Here are nine conversations Becky finishes on her own.
1. "Can I move my 6pm to tomorrow?" -- sent while you're teaching
A client texts mid-afternoon asking to shift tonight's session. Becky looks at your live schedule, checks the class she's currently booked into, checks what's actually open tomorrow with capacity and instructor coverage, offers the real options, and moves the booking once the client picks one. Your calendar updates. The old spot frees up.
How this differs from a triggered message: a reminder can only tell her she has a class at 6. It can't read "tomorrow," can't check tomorrow's capacity, and can't release the seat she's leaving. The reschedule is an actual write to your schedule, made from a text message, with no owner in the loop.
2. "Do you have anything for two people on Thursday?"
Duets and semi-privates are where most booking flows fall apart, because they need two spots held together and a partner named. Becky handles the coordination in the thread -- confirming who the second person is, finding a slot that fits the class type, and booking both spots as one appointment rather than two hopeful singles.
How this differs from a triggered message: there is no automation in the world that can decide who the partner is. That's a question, and questions need a conversation.
3. "How many sessions do I have left?"
The single most common studio text, and the one owners resent most, because it always arrives at 10 p.m. and it always requires opening something. Becky answers it from the client's actual package -- what they bought, what's been used, what's remaining -- in the thread, immediately, at whatever hour it was asked.
How this differs from a triggered message: a "package running low" automation fires when you decided it should. It doesn't answer the question the client asked at the moment she asked it, and it can't answer the follow-up ("wait, did my Venmo from Sunday go through?"). Becky can, because BookYourMat auto-matches incoming Venmo and Zelle payments to the right client's package -- so the balance she quotes is current, not a spreadsheet's best guess.
4. "Put me on the list for Saturday 9am" -- and then getting promoted off it
The 9 a.m. is full. The client asks to be on the waitlist. Later, someone cancels. Becky reaches out to the waiting client, and when they say yes, she books them through the normal booking path -- same capacity checks, same conflict guards, same calendar write as any other booking. The seat that was about to go empty gets filled without you opening anything.
How this differs from a triggered message: a waitlist alert that says "a spot opened, click here" is a race and a dead end -- whoever taps first wins, and whoever's driving loses. Becky's promotion is a conversation with a specific person, and the booking happens in the reply, not on a landing page.
5. "Can my daughter use my package for the Sunday class?"
If your studio has family package sharing turned on and the two clients are linked as a family or partner group, one member's package credit can cover another linked member's compatible class. So the answer to that text isn't "let me check and get back to you" -- Becky can confirm the arrangement and book the daughter against the shared package right there.
How this differs from a triggered message: family logic is a lookup plus a judgment plus a booking. Broadcasts don't do lookups. This is the kind of question that historically ate ten minutes and two phone calls.
6. "I'm so sorry, something came up an hour before class"
Late cancels are emotional and they're where owners lose the most time -- the apology, the policy explanation, the decision about whether to be generous. Becky can take the cancellation over text, apply your studio's actual policy consistently, and free the spot so the waitlist can move. Consistency is the quiet win here: the policy gets applied the same way at 5 a.m. as it does when you're annoyed on a Friday.
How this differs from a triggered message: a cancellation policy in an automated email is a paragraph nobody reads. Applied in conversation, at the moment it matters, it's a policy your clients actually experience.
7. "You've got two sessions left" -- before they notice
This one starts on Becky's side. When a client's package is running low, that's a moment worth a human-sounding text rather than a mass email -- and because it's a conversation, the client can reply "yes, send me another 10-pack" or "actually I'm traveling in March, can I hold off?" and Becky handles either branch.
Studio-wide nudges are still your call, not hers: BookYourMat's broadcasts let you compose a one-off SMS or email and target it -- holders of a specific package, people whose package is running low, clients who tried once and never came back, lapsed clients, members renewing soon, or a hand-picked list -- with a live recipient count before you send. Owner sends broadcasts. Becky handles the one-to-one thread.
How this differs from a triggered message: the triggered version ends when it's sent. The conversational version ends when the client has actually decided something.
8. "Can I bring a friend on Wednesday?"
A guest request has three parts: is there capacity, does the class type allow it, and how does the guest get paid for. It's exactly the kind of small question that isn't hard but is interrupting -- and it's the kind of question that goes unanswered until after class, by which point the friend has made other plans.
Becky reads the class, the capacity, and the client's package, answers the actual question, and books it if the answer is yes.
How this differs from a triggered message: you cannot pre-write this. It's a fork, and forks need a reader.
9. The 11:40 p.m. booking
Someone finds your studio, texts your number after a long day, and asks what's available Saturday morning. In most studios that text gets answered at 8 the next morning, if it gets answered. Becky answers it at 11:41 p.m., offers real open times, and books one.
How this differs from a triggered message: there's no trigger to fire. Nobody has done anything yet. This is an inbound stranger with intent, and the only automation that catches it is one that can hold a conversation.
The pattern underneath all nine
Every one of these is a reply. That's the whole line between an AI receptionist and a notification system.
A notification system pushes: reminders, sequences, blasts. Useful, and BookYourMat does that too. But push automations are built around what you predicted your clients would need. Every text above is a client needing something you didn't predict -- a different day, a second person, a friend, a balance, a spot that just opened -- and the only way to serve that is something that reads and answers.
The practical effect for a solo owner is that the phone stops being a queue. You finish a class, you glance at your dashboard, and the four things that came in during that hour are already handled, with the full transcript there if you want to read it. You stay in control -- you can see every conversation Becky had, and you decide how much autonomy she gets -- but you're not the router anymore.
See it answer
The fastest way to judge an AI receptionist is to watch it handle a message it wasn't expecting. That's most of a demo: we'll walk your actual schedule, your actual class types, and show you what Becky does with the messages your clients really send.
Book a 30-minute demo and see what your front desk looks like when it answers for itself.
