Where Admissions Enquiries Actually Get Lost

A family fills in the enquiry form on a school website on Sunday evening. The form emails the admissions inbox. On Monday the admissions officer is showing three families around and does not open the inbox until four. On Tuesday they reply. By then the family has heard back from two other schools and visited one.

Nothing went wrong in that story. Nobody was negligent. And the school probably lost the enrolment anyway, because in admissions the first credible response has a disproportionate advantage — and a form that lands in a shared inbox has no mechanism to produce one.

Schools tend to respond to soft enrolment numbers by spending more on getting enquiries. It is worth checking the other end first: what proportion of the enquiries you already receive convert to a visit, and how long does the first reply take? Most schools cannot answer either question, which is itself the finding.

There are three places enquiries reliably get lost.

The first is response time. An enquiry that gets a reply within the hour is a different conversation from one that gets a reply on Tuesday. An automatic acknowledgement that confirms receipt, sets an expectation, and offers something concrete — a prospectus, a link to book a tour — holds attention while a human catches up. This is not sophisticated, and its absence is the single most common gap.

The second is the invisible pipeline. If enquiries live in an inbox, nobody can see how many are open, how long each has been waiting, or which have gone quiet. The ones that go quiet are not rejections; they are usually families who meant to reply and did not. A visible pipeline with a stage per applicant turns those from lost causes into a follow-up list.

The third is the handover. A family accepted in March becomes a student in September, and in most schools that transition is a manual re-keying of everything the admissions team already collected — names, dates of birth, contact details, medical notes, previous school. Every field re-typed is a field that can be typed wrong, and the family is often asked for the same information twice, which reads to them as disorganisation at exactly the moment they are deciding whether they made the right choice.

That third one is where an integrated system earns its place. If admissions and student records are the same system, acceptance is a status change rather than a data migration. The medical note the parent uploaded in February is on the student record in September because it never moved.

Some practical things worth doing regardless of tooling. Measure time-to-first-response and treat it as the primary admissions metric — it is the one you control and the one that moves conversion. Write the acknowledgement email so it is genuinely useful rather than a receipt. Define what "gone quiet" means and review that list weekly rather than hoping. And ask, at enrolment, how the family first heard of you, because otherwise you are guessing about the spend at the top of the funnel.

For international schools there is an extra layer: enquiries arriving in several languages, families in other time zones, and documents that need collecting before a visa process can start. A pipeline that cannot record which stage a document is at will lose applicants to paperwork rather than to a competitor.

Skoolia’s admissions module keeps enquiries in a visible pipeline with stages and follow-up prompts, and an accepted applicant becomes a student record without anyone re-typing anything. The communication layer handles the acknowledgement automatically, in the family’s language.

Most schools do not need more enquiries. They need to stop losing the ones they have to a Tuesday.