Last updated: 18 October 2026 · Published 14 October 2026 · 6 min read
Where enquiries really get lost
Walk into a school office in February and you will often find enquiries living in four places: a register at the reception, WhatsApp messages on the admission coordinator’s phone, a form someone filled at a fair, and a sticky note on a monitor. Nobody is careless. The system simply has no single place for a lead to live.
A school CRM, in plain terms, is that place. Every enquiry gets one record, with the child’s class of interest, the parent’s number, the source, and a trail of what has been said so far. When the coordinator goes on leave, the next person sees exactly where each family stands.
Admission teams also tend to think in funnels without ever measuring one. If sixty families enquire about Nursery and only nine join, the interesting question is where the other fifty-one dropped off: before the campus visit, after the fee quote, or when a neighbouring school called first.
Features that matter, in the order a parent experiences them
1. Capture from every door
A good CRM accepts leads from the school website form, a phone call logged by the front desk, a walk-in, a campaign link and a manual import of a fair’s list. If staff have to retype, they will skip it on busy days. Duplicate detection by phone number matters more than it sounds, since the same mother often calls twice and her husband enquires separately.
2. Follow-up discipline
Look for next-action dates, reminders and a queue that shows “calls due today”. The goal is that a lead who said “call me after the unit tests” gets that call. Templates for WhatsApp and SMS save time, but check that messages go out through a provider you control and that parents can opt out.
3. Visits and assessments
Many schools run campus tours, interaction sessions or entrance tests. The CRM should let you schedule these, mark who attended, and record the outcome, instead of living in a separate sheet.
4. Documents and the move to admission
When a family confirms, the lead should convert into a student record without retyping: name, parents, class, documents and the first fee demand. This single step is where a CRM stops being a call tracker and starts saving real office hours.
5. Reports you will actually read
Source-wise enquiries, conversion by class, average days from enquiry to admission, pending follow-ups per staff member. Four or five numbers are enough.
A short buying checklist
| Question to ask the vendor | Good sign | Warning sign |
|---|---|---|
| Does a lead convert into a student record? | One click, fields carried over | Export, then re-import |
| Can I see who followed up and when? | Activity trail per lead | Only a status dropdown |
| How are web-form leads captured? | Directly into the CRM with source tag | Emailed to someone |
| Can staff work from a phone? | Yes, front desk and coordinator | Desktop only |
| Who can see parents’ contact details? | Role-based access | Everyone with a login |
| What happens to lost leads? | Reason captured, can be reopened next session | Deleted or buried |
Notice that nothing in this table says “AI”. Intelligent scoring can be useful at large scale, but a school with 200 enquiries a season benefits far more from reliable reminders than from a prediction engine.
Fix the process first, or the CRM will only store the chaos
Software cannot decide who calls a parent within a day. Before you buy, agree three rules in writing. First, every enquiry is logged within the same working day, whoever received it. Second, every lead gets a next-action date, even if the date is a month away. Third, one person owns the funnel report and presents it in the weekly staff meeting.
Define your stages in plain words. A typical school list reads: New, Contacted, Visit scheduled, Visited, Application issued, Admitted, Lost. Keep it under eight. Each additional stage is one more click for a tired coordinator.
RTE and reserved seats
If your school admits children under the RTE 25% provision, remember that these admissions come through the state’s allotment process rather than your enquiry funnel. Keep them visible in your admission records, but do not mix them into conversion maths. See RTE admission process and record-keeping for how to handle that side.
Measuring whether the CRM is working
After one admission cycle, compare three numbers with the previous year, even if the previous year came from memory and a register: the share of enquiries contacted within 24 hours, the share that visited the campus, and the share that joined. The first number should move quickly because it depends only on discipline. The others take a cycle to show.
Listen to the staff as well. If the coordinator says she still keeps a private notebook, ask why. The answer usually points to a missing field or a slow screen, and the vendor should be able to fix it during onboarding.
Takshiva’s admission management module covers enquiry tracking, follow-ups and the conversion to a student record, and you can judge it against the checklist above like any other option. Most of what this post describes is about habits, and any tool you choose should be held to them.
Mistakes schools make while choosing
The first mistake is buying for the demo. A vendor can make any CRM look smooth with five prepared leads. Ask to enter ten of your real enquiries from last month, including the messy ones with no email and a parent who gave a different number the second time.
The second is ignoring the front desk. The person who answers the phone at 9 a.m. while also handling visitors is the real user. If logging an enquiry takes more than a minute, she will write it on paper and promise to enter it later. Time the entry of one lead during the trial.
The third is treating the CRM as a marketing tool only. Sending messages is the small part. The larger value is in the discipline of recording what each family said: the fee concern, the sibling already in school, the transfer date. Six months later those notes are what let a coordinator open a conversation with “I remember you were worried about the bus route”.
The fourth is skipping the handover to the student record. A CRM that cannot pass a confirmed family into admission, with documents and the first fee demand, leaves the most boring and error-prone typing exactly where it was.
Frequently asked questions
Is a school CRM different from a normal sales CRM?
Yes in the details. A school CRM understands classes, academic sessions, siblings, documents and the step from lead to enrolled student, which a generic sales tool does not.
How many enquiries make a CRM worthwhile?
If you handle even a few dozen enquiries per session across several staff members, a shared record beats a register. The benefit grows with the number of people involved.
Can the CRM send WhatsApp messages to parents?
Many can, through a messaging provider. Check who holds the account, what the per-message charge is, and whether parents can opt out.
Should enquiry data be deleted after the session ends?
Keep what you need and set a retention rule. Contact details of families who did not join should not be held forever; see our note on the DPDP Act and school data.
