Source: https://oguzerol.com/en/ai-for-educational-institutions/

[![Example scenario: a parent asks about fees, the standard answer goes out at once, and the sibling discount request is passed to the manager.](https://oguzerol.com/gorseller/senaryo/ai-for-educational-institutions-senaryo-en.webp) View full size](https://oguzerol.com/gorseller/senaryo/ai-for-educational-institutions-senaryo-en.webp)

# Custom School Enquiry and Parent Communication App

[Oğuz Erol](https://oguzerol.com/en/about-me/)  |  13 min read  |  Published: 29 July 2026  |  Updated: 30 October 2026

## Key takeaways

- Adult enquiries, campus appointments and team handovers can share a record.
- The scope is adult communication, excluding sensitive student data and student assessment.
- An AI helper using approved information does not decide admissions or scholarships.

If enquiries remain in forms, meeting notes live in spreadsheets and parent conversations sit on different phones, I can develop a custom web application for your admissions team and school leadership. From an adult’s initial enquiry to a visit appointment, task handover and confirmed registration status, the process can stay connected to its owners and sources.

This is a development service tailored to private schools and school groups. The application can work alongside your existing student information system. Its priority is organising enquiries and communication with adults, reducing lost information between teams and showing leadership which tasks remain open. It does not delegate children’s educational, health or admission decisions to AI.

## Help different teams give the same family consistent information

A parent completes a campus-visit form and later asks a question on WhatsApp. Reception opens the conversation while admissions calls back from another list. If the date changes, an old reminder may still run or the meeting owner may miss the change. The issue is knowing together which information is current.

The proposed application connects the enquiry owner, meeting time, adult contact and next task. A team member can continue without asking a question a colleague has already answered. The principal can see which enquiry is waiting, why it is waiting and who owns the response.

Detailed student information is not required for every initial enquiry. We can start with the relevant campus, educational stage, communication preference and meeting need. This scope uses adult communication and task records; sensitive student information, health files and educational assessments are excluded.

## Example workflow: from a campus-visit request to registration confirmation

This is an illustrative workflow, not a record involving real parents, students or school results. An adult requests a campus visit through the school’s website. An admissions colleague responds, arranges an appropriate meeting and passes the next tasks to the relevant team.

| Stage | Record created | Owner and outcome |
| --- | --- | --- |
| Enquiry | Campus, educational stage and adult’s contact preference | A new task reaches admissions |
| First reply | Questions and approved school information | The authorised team uses the right content |
| Appointment | Date, location and meeting owner | Calendar and reminder update together |
| Meeting | Necessary brief notes and next action | The relevant team takes ownership |
| Missing step | Outstanding document or adult confirmation | An authorised colleague follows completion |
| Registration confirmation | Status from an authorised person or system | The enquiry receives a confirmed status |
| Operational handover | Adult contact preferences and open tasks | The authorised school team takes over with limited access |

A completed meeting does not mean that a student has been admitted or registration finalised. These remain separate states. Cancelling an appointment should cancel its reminder, and a new message should not silently move a closed enquiry to another campus.

## School CRM organises adult communication and task handovers

In this context, CRM is the organisation of communication with adult enquirers. It is not a system for scoring families. One person may have separate enquiries for different campuses or academic years. Keeping the contact and enquiry records distinct preserves that history.

Two enquiries using the same phone number do not automatically represent one student. A family may have more than one child, different contacts or changed guardian permissions. The system can suggest a possible duplicate, but an authorised person checks the source before merging anything.

When an enquiry changes campus, the new task owner and reason for handover stay visible. The aim is to keep incoming communication from being lost; it does not require everyone to access every family’s records. Historical retention and access also follow the school’s defined purposes and obligations.

## Ten screens shaped around the school team

| Screen | Daily work it supports |
| --- | --- |
| Enquiry desk | Review new adult enquiries by campus and owner |
| Meeting calendar | Arrange visits, introductory meetings and callbacks |
| Enquiry record | Keep the source, contact preference and next step together |
| Team inbox | Connect a WhatsApp conversation to the enquiry and colleague |
| Approved information library | Use versioned programme, transport and visit information |
| Tasks and handovers | See who is waiting for a reply or confirmation |
| Document completion | Show a required document task to the authorised team |
| Campus management view | Review open enquiries, appointments and errors |
| Communication preferences | Check channels, permission, opt-outs and message history |
| Import and access history | Inspect file uploads, data changes and permission activity |

Teachers do not need the whole enquiry history. If a teacher meeting is arranged, the appointment and necessary approved context can be shared. Finance also receives only the confirmation needed for its task; access to educational notes is not assumed.

## Leadership, admissions and adult contacts need different access

| Role | Example access | Boundary |
| --- | --- | --- |
| School group leader | Process reports for authorised campuses | Unnecessary bulk disclosure of personal details |
| Principal | Open work and authorised records for their campus | Unrestricted family archives from other campuses |
| Admissions adviser | Assigned adult enquiries and meetings | Student health or specialist support files |
| Reception | Visit times, contact preferences and routing | Financial and educational detail |
| Finance colleague | Relevant payment or registration confirmation from an authorised source | Default access to every conversation note |
| Authorised adult | Time-limited link and information for their enquiry | Other adults’ or children’s records |

Knowing a name or phone number does not establish authority to access information about a child. The school’s identity and authority checks become part of the design. Changed guardian access, shared links and departing staff all need a revocation process.

Downloads and sensitive record access can be logged. Permission testing includes opening a direct link, not simply hiding a screen in a menu. Avoiding unnecessary student data at collection is a stronger starting point than managing excessive access later.

## Six practical school workflows for WhatsApp and SMS

Checked 30 October 2026: outside the 24-hour service window following the latest user message, WhatsApp Business Platform requires approved message templates. [WhatsApp policy](https://business.whatsapp.com/policy).

| Trigger | Recipient | Condition and stop rule |
| --- | --- | --- |
| New enquiry acknowledged | The adult who made the enquiry | Correct record and reply channel |
| Campus visit approaching | The adult appointment holder | Appointment still valid; no duplicate reminder |
| Appointment changed | Relevant adult and internal colleague | Cancel the old reminder and confirm the new time |
| Follow-up information ready | The authorised adult | Staff-approved content and correct enquiry |
| Document-completion task opened | The authorised adult | Secure link, appropriate stage and access check |
| Campus event promotion | Adults with appropriate permission | Marketing permission, opt-out status and purpose |

An appointment message and a promotional message have different purposes. Opt-outs and channel preferences stay on record; importing a file again must not reopen withdrawn permission. Contact changes are checked to reduce misdirected messages. Unnecessary child information and sensitive attachments stay out of messages.

An official WhatsApp Business Platform connection follows permission and template requirements, including approved templates outside the service window following the adult’s last message. SMS is planned through an authorised provider with appropriate permission and opt-out controls. Turkish commercial-message and İYS requirements are assessed where applicable, using the [WhatsApp policy](https://business.whatsapp.com/policy) and [İYS guidance](https://iys.org.tr/iys/sss).

## AI can find school information without judging an application

AI can draft replies from an approved school information library, summarise adult conversations into tasks or identify unanswered questions in a long exchange. The source and its update date can remain visible. Capacity, fee or programme information missing from the source must not be invented.

For example, a transport question can produce a draft based only on the source approved for the relevant campus. Old information or a question requiring individual judgement goes to an authorised colleague. In an initial release, outward replies can remain subject to human review.

This scope excludes student admission scoring, inferred suitability based on family income, behavioural or health classification, scholarship decisions and automated adverse decisions about students. Children’s messages and private files are not placed in a general AI knowledge pool. Communication assistance remains separate from educational judgement.

## Data boundaries for parent communication

The initial form collects necessary fields such as adult contact details, campus and meeting needs. Each field has an identified purpose, audience and retention period. Student identity documents, health files, sensitive information and educational assessments are outside this application’s scope.

Final registration stays in the authorised school system. Where needed, this application uses only the enquiry reference and confirmed status instead of duplicating sensitive document archives. Management reports use process totals; correction or deletion requests can be assigned to the responsible person.

## Migrate old enquiry spreadsheets with controlled checks

Before import, we identify the file owner, academic year, campus, status definitions and source of communication permissions. A cell marked “contacted” might mean a call was made, a meeting happened or registration finished. That ambiguity must be resolved rather than becoming a definitive status in the new application.

An import preview shows rows, errors and possible duplicates. Similar phone numbers or emails create candidates for review; separate enquiries within one family remain distinct. Re-uploading the same file should not create fresh enquiries and fresh messages.

Source row counts and campus and status totals are compared against imported records. Missing permission evidence does not initiate promotional messaging. The admissions data owner approves the migration, and we agree when the old file becomes an archive and where future corrections are made.

## Connect the website, advertising and existing school systems

An adult’s web enquiry can reach the admissions team with its campus and topic. Advertising-source information can be connected under the necessary measurement and permission conditions. Leadership can then assess the needs behind enquiries as well as the number of submitted forms.

Controlled CSV exchange may be the first connection to existing school software. If an API exists, access, contractual conditions and available fields need verification. Reading enquiry status and changing a student record are different actions. A write connection requires explicit authority, approvals, duplicate checks and confirmation of the receiving system’s result.

I do not promise ready-made connections to every student information, payment or public-sector system. Failures and the last successful update remain visible. If final registration confirmation is stale, the application must not present the enquiry as completed.

## A principal’s report should explain why work is waiting

Reports can show enquiries, scheduled and completed meetings, adult requests awaiting replies, incomplete steps and handovers by campus, academic year and educational stage. Enquiry sources and task ownership can help organise team workload.

Definitions matter. Two campus requests from the same adult are not the same as two different families. Meetings, enquiries and confirmed registrations are measured separately. Missing historical information should show which comparisons it affects.

These reports do not rank students by value or automatically penalise employees. Numbers support judgement; interpretation remains with leadership. Results based on stale data, import failures or unconfirmed records are marked accordingly.

## Paid scoping, a campus pilot and practical training

In the initial paid scope, I map admissions tasks, files, communication channels and access boundaries. Real child information is unnecessary; anonymised examples are sufficient. Pricing and timing follow the agreed work.

A pilot can focus on one campus and one enquiry flow. Alongside daily work, the team tries appointment changes, withdrawn permission and incorrect record matches. Report totals are compared with existing sources before use expands across campuses.

Training follows each role. Support responsibilities cover access removal, information-library updates, backup and restoration, provider failures and transitions between academic years. We separately define which records carry into a new year.

## Acceptance scenarios to test together

- One adult’s enquiries for different campuses remain separate while duplicate contacts go to review.
- Changing an appointment prevents a reminder for the old time.
- A colleague at another campus cannot open unauthorised enquiry detail.
- A new import cannot reverse a communication opt-out.
- AI cannot confidently supply fees or capacity absent from the source.
- Stale registration confirmation leaves the status visibly pending.
- A revoked document link cannot be reused.
- A repeated event or retry cannot produce a second notification.

## When this application may not be necessary

If your current school software already meets your enquiry, team-inbox and permission needs, better configuration may be the right first step. A small volume of requests managed consistently by one person may not justify extensive custom development.

Where admissions, reception and leadership responsibilities remain unclear, the process needs agreement first. A useful starting point for custom development is a recurring, specific problem, sources with identifiable owners and a team willing to run the pilot.

## Frequently Asked Questions

### Do we need to replace our student information system?

Usually not. Enquiries and adult communication can be managed separately, with necessary statuses read from the existing system. Connection access is verified separately.

### Can several campuses share the application?

Campus-specific records, permissions and handovers can be designed. Central reporting and campus staff access do not need to expose the same level of detail.

### Will AI decide which students are admitted?

No. AI assists communication from approved information and summarises tasks. Admissions, scholarships, educational assessment and adverse decisions remain with authorised people.

### Can we send parents bulk WhatsApp or SMS messages?

That depends on recipient authority, purpose, channel rules and appropriate permission and opt-out checks. Submitting an enquiry is not unlimited permission for promotion.

### What if our old spreadsheets contain no permission records?

The field remains unknown rather than being treated as consent. Import and promotional messaging are assessed separately, and an appropriate process is defined with the school.

### What should we share at the start?

Your campus structure, team roles, current systems and the enquiry step that most often stalls are enough. You do not need to send real child information, health documents or parent lists.

## Describe your school’s enquiry and communication workflow

Your scope enquiry can explain which teams are involved, where requests arrive and where they get stuck. Through paid scoping, we can define the screens, data boundaries, connection requirements and acceptance scenarios for a development plan suited to your school.

This application covers adult enquiries and parent communication. Student health records, sensitive student information and student assessments are outside this scope.

[Describe your workflow for a scoping engagement](https://oguzerol.com/en/contact/).

[Back to top ↑](https://oguzerol.com/en/ai-for-educational-institutions/#icerik)
