CRMAdmissions & enrolment

Education CRM

The admission season, run as a system.

Enquiry capture across every channel, counsellor allocation and follow-up cadence, application and document tracking against the seat matrix, fee-linked conversion, and campaign attribution measured on students who enrolled and stayed — not on leads generated. Hands the enrolled student to the ERP registry without re-entry.

Request a working demoJump to the module ledger
SpecificationCRM
Modules
8
Cycle
Enquiry → application → offer → enrolled
Channels
Web · call · walk-in · WhatsApp · campaign · referral
Conversion event
Fee paid, not form submitted
Handover
Enrolled record created in the ERP registry
Attribution
Source carried through to retention

Built for

  • Schools running an admission window
  • Colleges and universities
  • Coaching institutes and chains
  • Online and hybrid programme providers
  • Multi-campus groups and franchise networks

§ 01

Why a general CRM struggles here

An admissions funnel looks like a sales funnel and behaves like a queue with a deadline. The season is short and non-negotiable, so a lead that goes cold for four days in March is not a lead that will convert in June — it is a student now enrolled somewhere else. Speed of first contact matters more here than in almost any other funnel, and it is the metric most institutions do not measure.

The middle of the funnel is unlike sales too. Between interest and enrolment sits a documentation stage — certificates, category proof, previous marksheets, transfer certificates — where an application stalls not because the family is undecided but because one document has not arrived. A pipeline that models this as a probability-weighted deal stage tells you nothing useful. What is needed is a checklist per applicant and a chase against the missing item.

And the conversion event is a payment against a seat, not a signature. Seats are finite per programme, category, and section; a quota seat cannot be sold to a general applicant; a waitlist has to move in an order that will be defended if questioned. General CRMs have no concept of a seat matrix, which is why institutions using one end up running the actual admission on a spreadsheet beside it — and that spreadsheet, not the CRM, becomes the truth.

§ 02

Module ledger

Built around the admission cycle rather than a generic pipeline. Every stage below has a real gate — a document, a seat, or a payment.

01

Enquiry capture

Every way an enquiry can reach the institution, landing in one queue with its source intact.

  • Website and landing-page forms with UTM and campaign capture
  • Meta and Google lead-form ingestion
  • Call tracking with recordings attached to the enquiry
  • WhatsApp Business API conversations threaded to the record
  • Walk-in and seminar capture on a tablet, offline-tolerant
  • Referral capture with the referring student or parent recorded
  • Duplicate detection across channels — one family, one record
02

Allocation & response time

Who owns this enquiry, and how long did it take to reach them. The single highest-leverage number in the whole funnel.

  • Round-robin, load-based, or rule-based counsellor allocation
  • Programme, language, and region routing rules
  • First-response SLA with escalation when it is breached
  • Reassignment on leave, exit, or overload, with history retained
  • Response-time reporting per counsellor and per source
03

Follow-up cadence

The discipline layer. A cadence the counsellor works from, rather than a list they remember to open.

  • Sequenced tasks per stage with due dates and reminders
  • Call, WhatsApp, email, and visit logged against the enquiry
  • Templates with approval so outbound messaging stays consistent
  • Automatic no-contact escalation to the branch or admissions head
  • Snooze with reason, and mandatory next action before closing a call
  • Lost-reason capture — fee, distance, competitor, timing, no response
04

Counselling & campus visit

The conversations and visits that actually decide it, recorded so a handover does not lose the thread.

  • Counselling session notes with structured fields, not free text only
  • Campus visit, demo class, and open-day scheduling with attendance
  • Interest profile — programme, budget band, distance, hostel, transport
  • Parent and student recorded as distinct contacts on one record
  • Full interaction history visible to whoever picks the record up next
05

Application & document verification

The stage where applications actually stall. Modelled as a checklist against the applicant, with a chase on the missing item.

  • Online application form configured per programme
  • Document checklist per category, quota, and programme
  • Upload, verification queue, and rejection with a reason the family sees
  • Automatic chase on the specific missing document, not a generic reminder
  • Eligibility check against qualification, marks, and age criteria
  • Entrance test or interview scheduling with scores recorded
06

Seat matrix, offers & waitlist

Finite seats, allocated under rules that must be defensible if a family or a regulator asks.

  • Seat matrix by programme, section, category, and quota
  • Merit list generation on configured criteria with tie-break rules
  • Offer issuance with an acceptance deadline and automatic lapse
  • Waitlist movement in a recorded order as seats free up
  • Provisional admission pending a result, converted or lapsed on a date
  • Live seat position visible to the admissions head, never over-allotted
07

Fee-linked conversion & handover

The conversion event is money against a seat. The moment it lands, the applicant becomes a student record without anyone re-typing anything.

  • Payment link per offer, tied to the specific seat held
  • Part payment, instalment plan, and concession applied at admission
  • Seat released automatically if payment lapses past the deadline
  • Student record created in the ERP registry with documents carried over
  • Cancellation and refund processed by rule, with the trail retained
