Key takeaways
- Families compare several schools at once, and the first to answer with a clear visit date often wins the seat.
- Most lost enquiries are not refused. They go quiet after a promised callback or fee sheet never arrives.
- GeniOS reads the enquiry sheet, email, chat and tour calendar together and names the enquiry that needs a person today.
- Agents can draft tour invites and fee emails, but nothing reaches a family until a person approves it.
The problem
Admissions season is a flood. Between January and April a mid-sized school or college can take sixty enquiries a day from the website form, phone calls, education fairs, walk-ins, email and chat. A few counsellors answer them while running open days and campus tours. Every conversation ends with a promise: "I will send the fee structure tonight", "Let me check hostel rooms and call you back", "The principal will confirm the scholarship by Thursday".
Picture a normal Monday. Neha, a counsellor, has 42 open enquiries and three tours booked. On Friday a parent asked whether her daughter can visit before the 20th and what the merit scholarship covers. Neha replied on chat that she would call back. Over the weekend two fairs brought in 80 new names, and the callback never happens. The parent does not complain. She books a visit at another college that replied on Saturday with a time slot and a fee sheet.
Nobody sees this as a loss. The enquiry stays in the sheet as "Contacted". At the end of the season the intake is 30 seats short, and nobody can say where those families went.
Why it slips today
Schools already have admissions tools. Each holds one piece of the story, and the promise that matters sits between them.
| Where it lives | Who sees it | How it slips |
|---|---|---|
| Enquiry sheet or admissions CRM | The admissions office | Status stays "Contacted" while the real conversation moves to phone and chat |
| A counsellor's chat | One counsellor | A callback is promised and never logged |
| Email about fees, hostel or scholarship | Whoever opened it | The answer waits on finance or the principal |
| Open day sign-up list | The events team | Attendees never get a personal next step |
A dashboard counts enquiries by source. It cannot tell you that the Rao family was promised a call on Friday and did not get one. A weekly review catches it days late. And the people who answer the hard questions, like finance on scholarships, sit outside admissions and never see the clock running.
The solution
GeniOS reads where admissions work happens, read-only to start: the admissions inbox, counsellors' chat, the enquiry sheet or CRM, the tour calendar and the intake plan. When an enquiry needs a person, it sends one piece of intelligence with the situation, what to do, why, one owner and a date.
- Enquiries going cold. Families who asked a question or requested a visit and have heard nothing for longer than your normal reply time.
- Promises made to families. Callbacks, fee sheets, tour slots and scholarship answers, followed until there is proof they were kept.
- Answers stuck inside the school. Questions waiting on finance, the principal, transport or the hostel, with the person who must answer named.
- Intake pace against the goal. A programme trailing its seat target, so effort goes where seats are still open.
It is Relationship & Opportunity Intelligence applied to families deciding where their child will study.
See it on the whiteboard
One enquiry moving through GeniOS, from three scattered messages to a booked tour and a goal that moves.
The Rao family is still waiting for a tour
How: call today, offer Saturday's campus tour and send the fee sheet before the 20th.
- Your tools. A parent asks for a visit, a counsellor promises a callback in chat, and the sheet still says "New" six days later.
- GeniOS thinks. It reads the three together: what happened, the pattern, the family's deadline and who owns the enquiry.
- Intelligence. Anita, the Admissions Head, gets one note: the Raos are still waiting, and a tour and fee sheet should reach them before the 20th.
- Delegated. Anita hands the tour invite to a Scheduler agent. Nothing is sent until she approves.
- Goal moves. The tour is booked and the family pays the deposit. GeniOS sees the proof and the design intake moves forward.
How GeniOS thinks and plans
GeniOS starts from the school's own goals, formed from the intake plan, the principal's emails and the admissions review deck: for example, fill 240 first-year seats, with 60 in the new design programme. Every open enquiry is checked against that goal, so an enquiry for a full programme is treated differently from one for a programme that is short.
For each enquiry it connects four pieces. What happened: the family asked for a visit and fee details on Friday. The pattern: a callback was promised in chat, but nothing followed, and this counsellor has eleven other promises open. The impact: the parent mentioned another college's deposit deadline on the 20th. The owner: Neha owns the enquiry but is overloaded, so the note goes to Anita, who can reassign it.
Then it picks one next step: a call today with a Saturday tour slot and the fee sheet, before the 20th. If the scholarship answer is the real blocker, the step goes to finance instead, with the date the family needs it. It is the discipline of Goal & Execution Monitoring: every step tied to a goal, an owner and a date.
How it delegates and gets it done
The owner answers with Delegate, Done, Later or Not relevant. Delegate hands the work to a person or an AI agent: another counsellor with fewer open enquiries, a Scheduler that proposes three tour slots, or a Reply Drafter that writes the fee email in the school's usual tone.
Nothing goes to a family until a person approves it, which matters when a wrong fee figure or a careless scholarship promise causes trouble later. See human in the loop vs human on the loop.
An item closes only on proof: the booking in the calendar, the fee email in the sent folder, the status change in the CRM. Then the intake goal moves. GeniOS learns from each outcome. If families offered a tour within a day visit more often, it raises cold enquiries sooner. If scholarship questions always wait on finance, it routes them there on day one.
How it reaches you
Intelligence arrives on its own in the GeniOS Mac app, from the menu bar, and on the web dashboard. Most days an admissions head sees a handful of notes, each about one family or one stuck answer.
You no longer chase counsellors for updates, read a weekly conversion report to guess where families are lost, or decide which of 300 open enquiries to look at first. Nobody tags anything or writes a prompt.
A worked example
The college, names, dates and numbers in this example are made up to explain the idea.
A 3,000-student private college in Hyderabad has 240 first-year seats across business and design, at about $4,200 a year. In early March the design programme has 34 confirmed students against a target of 60.
On Friday 6 March Mrs Rao emails asking to see the design studios before the 20th, and what the merit scholarship covers. Neha replies on chat that she will call on Monday, but on Monday she is at a fair. The scholarship rules sit with Suresh in finance, who has not answered two earlier emails on the same question. By Thursday the sheet still says "New".
That Thursday Anita gets one note. The Rao enquiry is for design, 26 seats short; the family was promised a call six days ago; and another college's deposit deadline is the 20th. Nine other design enquiries wait on the same scholarship answer.
Anita delegates the scholarship answer to Suresh by Friday noon and the tour invite to the Scheduler, approving a Saturday 10:00 slot with the fee sheet. Suresh confirms on Friday, and a Reply Drafter prepares the answer for all ten families, which Anita approves. The Raos visit on Saturday and pay the $500 deposit on the 14th. GeniOS closes the item on the deposit record, and design moves to 35. One student is worth about $12,600 over three years.
How to measure it
- Hours from enquiry to first real reply, not counting automatic acknowledgements.
- Share of promised callbacks closed with proof: a logged call, sent email or booked tour.
- Enquiry-to-visit rate by programme, especially those short of their seat target.
- Enquiries waiting on an internal answer for more than two days.
Where it applies
These are application areas, not current deployments: schools, colleges, coaching institutes and online course providers, wherever learners ask before they commit.
- Domains: Sales, Marketing, Administration, Finance
- Industries: Education & EdTech
- Roles: Founders, Executives, Managers
Questions about admissions follow-up
Does GeniOS contact parents on its own?
No. It drafts tour invites and replies only when an owner delegates the work, and nothing is sent until a person approves it.
We already use an admissions CRM. Why add GeniOS?
The CRM holds what counsellors remember to log. GeniOS reads it alongside email, chat and the tour calendar, so it sees promises that were never logged.
How does it decide which enquiry matters most?
It weighs the intake goal, the family's own deadline and how long they have waited. An enquiry for a programme short of seats, with a deposit deadline near, comes first.
What about family privacy?
GeniOS reads only the sources you choose, read-only to start. Each note shows only what the owner needs to act.
Status
Exploring This is an application area we are exploring with early customers. If slow follow-up is costing your school seats, book a call and we will show how it would work on your own enquiries, starting read-only.