Sports Coaching: The Parent and the Player Both Message You

Two messages arrive under the same reel about your under-14 batch. One says "what are the timings and fees for my son". The other says "sir main join karna chahta hu, main 12 saal ka hu".

Same enquiry. Same trigger word. Same template, if you built it the obvious way. And one of those two people is a child, on a platform with an age floor, having a conversation with a business about their own body.

That is the thing that makes a sports account different from every other coaching account, and it should shape the build before anything about conversion does.

The first decision is who your automation is written to

Most academy templates are written to nobody in particular, which in practice means they are written to a parent — fees, timings, transport, the language of a transaction.

Then a fourteen-year-old reads it. Or a twenty-six-year-old wanting to get back into football reads it. Or a parent of a five-year-old reads it, on a post about the senior batch.

Pick one and write plainly for them. The version that works on most academy accounts is: write to the adult, and never say anything to a child you would not want a parent to read over their shoulder. That single rule removes most of the failure modes below without any clever configuration.

Never automate anything about a body

This is the absolute rule and it is not a matter of tone.

Injury. Pain. Recovery. Whether it is safe to play on something. Whether a child is fit to train. Diet, weight, supplements, growth, "kitne din mein height badhegi". Anything at all that a person describes about how their body is behaving.

These are not questions with a templated answer, they are not questions a language model is in a position to answer, and on a junior account they concern somebody else's child. The automation's job when one arrives is to send nothing and put the message in front of a person.

Coaches who work on the body more broadly will find the fitness version of this list goes further, and much of it transfers directly.

What is genuinely safe to template

A surprising amount, and it is the boring half of the inbox, which is the half you want back.

Which age groups train on which days. Where the ground is and what the nearest landmark is. What the trial process is. Whether kit is provided. Whether there is a girls' batch. Whether they do residential camps. What to bring on the first day. Which languages the coaches speak. Where to see photographs of the facility.

Every one of those is identical for everybody who asks, has no bearing on any individual's body, and is safe to send at eleven at night to whoever typed the word. That is the automation. It is smaller than the tool lists imply and it will still clear most of your inbox.

The public reply is more sensitive here than anywhere

A comment automation posts publicly, under the comment, where the commenter's username sits.

On a junior sports post, that username often belongs to a child, and the public reply associates them by name with a specific age group, at a specific ground, on specific days. Keep the public reply to something completely generic — "sent you a DM" — and never let it repeat the batch, the timing, the venue or anything the person said.

It is worth a second thought about whether the public reply needs to exist at all on posts about children's batches.

Trials, camps and the dated template

Sports accounts run on dates: selection trials, summer camps, a tournament entry deadline, a new batch starting Monday. All of it goes stale, and the reel it hangs off keeps getting found.

The discipline is the same one every launch-shaped business needs. Keep dates out of the template where you can, put them on a page you edit, and where a date must be in the reply, write the switch-off in your calendar the same day you build the automation. "Trials this Sunday" quoted in November is not a small embarrassment on an academy account — it is a family that turned up at an empty ground.

Run the review queue, and run it longer than you think

The review queue holds replies for a person to approve, edit or reject before they go out. Most accounts move past it quickly. An academy should not, because what you are checking is not correctness. It is whether an adult wrote something appropriate to a fourteen-year-old.

Takeover means that the moment any coach replies by hand, automation stands down in that thread permanently. On an account dealing with minors, that boundary — between a supervised conversation and an unsupervised one — should be crossed early and often.

What it will not do, and one thing you must do yourself

It cannot message anybody who has not messaged you first. There is no booking calendar, no payment link, no CRM sync, no WhatsApp, no broadcast, no sequences. Captured people leave as a CSV. It does not publish or schedule content, and there is no analytics product.

Templated replies are free and unlimited, and an academy built the way this post describes will run almost entirely on templates. A credit is spent only when the AI writes a new reply. Free tier is 100 credits with no card, packs start at ₹499.

Two clocks, both the platform's: seven days from each comment, twenty-four hours inside a DM thread, restarted only by their message.

The thing that is yours: your own policy on how the academy communicates with under-18s, written down, known by every coach with the login, and independent of whatever the software is configured to do. Schools face the same problem from the other direction, and what the checks do and do not protect you from is worth reading before you go live.