08

Attribution & season analytics

What the marketing budget actually bought — measured at enrolment and at retention, not at lead generation.

  • Cost per enquiry, per application, per admission, and per retained student
  • Source and campaign performance with conversion at each stage
  • Counsellor performance on response time, conversion, and quality
  • Funnel drop-off by stage with the reason distribution
  • Season-on-season comparison at the same point in the cycle
  • Geographic and feeder-school analysis for next season's planning

§ 03

One admission, start to finish

Every arrow below is a system event with an owner and a clock. None of them is an email someone remembers to send.

  1. 01

    Enquiry lands

    Captured from any channel with source, campaign, and referrer attached. Duplicates merged so a family that called and also filled the form is one record.

  2. 02

    Allocated

    Routed to a counsellor by rule within seconds, with a first-response SLA started and an escalation waiting if it is breached.

  3. 03

    Contacted & qualified

    First call logged, interest profile captured, programme and budget band recorded, and the follow-up cadence started from the correct stage.

  4. 04

    Visit or demo

    Campus visit or demo class scheduled and attendance recorded — the strongest single predictor of conversion, and therefore worth measuring.

  5. 05

    Application

    Form submitted, documents uploaded against the checklist, verification queue worked, and the chase running on whatever is specifically missing.

  6. 06

    Offer

    Eligibility confirmed, seat held against the matrix, offer issued with an acceptance deadline that lapses automatically if it passes.

  7. 07

    Enrolled

    Fee paid against the held seat. The applicant becomes a student in the ERP registry with documents and history carried across intact.

  8. 08

    Attributed

    Source cost measured against this enrolment — and again after the next fee instalment, which is when the number becomes worth acting on.

§ 04

Who sees what

Pipeline data is competitive and personal at the same time. A counsellor sees their own; nobody sees another counsellor's conversations without a reason.

Who sees what
RoleCan seeCan do
CounsellorOwn allocated enquiries, tasks, conversations, and conversion numbersLog calls and visits, move stages, request documents, issue offers within authority
Admissions headThe whole funnel, seat matrix position, response times, and counsellor performanceSet allocation rules and cadences, approve offers and concessions above threshold, move waitlists
Verification deskDocuments pending verification across all applicants, with the checklist per categoryVerify or reject with a reason, request re-upload, confirm eligibility
MarketingSource, campaign, and cost data with stage-wise conversion — not individual conversationsConfigure campaigns and tracking, analyse attribution, plan spend
AccountsAdmission payments, concessions applied, refunds, and reconciliationConfirm receipts, process refunds by policy, reconcile against the bank
ManagementSeason dashboards across every campus, with drill-down to any enquirySet seat matrix and fee policy, approve exceptions, compare campuses
Applicant / parentOwn application status, document checklist, offer, and payment positionApply, upload documents, accept an offer, pay, and track their own status

§ 05

What it connects to

Acquisition on one side, the registry on the other. The handover to the ERP is the one that matters most and is the one general CRMs cannot do.

Acquisition

  • Meta Lead Ads and Google Ads lead forms
  • Website and landing-page forms with UTM capture
  • Call tracking and cloud telephony with recordings
  • WhatsApp Business API two-way conversations
  • Education marketplaces and listing portals

Conversion

  • Payment gateways with per-offer payment links
  • UPI collect and dynamic QR
  • e-sign for offer acceptance where the institution uses it
  • DigiLocker document pull for verification

Institutional

  • Education ERP registry — the enrolled handover
  • Learning Management System for trial and demo access
  • Entrance test platforms with score import
  • Shared identity across the suite

Analytics & outreach

  • GA4 and conversion export back to ad platforms
  • Transactional email and SMS
  • Data warehouse export for season analysis

§ 06

Ground it stands on

An admissions CRM holds personal data collected before any relationship exists, which makes consent the whole ball game. Under the Digital Personal Data Protection Act, 2023, notice must be given at collection in clear language, the stated purpose limits what the data may later be used for, and an enquiry that never converts cannot simply be retained indefinitely in case it is useful next season. Where the prospective student is a minor — which covers most school and foundation-coaching enquiries — verifiable guardian consent is required and behavioural advertising to them is prohibited.

Outbound contact carries its own rules. Commercial communication by SMS and voice sits under TRAI's regulations, and WhatsApp Business messaging has its own template and opt-in requirements that are enforced by the platform rather than by a regulator. Both are configured here as constraints on the cadence, not as guidance in a policy document.

The seat allocation itself is the part institutions are most often asked to defend. Merit criteria, tie-break rules, quota seats, and waitlist movement each produce a decision that a family — or a regulator — may challenge, sometimes years later. Each is applied as a recorded rule with the resulting order retained.

