Admission season automation: 90 days of enquiries handled by AI

Updated 2026-09-19 · 4 min read · By the Convo360 team

The 90-day admission cycle

Admission season for coaching institutes, schools and edtech businesses typically runs in three phases: early enquiry (parents and students exploring options), active counselling (comparing and deciding), and enrolment (paying and confirming). Each phase needs a different kind of automation, and results day usually creates a sudden spike that breaks flows built only for a steady trickle.

Treating all 90 days as one long enquiry period is the most common mistake. A parent messaging in week one wants general orientation information; the same parent messaging in week eight, close to a deadline, wants a fast, direct answer about seat availability and payment. Building one flow that tries to serve both moods equally usually serves neither well.

The 90-day calendar

Building the FAQ layer

Most early enquiries repeat the same questions: fees, batch timings, faculty, eligibility criteria. Build this as a guided (no-AI) bot using a List Menu for the top questions, backed by an AI Reply step with a knowledge base of your prospectus and FAQ document for anything the menu misses. This combination answers instantly without a counsellor typing the same reply fifty times a day.

Qualifying and routing to a counsellor call

1. On Convo360's Flow Builder, after the FAQ interaction, use Ask a Question to capture course interest, current class or qualification, and preferred batch timing.
2. Add a Condition block to score interest, for example a specific course plus a stated timeline of 'this month' routes to high priority.
3. High-priority leads get an outbound AI voice call or are pushed straight to Save CRM Lead tagged for a human counsellor callback.
4. Lower-priority leads enter a nurture drip sequence with course highlights over the following weeks.

Coaching institutes and schools drawing from smaller towns and semi-urban areas often see enquiries in Hindi or a regional language rather than English. Configuring the FAQ bot and AI Reply step to respond in the language the parent or student writes in, rather than defaulting to English, removes a real barrier during the enquiry stage, when a parent unsure of the language is far more likely to simply message a different institute instead of persisting in English.

Admission decisions for school-age students usually involve a parent managing logistics and payment, and sometimes the student themselves messaging separately about course content or peers. Where both are in touch, tag both numbers under the same lead record in the CRM rather than treating them as two unrelated enquiries, so a counsellor sees the full picture, and fee reminders go to whichever number actually handles payment.

Automating fee reminders without sounding like a collections call

Partial enrolments (registered but fee pending) are common and easy to lose track of manually. A Wait / Delay-based reminder flow, triggered a set number of days after registration, sends a friendly Utility template with a Razorpay payment link, and escalates to a human only after two automated reminders go unanswered.

Enrolment often needs documents, ID proof, previous marksheets, photographs, collected before a seat is confirmed. Rather than asking for these over chat as loose attachments, use a Show Form (web) or WhatsApp Flow native form block to collect them in one structured step, with a clear checklist of what is required. This reduces the back-and-forth of 'please also send your photo' messages that otherwise stretch enrolment out over several days.

Preparing for the results-day surge

The day results are announced (board results, entrance exam results), enquiry volume can multiply overnight. Before that date, test your FAQ flow under the assumption of high concurrent conversations, make sure seat-availability and fee information are current, and add a waitlist capture branch so a full batch does not turn away a lead permanently, it gets a place on next batch's list instead. Reviewing Flow Logs the morning after results day quickly shows which questions the bot could not handle.

Once enrolment closes and batches are finalised, the automation job shifts again: welcome messages with the class schedule, a reminder the day before the first class, and a short orientation FAQ (what to bring, where to report, login details for online batches) sent automatically to everyone in that batch's group. This closes the loop from first enquiry to actually starting classes without a separate manual coordination effort for each new batch.

Measuring the season without guesswork

Track enquiry-to-counselling and counselling-to-enrolment conversion by week, using the CRM pipeline stages you already set up. A slow week for raw enquiries is not automatically a bad week if counselling-to-enrolment conversion stayed steady; a strong enquiry week that produces very few counsellor bookings usually means the qualification questions or FAQ answers are not building enough confidence to move forward. Comparing these two ratios week over week tells you where to focus attention rather than reacting to enquiry volume alone.

Step by step

1. Build the FAQ botSet up a guided menu for top questions with an AI Reply fallback backed by your prospectus.
2. Add lead qualification questionsCapture course interest, current qualification and timeline with Ask a Question.
3. Score and route leadsUse a Condition block to send high-priority enquiries to a counsellor call or CRM tag.
4. Set up fee remindersBuild a Wait / Delay reminder sequence with a payment link for pending fees.
5. Load results-day contentUpdate seat availability, fees and FAQ answers before the results date.
6. Add a waitlist branchCapture leads for a full batch onto a waitlist instead of losing them.
7. Monitor and adjustReview Flow Logs daily during peak days and add missed questions to the FAQ menu.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.