How coaching centres stop losing admission enquiries

The enquiry does not fail. The gap after it does.

Almost nobody loses an admission enquiry at the point it is made. The parent fills in the form, or sends the message, or misses the call back — and the enquiry exists. It is what happens in the next few hours that decides whether it becomes an admission, and in most institutes what happens next is nothing, because the person who would have answered was teaching.

That is the whole problem, and it is worth stating plainly because it changes what the fix has to be. The fix is not a better form and it is not a bigger counselling team. It is that the first answer has to happen without a person being free at that moment, and it has to happen where the parent already is.

Where enquiries actually leak

Four places, in our experience of building for institutes. The enquiry arrives somewhere nobody is watching — a form that mails an inbox, a missed call, a message on a number one person owns. It arrives outside office hours, which for a coaching centre is most of the hours a working parent is free. It arrives in a language the ready-made reply was not written in. And it is answered once and never followed up, because there is no list of who was answered and who was not.

None of those is a strategy problem. All four are the same operational problem seen from different sides: no system owns the enquiry between the moment it arrives and the moment somebody has time for it.

What closing the gap involves

Capture first. Every enquiry lands in one place, whichever door it came in through, and it stays there as a record rather than as a message in somebody’s phone.

Then the first answer, automatically, on WhatsApp — because that is the thread the parent already has open, and because it means the reply arrives at nine in the evening as readily as at eleven in the morning. In Pathshala that reply comes back in Hindi, English or Hinglish, detected from whatever the parent actually typed rather than chosen in advance, and it is drawn only from the institute’s own knowledge base. When the question is about fees or syllabus, it sends the sheet the institute already has, as the PDF it already is, instead of retyping it into a message where it can be got wrong.

Then sorting. Not every enquiry is worth a counsellor’s afternoon, and the ones that are should not be found by scrolling. Lead scoring — hot, warm, cold — is what turns a day of messages into a short list of calls to make.

And then the part that is easy to design away: a person has to be able to take over. The owner sees every conversation live and can step into any of them mid-sentence, at which point the AI stops talking. An institute that cannot interrupt its own automation will not trust it, and an automation nobody trusts gets switched off.

What it should not involve

An app for parents. Anything that asks a parent to install software and remember a password to be told a fee is due has added a step to the one interaction that most needs none.

And it should not involve buying an entire ERP to fix one leak. Pathshala is sold module by module for exactly this reason: an institute that is losing enquiries buys the enquiry module, and adds fees or attendance later if there is a reason to. Nothing is forced into a bundle.

An admission enquiry is not lost when it arrives. It is lost in the hours before anyone answers it — so the first answer has to be automatic, in the parent’s language, in the thread they already have open.