Compliance · 6 min read
Instagram Automation for Schools: Never Automate the Fees
Schools, colleges and coaching institutes get a particular kind of Instagram inbox. It is seasonal, it spikes hard, and almost every message in it is somebody making a decision that will cost them a year of their life and a large amount of money.
That combination is why the automation advice here is narrower than it is anywhere else on this blog. The volume genuinely justifies automation. What the messages are about mostly does not.
The list that never gets automated
Write these down before you build anything, because the pressure to include them arrives during admissions season when everyone is tired.
Fee structures. Not the total, not the instalment plan, not the hostel component, not "roughly around". Fees vary by category, by year, by stream, by quota, and a figure sent instantly by your official account is a figure a parent will screenshot and hold you to. If it changed last month, the automation does not know.
Eligibility. Whether this student, with these marks, from this board, qualifies. That is an assessment. A keyword match is not making it.
Admission decisions, in any form. Including the softened versions: "you have a good chance", "students like you usually get in", "seats are still open for your category". Each of those is a statement someone will act on.
Cut-offs, merit lists, seat availability, scholarship amounts, placement figures. All of these are numbers that move, and several of them are numbers a regulator has opinions about how you present.
Anything about a specific child. Their marks, their application, their interview, their conduct.
The other reason to be careful: who is writing
A meaningful share of the messages a school account receives are from people under eighteen, or from a parent writing about someone under eighteen. Often you cannot tell which from the message.
That changes a few things that are otherwise routine.
Capture less. The lead record holds who asked, on which post, which keyword matched, and when. That is enough. Do not build a flow that asks a sixteen-year-old for a phone number, an address, a date of birth or a marksheet in a DM. If you need those, they belong on your own application form with whatever consent your institution already uses there.
Drop the persuasion techniques. Scarcity language, countdowns, "only a few seats left", pressure to decide today. Those are standard commercial tactics and they are inappropriate aimed at a teenager choosing a college.
No payment links. Nothing here processes a payment and nothing should ask for one in a DM.
Know that the lead row is a different kind of record. A CSV of prospective students is a file about children. Treat its storage, access and retention accordingly; the data privacy post covers the general shape of what is and is not stored.
What is safe, and it is a real list
The safe answers share one property: they are administrative, identical for everyone, and already published somewhere you control.
Where the campus is and how to get there. What the visiting hours are. How to book a campus visit. Which dates the term or the batch begins, if those are already announced. Where the prospectus or the syllabus PDF lives. Which documents the application asks for. Which languages the course is taught in. The admissions office's phone number and email, and when it is staffed.
That is enough to absorb most of the season's volume, because most of the season's volume is people who could not find the prospectus.
The automation's job at a school is not to answer the question. It is to get the person to a named human quickly and without a stale number attached.
Building it so it defaults to silence
Invert the usual posture. Instead of replying to everything except a blocklist, reply to nothing except a short list of situations you decided were safe.
- Scope to specific posts. The admissions-open post, the campus tour post. Not the whole account. Advanced settings let you restrict which posts an automation applies to, and here you should.
- Trigger on a word you asked for in the caption. "Comment PROSPECTUS and we will DM it." A word typed on purpose, not a broad any-of list that catches a sentence someone wrote in worry.
- Put the whole no-automation list into negative keywords.
fees,fee,scholarship,cut off,cutoff,eligibility,admission,marks,percentage,refund,complaint,hostel. Yes, this blocks a lot. That is the intent. - Route, do not resolve. Every safe reply ends with the admissions office contact and when it is open.
- Test it on yourself first. The whole pipeline runs and lands in your own account, so you read it as a parent would.
Language, and the thing that will trip you
Enquiries arrive in Hindi, in Hinglish and in the regional language of wherever you are. Matching folds case and punctuation, and it folds Latin accents. It does not fold Indic vowel signs, so a Devanagari keyword matches exactly the letters you typed and nothing near it.
Practically: list the Roman spellings people actually use alongside any script keyword, and list more of them than feels necessary. The localisation post has the longer treatment.
The clocks, in an admissions season
A comment can be replied to for seven days. A DM thread is open for twenty-four hours, restarting only when they write. There is no reminder, no follow-up nudge, no deadline sequence — the platform does not permit it and this product does not have sequences or broadcasts regardless. Application deadline reminders are email and phone calls, as they always were.
Takeover means the moment a counsellor replies by hand, the automation stands down in that thread. On a school account that should happen early and often.
What this does not do
No CRM sync — leads export as a CSV. No application processing, no document collection, no fee payment, no calendar or scheduling integration, so nothing here can confirm a campus visit. No WhatsApp. No analytics. No scheduling or publishing. Official Instagram Graph API only.
Templated replies are free and unlimited, and a credit is spent only when the AI writes a new reply. On an account built the way this post describes, the AI writes almost nothing, which is the correct configuration. Free tier is 100 credits with no card, packs from ₹499.
And running no automation at all is a legitimate answer. If nobody will read Activity weekly during admissions season and re-check the templates when the fee circular changes, off is the right setting. The checks explain what would have stopped a send, and the healthcare version of this line is the closest neighbour on the blog.
