Artificial intelligence
AI for a private school: what the enrolment window can delegate
For six weeks the same question arrives sixty times a day. A system can answer it — provided it never confirms a place.
A language school in Constantine, the second week of September. The phone rings while three families wait in front of the office. The manager answers, for the fortieth time that day, the same question: Saturday hours, the price of the term, and the papers to bring.
That week decides the year, and the enrolment campaign is run day by day. The question asked here is a different and a new one: inside that window, what can an artificial intelligence system absorb, and what must it not touch?
The answer rests on an asymmetry. The questions repeat and the decisions are irreversible: enrolling somebody, accepting a file, taking a deposit. This article gives the split, the four refusals that come with it, and the fifty-message check that tells you whether automating would do anything for you.
The window does to the phone what it does to the office
Across a school year, demand at a private school is not spread out: it concentrates into a few weeks, and inside those weeks into a few hours. The same office that handled five calls a day in May takes forty in September, with families standing in front of it.
Record one day, changing nothing, and note the question asked on each call. In the schools we have watched, five questions recur: the timetable, the price and what it includes, the documents required, the deadlines, and the level or age accepted.
Those five share one property: their answer already exists, it is stable for the whole window, and it does not depend on who is asking. That is the exact definition of what can be written once and served a thousand times.
What remains after them is the work: a parent hesitating between two formats, an adult asking whether their level is enough, a family negotiating instalments. Those exchanges are not questions, they are decisions, and they need the person holding the office.
Nothing is automated before it is published
The commonest mistake is wiring an answering system onto information that is written down nowhere. The price is known to the management, the timetable is on a printed sheet, the list of documents is in the secretary’s head. The system answers anyway, and what it says is a reconstruction.
The correct order is the reverse and it is free. Publish first, on your own page, the five answers from the previous section; check that they are accurate; only then have them served automatically. Half the schools that do this first step find their telephone traffic drops before any tool is installed.
There is a less obvious benefit and it lasts: published information is dated, can be relied on, and is corrected in one place. Information reconstructed by a model is different every time it is asked for, and you will never know what was said to whom.
The rule that follows holds for everything below: the system serves what exists, it does not manufacture it. A supplier offering to let the model "answer naturally" with no written corpus is offering to let a machine speak for the school.
The price is read, not negotiated
Price is the first question asked, and it is also where automation goes wrong fastest. The system can read the published tariff, say what it includes and what it does not, and name the payment terms as written. That covers the vast majority of calls.
What it does not do: grant a discount, approve instalments, apply a sibling rate, or say that an arrangement "is possible, speak to the management". That last phrase looks prudent and is not: it has already promised that an arrangement exists.
The distinction is sharp because a discount is a commercial decision committing the school for a full year, and sometimes towards a whole family. It is taken knowing the numbers, the group concerned and what has already been granted to others — three things an answering system cannot see.
The practical setting fits in one sentence to write into the corpus: any question about a discount, a payment delay or a special case hands over to a person, with no preliminary comment. No "that may be possible", no "we usually accept".
Record a request for a place, never confirm it
This is the article’s central refusal. A system can collect a name, a desired level, a preferred slot and a contact, and say clearly that the request is recorded and will be handled by the school. It cannot say a place is reserved.
The reason is that the number of places is a physical constraint, not a database field. A group fills up, splits or is cancelled against thresholds, a teacher withdraws, a room is reassigned. A confirmation issued by a system that does not see those constraints creates an enrolment that does not exist.
The consequence is not administrative, it is human and it lands at the worst moment: a family turns up on the first day with a written confirmation, in front of other families, and the school has to explain that the group is full. That is the kind of incident a neighbourhood retells for years.
The wording that protects everybody is short and has to be imposed as it stands: your request is recorded, it is not yet an enrolment, the school will confirm within such a time. The time announced has to be one the office actually keeps, which is an organisational decision before it is a sentence.
The document list, and refusing to judge a file
The system can do two useful things with a file. Give the exact list of documents expected for the chosen format, and acknowledge what has been handed in while naming what is still missing. Both are mechanical and verifiable.
It does not judge the file. Whether a transcript matches the stated level, whether a certificate is acceptable, or whether a student should sit a placement test, is a pedagogical decision. A model taking it produces a fluent answer with no authority, and the school will discover the disagreement in class three weeks later.
The edge case deserves naming because it always comes up: the placement test. A system can offer a test slot, remind that it is required for a given format, and pass on the result entered by a teacher. It does not run the test, does not interpret the mark, and does not announce a placement.
Put another way, the rule is the one running through this whole file: what can be counted, the machine may count; what has to be judged belongs to somebody whose trade that is.
Payment: what the system does not touch
A school automating its answers is quickly tempted to add the deposit, because the deposit is what turns a request into a commitment. It is also what turns a reception tool into a till, with the obligations that come with it.
The split we apply is this. The system says how you pay, where, within what deadlines, and what a deposit commits or does not — because all of that is written. It does not take money, does not issue a receipt, and never says a payment has been recorded: that sentence has to come from the person who saw the cash or the transfer.
There is a specifically local reason for this caution. A significant share of payments is still made in cash at the office or by bank deposit, and matching a deposit to a family is done by hand. A system announcing a payment received before that matching will be wrong regularly, and the error will be about money.
If you keep one boundary from this section: the system talks about payment, it never talks about a payment.
A minor is not a prospect
An enrolment request contains a child’s name and age, often their previous school and level, and a parent’s contact. That is personal data within the meaning of law 18-07 of 10 June 2018, amended and completed by law 25-11 of 24 July 2025, and it concerns somebody who did not give their own consent.
Three practical consequences. Communication goes to the parent or guardian, not the pupil, reminders included: a message sent to a teenager’s number because it appears in the form is a decision nobody took. The list of requests that did not complete is not reused the following year as a commercial file. And the processing has to be described in a register, which the template filled in on a real case shows in one morning.
If the tool relies on a service hosted outside Algeria, the messages and the files go with it, and the transfer regime is looked at before the supplier is chosen, not when a family asks the question.
This paragraph describes the state of a regulation at the date of publication and does not replace a lawyer’s advice. It is here because a school opening an online form in August is processing children’s data from the first day of the window.
Follow-up: three messages, and the day it burns your list
Automatic follow-up works during a short window, and it is also the mechanism most easily set too strong. Three messages are enough, and their content matters more than their number: the first confirms the request, the second recalls a missing document or a deadline, the third says the window is closing.
Each has to carry something new. A message repeating "have you thought about enrolling?" carries nothing, and the family receiving it three times does not think the school is keen: they think it is badly run. Follow-up that works names what is missing on the family’s side or what has changed on the school’s.
The stopping rule matters more than the cadence. Any human reply, any incoming call, any document handed in stops the sequence — otherwise the office is talking to somebody while the system writes them something else. It is the most visible defect from outside, and it destroys exactly the trust the window is meant to build.
We will not put forward a conversion rate for those messages. We have measured none on Algerian schools, and figures published elsewhere describe school systems with neither the same calendar nor the same payment methods.
What the system must hand back to the office every evening
This is the function nobody asks for and that earns its keep the most. At closing, a single page: the requests received that day, those waiting on the school, those with an incomplete file, and the questions the system refused to handle.
That last column is the most valuable, and it is almost always absent from the tools on the market. It holds discount requests, special cases, pedagogical questions — everything that needs a decision. Without it, a handover to a human is not a handover: it is an invisible queue.
The evening page has to be printable, because a school office during the window runs on paper and a notebook does not break down. It is a trivial remark and it is the difference between a tool used in September and a tool abandoned on the third day.
It also serves after closing: it is the only trace saying what families asked this year, in what quantity, and what the school had no written answer for. That is next year’s corpus, assembled for free.
The language of the reply, and the pupil’s name
An Algerian school receives its requests in Arabic and in French, often mixed in the same message, and the reply has to follow the language of the request rather than the software’s. A family writing in Arabic and receiving a confirmation in French will call back to check a date, which cancels the benefit sought.
The pupil’s name is the other point of friction, and it is specific to the country: one name is written several ways in Latin characters, and a system writing the name as it understood it creates two files for one child — then two records, two registers and two reminders. The answer is the one the article on words these systems do not know describes: match against the existing list and flag, never silently correct.
Automatic messages further contain a date, a time and an amount, which are the three things that display badly in Arabic if the template has not been checked. The full list is in the article on what machine-written Arabic breaks.
Those checks take ten minutes on a phone, and they have to be done before the window. During the window nobody will have time to fix a template.
The check: fifty messages, five questions
Take the last fifty messages and calls received during your last window — a notebook is enough, if one was kept — and sort them into two piles only: those whose answer was already written down somewhere, and the rest.
The ratio between the piles is your answer. If two thirds fall in the first, publishing those answers and then serving them automatically will give you back a significant part of the window. If the first pile is thin, your load is made of decisions, and an answering system will not lighten it — it will add an interface to watch at the worst moment of the year.
Add one check, which costs five minutes: in the second pile, count the requests for a discount or for instalments. That is the volume your tool will have to hand back to the office every evening, and it is the best test of a supplier — ask them to show you where that list appears.
Many schools discover at this stage that their real difficulty is not answering but knowing where each family stands. That is not an automatic-reply problem, it is a single-list problem, and it is solved with a table kept by a person.
What we do, and what we refuse
We write the window’s five answers with you, publish them on your page before anything is wired up, then have them served on the channels your families already write to. We put the handover to a person on anything touching a place, a file or a discount, and we deliver the evening page, printable.
We refuse four things, and they are not lifted later: confirming a place, judging a file, taking or announcing a payment, and granting anything on price. A school obtaining those four functions from a supplier would have bought the right to be wrong quickly and in writing.
We promise no gain in enrolments. We have no before-and-after measurement on Algerian schools, and a school that fills its groups does so with its reputation and its former pupils, which the reference article on this trade explains better than we would here.
What you can do without us is the first half of the work and the most profitable: write the five answers, publish them, and keep the evening page by hand for one window. If that is enough, there is nothing to buy — and next year you will know exactly what was missing.
Frequently asked questions
Should this be installed before the window or during it?
Before, with room to spare. A tool wired up during the window gets tuned when nobody has time to tune it, and the first error happens in front of families. If the window is open, write and publish the answers this year, and wire up next year.
Can the system answer on social networks?
Yes, and that is often where requests arrive. The rule does not change: it serves published answers, and hands over to a person for everything else. Watch one detail specific to those channels: a public comment gets a public reply, and a child’s name has no business there.
What about requests arriving after closing?
Record them and say so clearly: the window is closed, here is the date of the next one. It is the simplest case to automate and one of the most useful, because it produces the list you will open the next window with.
Does it replace the person at the desk?
No. What is absorbed is the five repeating questions; what remains — deciding, arbitrating, reassuring, arranging a payment — is precisely what families come in for. A school buying this to remove a post will be disappointed at the moment it most needs somebody.
Our competitors advertise instant answers. Should we match them?
Look at what those answers contain before concluding. An instant reply confirming a place or promising an arrangement creates a problem the school pays for on the first day of term. The useful speed is that of the five written answers, and it requires no promise.
Can we use last year’s list of requests?
To get back in touch with families who approached you, yes, saying who you are and why you are writing, and allowing them to stop. What is not done is treating that list as a prospecting file to be passed on or sold, and doing it in the name of a minor rather than their parent.
Where we come in
The two piles from your notebook say most of it: when the first one wins, the window is relieved by written answers rather than by a tool.
- We draft and publish the window’s answers with you, before a single channel is wired up.
- A seat, a dossier or a reduction leaves the machine at once and reaches a named person, with no holding line that has already promised something.
- Every evening you receive a printable page, and the column of unhandled requests comes first on it.
None of our systems will tell a family that a place is held or that a payment has arrived: those two sentences belong to somebody who has seen the list and the money.
Read next
Schools and training: your year is decided in six weeks
Two enrolment windows decide twelve months. What gets worked on the rest of the time is the next window.The six weeks: running the enrolment campaign day by day
A window is not endured, it is prepared. Most of what decides your year happens before it opens.Training a model: the three cases where it is worth it
Training changes the shape of answers, almost never their content. What you must supply, and the three cases where it is the right tool.
Let us talk about your project
A free audit, no commitment: we look at your online presence and tell you what is holding it back.