All modules Admissions & StudentsOptional Aira or AI assistance

Enquiry Management software for Indian schools

Capture and convert leads

Feature identity
Enquiry Management
An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Enquiry Management in a school workflow

Admissions & Students

01
Required context
Admissions stages and assignment rules must be confirmed before rollout.
02
Supported work
6-stage Kanban (New → Contacted → Visit → Application → Admitted/Lost) with live counts and funnel stats.
03
Reviewable result
An owned admissions pipeline from first enquiry through follow-up, application decision and controlled student conversion.

Example record

Enquiry Management

Authorised view

6-stage Kanban (New → Contacted → Visit → Application → Admitted/Lost) with live counts and funnel stats
Public enquiry forms capture leads with duplicate detection and auto-assignment
AI drafts warm follow-up messages — PII-safe: only pipeline context ever reaches the model
“Admit as student” converts a lead atomically, carrying uploaded photos and documents across

Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

A drag-drop admissions CRM: enquiry forms on your public website feed the lead pipeline, stages move through a governed workflow, and one click converts an admitted lead into a real student record. OTP-verified self-registration with an admin approval queue absorbs the admission-season rush.

The school problem

School teams need a dependable way to handle Enquiry Management: Capture and convert leads. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Capture and convert leads.

6-stage Kanban (New → Contacted → Visit → Application → Admitted/Lost) with live counts and funnel stats
Public enquiry forms capture leads with duplicate detection and auto-assignment
AI drafts warm follow-up messages — PII-safe: only pipeline context ever reaches the model
“Admit as student” converts a lead atomically, carrying uploaded photos and documents across

Operational result

What your school gets

An owned admissions pipeline from first enquiry through follow-up, application decision and controlled student conversion.

Access and ownership

Who typically uses it

Admissions counsellor
Front-office executive
Admissions head
Principal

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Admissions & Students catalogue capability

Admissions stages and assignment rules
A plan that includes Aira for optional follow-up drafting
Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Flagship workflow deep dive

Admissions Pipeline & Aira-Assisted Follow-up

Every enquiry gets an owner and a next step.

Bring public enquiries, counsellor follow-ups, applicant registration, documents and final enrolment into one governed pipeline. Teams can see where a family is waiting, while admission decisions and student creation remain authorised human actions.

Interactive operating model

A governed admissions passage

The interactive pipeline shows where information moves and where a human decision remains mandatory.

Illustrative workflow · no customer data

Stage 1 of 6

Enquiry captured

A public, walk-in or phone enquiry enters the school pipeline.

Control point

Rate limits and duplicate flags protect the intake; a flag does not delete or reject a lead.

Evidence retained

Source, class of interest, created time and duplicate-review state.

Core workflows and features

The operational work behind the promise

Six-stage pipelineMove enquiries through New, Contacted, Visit, Application, Admitted or Lost with live stage counts and funnel context.
Public enquiry captureAccept school website enquiries through a rate-limited public path and flag likely duplicates for review.
Source and class contextRetain where an enquiry came from and the class of interest so the team can compare its funnel responsibly.
Counsellor ownershipAssign responsibility, record follow-up history and keep a visible next action rather than relying on a private notebook.
OTP applicant registrationLet an applicant submit a registration through OTP verification before staff review the supplied record.
Review and correction queueAuthorised staff can review, request correction, approve or reject submitted registration information.
Document carry-overKeep eligible applicant photos and documents attached when an admitted lead becomes a student.
Capacity-aware placementCheck the configured class cap and use the least-filled-section hint as decision support, not automatic placement authority.
Atomic lead conversionCreate the student and guardian record with a server-minted admission number and mark the lead converted in one controlled transaction.
Admissions reportingReview current source, stage and conversion counts from the recorded pipeline.

Aira-assisted follow-up

Draft the next message without deciding who gets admitted.

Aira can draft a warm follow-up from bounded pipeline context such as stage, source, class of interest, time since last contact and follow-up count. Names, phone numbers and email addresses are not supplied to this drafting agent.

Prepare a reviewable follow-up draft from the current non-identity pipeline context.
Return the draft to the authorised counsellor without persisting it as completed outreach.
Let the counsellor edit the wording, choose the actual channel and separately record what was sent or discussed.
Keep duplicate flags, seat hints and funnel statistics as decision support for staff review.

Human boundary

Aira does not send the follow-up, score or rank applicants, decide admission, assign a child automatically, or convert a lead. An authorised person reviews the draft and performs every admission-state change.

Key daily uses

What the school team does here

Work today's assigned follow-up queue and record the outcome.
Find enquiries that have remained in one stage without a next step.
Compare current applications and admissions by recorded source.
Request missing or corrected applicant information.
Convert a reviewed and accepted enquiry into a student record.

Used by

Admission counsellor
Admission manager
Front-office executive
Principal
Tenant administrator
Parent or applicant

Actual access follows the school's plan, role permissions and record scope.

Measurable operating indicators

Metrics to track — not guaranteed ROI

Establish a baseline before rollout, agree the reporting period, then compare the school's own source evidence.

Pipeline conversion

Admitted enquiries ÷ eligible recorded enquiries

Review conversion by source and period without presenting it as an AI-generated forecast.

Follow-up discipline

Open enquiries with an owner, next step and recent contact record

Highlights missing operational ownership before a family drops out of the process.

Source effectiveness

Applications and admissions grouped by recorded source

Helps the school compare channel quality using its own funnel evidence.

Prerequisites and availability

Confirm the operating context before rollout.

Admissions catalogue capability · optional Aira follow-up drafting on plans that include it

Confirm admission roles, pipeline definitions, class capacity and the school's acceptance policy.
Public capture and OTP registration require their configured public and messaging paths.
Aira drafting needs the Aira AI assistant included on your plan, a governance precheck and available credits.
Staff must verify applicant data, documents, consent and school policy before conversion.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Does an enquiry automatically become a student?

No. An enquiry moves through the stages your school defines, and admission is a separate, permissioned conversion that creates the student record and assigns the admission number from the school's own allocator.

Can AI chase our enquiries on its own?

No. Where the assistant tier is enabled, Aira can draft follow-up copy for a person to review and send. Stage changes, admission decisions and outbound messages stay human actions under the school's messaging controls.

Does Enquiry Management work on its own?

Student Admission, Front Office, Admission Reports, Website Builder AI are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling Enquiry Management?

Admissions stages and assignment rules. A plan that includes Aira for optional follow-up drafting. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Enquiry Management?

Optional Aira or AI assistance. Aira supports only the reviewed actions listed on this page, and authorised people remain responsible for confirming material actions.

How do we confirm the plan and implementation scope?

Plan inclusion and rollout scope depend on the live plan matrix, readiness state and your school's written proposal. The demo team will confirm the applicable boundary before rollout.

Related evaluation guides

See the Admissions & Students workspace Compare plans and commercial costs

See it in your school context

Run enquiry management the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.