Trial Class Follow-Up Scripts That Turn Visitors Into Members

Why trials go quiet

Here is the pattern this sequence is built around. A parent books a trial. The kid shows up, has fun, leaves. The parent means to sign up. Then Tuesday happens: work, dinner, homework, a sibling's game. By the weekend the trial is a warm memory and a task on a list nobody is looking at. If the school never calls, nothing moves it back up that list.

Silence is not a no. It is the absence of an answer, which is a different thing, and it usually means nobody asked in a way that made answering easy. That is what the sequence is for, and it has three rules: be fast (same day, not next week), be specific (say something only someone who watched the class could say), and make the next step one reply long ("want me to hold Tuesday?").

Everything below assumes your website already gets trial requests to a phone a human carries, within a minute, with the parent's name, the child's name, and the program. If it does not, fix that first. It is point 22 on the website checklist. Scripts cannot save a request nobody saw.

The full sequence at a glance

Three of the twelve are below, word for word. The complete pack, with the emails, the call script, and the objection replies, is in the free kit further down.

Before the trial: kill the first-day fear

Between booking and walking in, a family is holding a set of small unknowns: where to park, what to wear, whether the parent stays on the mat side, whether their kid will be the only new one in the room. You cannot know which of those is weighing on them, so answer all of them. Every message before the trial removes one.

The day-before reminder and the morning-of text follow the same pattern: short, one logistics detail, the name of the person who will greet them at the door. A name turns a building into a person.

Same day after the trial: the message that matters most

This is the one that does the work. The parent is still in the glow of watching their kid try something hard. Send it within two hours, while the car ride conversation is still happening.

The same-day email goes out that evening, after the text. It carries what does not fit in a text: the program page link, the schedule, the price, exactly how to enroll (a link, not "come by the desk"), and one or two photos from class if you have permission. The text starts the conversation. The email answers the questions the parent will Google at 10 pm.

Day 2 and day 7: ask for the yes

Two days of silence tells you nothing on its own, so treat it as a question still open rather than an answer. The day 2 text answers the thing they are most likely weighing but did not ask about — price or commitment — and then asks plainly. Something like: "Quick one: our kids program is {price}/month, no contract, cancel any time. Want me to save {Child}'s spot for {Day}?" If you do not publish prices, this is where you say your honest sentence about how you price.

Day 4 is a two-minute phone call. Not a pitch. "Hi, this is {Name} from {School}, just calling to see if you had any questions after {Child}'s class." If voicemail, leave it, then text "Just left you a voicemail, no rush, here if you have questions."

Day 7 is the last direct ask. It names the deadline honestly (the spot in that class, not a fake countdown) and gives permission to say no: "If now isn't the right time, totally fine, just let me know and I'll stop bugging you." A no is a useful answer: it ends the sequence and frees the spot.

No-shows and "we're thinking about it"

"We're thinking about it" is a polite placeholder, and underneath it is usually something concrete: price, the other parent has not agreed yet, the kid was nervous, or the schedule collides with something. You cannot know which, so the reply names the two most common candidates gently, answers both, and invites them to correct you. "Totally understand. Usually the two things families weigh are the schedule and the cost, so: {Alt class} is also open, and the program is {price}/month with no contract. Would either of those change the picture?"

"Too expensive" gets an honest reframe, never a discount you did not plan to give. Break the month into classes ("that's about {price per class} per class, twice a week, with a coach who knows {Child} by name") and offer a smaller step if you have one: a shorter membership, once a week to start, a family rate you already publish. Keep the discount decision out of the moment: a price you improvise once is a price you have to defend to the next family who hears about it.

Make it a system, not a memory

Scripts only work if they fire every time. The minimum system is a shared note on the front-desk phone with the twelve messages, and a calendar reminder set the moment a trial is booked: day 0, day 1, day 2, day 4, day 7, day 14. Whoever is on the desk sends the message, fills in the blanks, and checks the box.

1. 1Trial request arrives on a phone a human carries, with name, child, program, and preferred day.
2. 2Confirm within 10 minutes. Add the trial to the calendar with the six follow-up reminders.
3. 3During class, the instructor writes one specific observation about the child on a card.
4. 4Front desk sends the same-day text with that observation within two hours.
5. 5The rest of the sequence runs off the reminders. Every reply gets answered within the hour.
6. 6Yes, no, or day 14: close the loop and log the outcome so you can see your trial-to-member rate each month.

If you run member software, check whether it can schedule the reminders for you; automated messaging is a common feature. If you do not, a phone note and a calendar do the job for a school with a few trials a week. Either way, keep two things human: the specific line about the child, and the replies. A message that reads like it was assembled by a system invites the reply it deserves.

One more thing to check: the trial request itself. If your website's form is slow, buried, or asks for ten fields, the sequence never starts, because there is nothing to start it. We build academy sites with the trial offer in the first screen and a short form that emails the request straight to you. See what yours would look like with a free 24-hour preview. Then plug in the scripts.

Questions