Implemented against

  • DPDP Act 2023 — notice at collection, purpose limitation, and consent withdrawal
  • Verifiable guardian consent where the prospective student is a minor
  • Retention policy for non-converting enquiries, executed rather than promised
  • TRAI commercial communication rules for SMS and voice outreach
  • WhatsApp Business template approval and opt-in enforcement
  • Merit, tie-break, and quota rules applied as recorded rules with the order retained
  • Waitlist movement logged in sequence, defensible on challenge
  • Document access restricted to the verification role, not the whole funnel
  • Full audit on offer issuance, concession approval, and seat allocation

§ 07

What it replaces

Compared against a general sales CRM plus the spreadsheet that inevitably runs beside it.

What it replaces
AspectGeneral CRM + the real spreadsheetThis platform
SeatsTracked in a spreadsheet the CRM knows nothing aboutA live matrix by programme, category, and quota that cannot be over-allotted
ConversionA stage someone drags a card intoA fee paid against a specific held seat
Stalled applicationsA deal at 60 percent probabilityA named missing document with a chase running on it
Response timeUnmeasuredAn SLA per enquiry with escalation on breach
AttributionCost per leadCost per enrolled student, and again per retained student
Handover to the ERPRe-typed by the front office in the admission weekThe record becomes the student record; nothing is re-entered
WaitlistManaged by whoever remembers the orderMoved in a recorded sequence that can be defended

§ 08

Rollout

Timed to be live before the season opens, never during it. An admissions team asked to learn a new system in peak week will run the spreadsheet instead, and they will be right to.

  1. 01Week 1–2

    Funnel design

    • Stages, allocation rules, and cadences configured to how your team actually works
    • Seat matrix, quota, and merit criteria loaded per programme
    • Document checklists defined per category and programme
    • Existing enquiry data migrated and de-duplicated
  2. 02Week 3–4

    Channels live

    • Website forms, ad lead-forms, call tracking, and WhatsApp connected
    • Consent notice and opt-in wording reviewed and deployed at every capture point
    • Message templates approved and loaded
    • Counsellors trained on their own pipeline, not on a feature tour
  3. 03Week 5–6

    Application to offer

    • Online application, document upload, and verification queue live
    • Eligibility, merit list, and offer issuance rehearsed against last season's data
    • Payment links and seat-hold expiry configured
    • Refund and cancellation policy encoded as rules
  4. 04Before the season opens

    Handover & attribution

    • ERP registry handover tested end to end with a real enrolment
    • Attribution reporting validated against last season's known outcome
    • Season dashboards signed off by the admissions head
    • Runbook and escalation ownership handed to your team

Talk to an engineer

Bring last season's numbers.

We will show where the funnel actually leaked and what it cost per enrolled student — before you decide anything.

  • Your data stays yours — NDA on request before anything is shared
  • A working demonstration, not a slide deck
  • Written scope and an honest timeline before any commitment

We reply within one business day.

We use these details only to respond to your enquiry. See our privacy policy.

§ FAQ

Questions we are actually asked

We already use a general CRM. Why change?

The test is whether your seat matrix lives inside it. In our experience it does not — seats, quota, merit order, and waitlist movement end up in a spreadsheet beside the CRM, which means the spreadsheet is the real system and the CRM is a call log. If your admission genuinely is a simple pipeline with unlimited capacity, a general CRM is fine and we will say so. If it has finite seats under rules you may have to defend, it is not.

Does it replace our marketing tools?

No. It ingests from them — Meta and Google lead forms, landing pages, call tracking, WhatsApp — and it exports conversions back so the ad platforms optimise toward enrolments rather than form fills. Campaign creation and creative stay wherever you run them today.

What exactly happens when a student enrols?

The applicant record becomes a student record in the ERP registry, carrying the verified documents, the interest profile, the concession applied, and the full interaction history. Nobody re-types a name, and the admission number issued at that moment is the same identifier the student carries to their transfer certificate or degree. That handover is the main reason to run an education CRM rather than a general one.

Can we use it without your ERP?

Yes — enrolled records export over an API or a scheduled file in a format your ERP accepts, and several institutions run it that way. You lose the zero-re-entry handover and the retention-based attribution, which is the part that measures whether a campaign produced students who stayed rather than students who enrolled.

How do you handle consent and the messages we send?

Consent notice and purpose are captured at every point of collection in the wording you approve, and withdrawal is honoured across every channel rather than per channel. Outbound is constrained by TRAI rules for SMS and voice and by WhatsApp's template and opt-in requirements — the cadence engine will not send what the rules do not permit, which is a deliberate limitation rather than an oversight.

Our counsellors work on phones during walk-in season. Does that work?

The counsellor surface is mobile-first and tolerant of poor connectivity — a walk-in captured on a tablet in a corridor syncs when the connection returns rather than being lost. Analysis and configuration are desktop tasks and are designed for a desktop.

Can each campus in a group run its own admission?

Yes. Seat matrices, fee structures, criteria, and counsellor teams are per campus, while group management sees the consolidated funnel with drill-down. Enquiries that arrive at the wrong campus can be transferred with their history and their source attribution intact.

Primary sources

Elsewhere in the suite