AI Chatbots for Schools in India: What They Can Do and How to Set One Up Safely

An AI chatbot can save a school office hours every week by answering the questions parents ask again and again: admission dates, fee deadlines, bus timings, uniform rules, holiday lists. It works best on the school website and WhatsApp, answering only from the school's own documents, and handing anything sensitive to a person. In a school town like Dehradun, where admission season brings calls from parents across the country, that alone can take a lot of pressure off the front office.

What it should not do is give advice about a specific child, or touch student records, without proper consent and access controls. India's data protection law treats children's data with extra care, so the design has to start from that.

Here's what we'd build, what we'd avoid, and how to start small.

Which questions can a school chatbot handle?

Most of the calls and messages a school office gets fall into a few groups. These are good candidates:

• Admissions: dates, eligibility by age, documents needed, the application process, fee structure for each class.
• Fees: due dates, payment methods, late fee rules, where to get a receipt.
• Transport: routes, pickup points, timings, who to contact about the bus.
• Calendar: holidays, exam schedules, parent-teacher meetings, events.
• Policies: uniform, attendance, leave applications, mobile phone rules.
• Circulars: "What did the last circular about the annual day say?"

All of these have answers already written down somewhere: the prospectus, the website, circulars, the fee notice. The assistant's job is to find the right answer quickly and quote it, in English or Hindi, any time of day.

What should it not do?

Draw the line clearly before building anything:

• No advice about individual students. Marks, behaviour, health or learning needs go to a teacher or counsellor, not a bot.
• No access to student records by default. If you later want "What's my child's fee balance?", that needs a logged-in parent account, proper verification and a deliberate decision, not a public chatbot.
• No guessing. If the answer isn't in the school's documents, it should say so and pass the question to the office.
• No marketing to children. Keep it a service for parents and staff.

How does India's data protection law affect this?

The Digital Personal Data Protection Act, 2023 (the DPDP Act) applies to schools that handle personal data digitally. Two parts matter most here:

• Processing a child's personal data (anyone under 18) needs verifiable consent from a parent or lawful guardian.
• The Act restricts tracking, behavioural monitoring and targeted advertising directed at children.

The detailed rules arrived with the DPDP Rules, 2025, published in November 2025. Most obligations, including Rule 10 on children's data, apply 18 months after notification, which works out to around May 2027 (summary of the Rules). Rule 10 says the school must get verifiable consent from a parent or guardian, which means checking that the person giving consent really is an identifiable adult. DigiLocker and other authorised government platforms can be used for that check. Building for these rules now is far cheaper than retrofitting later.

For a first chatbot, the simplest safe approach is to keep it to public information that needs no personal data at all. Don't ask for a child's name, class or roll number in an open chat. If you add parent-specific features later, build them behind a login with consent recorded, and get advice from your legal counsel on your exact obligations. This post isn't legal advice.

Where should the chatbot live?

Most schools should start with the website, then add WhatsApp once the answers are reliable. On WhatsApp, the cost per message is small: on Meta's rate card effective 1 October 2026, a utility message such as a fee reminder costs ₹0.115 to an Indian number, so a reminder to 800 parents costs about ₹92 plus GST and your provider's fee (Meta pricing). Since 1 October 2026, Meta also charges for ordinary replies to parents who message the school first, but each number gets 1,000 of those free every month and after that they cost the same ₹0.115 each, so 3,000 replies in a month would add about ₹230 plus GST.

How does it give accurate answers?

The trick is to make the assistant answer only from the school's own documents, not from whatever it picked up on the internet. Here's how that works:

1. We collect the school's documents: prospectus, fee notices, transport routes, calendar, policies, recent circulars.
2. These are split into small sections so the assistant can search them in a second.
3. When a parent asks a question, the assistant finds the most relevant sections and answers only from them, with a link to the source.
4. If nothing relevant is found, it says it doesn't know and offers to connect the parent to the office.

The most important part is keeping documents up to date. A bot quoting last year's fee structure does more harm than no bot. So we give the office a simple way to upload new circulars, and the assistant uses them straight away.

How do you know it's ready for parents?

Before launch we write a test set of real questions the office gets, usually 50 to 100, with the correct answers. We run the assistant against them and check every answer. We also include tricky ones: questions about a specific child, questions whose answers aren't in any document, rude messages, and questions in Hindi or mixed Hindi and English. It only goes live when it gets the normal questions right and handles the tricky ones safely.

After launch, someone at the school should read a sample of conversations every week for the first month. That's where you find missing documents and confusing answers.

What would we do for a school?

If a school came to us today, this is the plan we'd suggest:

1. Week 1: list the 30 most common questions from the office phone and WhatsApp, and gather the documents that answer them.
2. Weeks 2 to 3: build a website assistant that answers only from those documents, in English and Hindi, with a "talk to the office" handover.
3. Week 4: test it against real questions, fix gaps, and let a few staff and parents try it.
4. Then: launch on the website, measure which questions it handles, and decide whether to add WhatsApp.

No student data is involved at any point in this plan, which keeps it simple and safe. You can see the kind of AI work we do on our AI development page, and if you're wondering about running costs, our post on what an AI support chatbot costs walks through the numbers.

A checklist for schools

• We've listed the questions the office answers most often
• Every answer comes from a document the school controls
• The bot never asks for a child's personal details in an open chat
• Anything about an individual student goes to a person
• There's a clear "talk to the office" option on every answer
• Someone owns keeping documents up to date
• We tested it on real questions, including Hindi and tricky ones
• We've checked our data protection obligations with legal counsel before adding any personal data, including Rule 10's parental consent requirement

If you run a school and want to talk this through, book a free 30-minute call. We'll tell you honestly whether a chatbot is worth it for your office's volume of questions.