A lead is more than a phone number
A parent can enquire through a website, social advertisement, phone call or walk-in. When these conversations live in different inboxes, staff may not know whether a colleague has already replied. A contact list shows who asked; it rarely explains what the team should do next.
A school admission CRM should make that next action visible. Its purpose is to organise a responsible conversation, preserve context and help the institution understand the journey. It cannot guarantee admission or replace programme quality, timely responses and a suitable offer.
Use stages that describe real events
| Stage | Evidence needed | Next action |
|---|---|---|
| New enquiry | Source and contact recorded | Assign a counsellor |
| Contacted | Conversation outcome saved | Agree an appropriate next step |
| Visit or demo booked | Date and meeting type confirmed | Prepare and remind |
| Application in progress | Family has started the application | Resolve missing information |
| Admitted or closed | Defined decision recorded | Handover or closure reason |
Separate response speed from conversion quality
Track first-response time, overdue actions, booked-to-attended visits and applications that remain incomplete. These measures identify where work stops. A high enquiry count can hide poor follow-up; a high admission count can hide an unclear denominator.
Agree on reporting definitions before comparing counsellors. Decide whether repeated submissions count as the same enquiry, how transfers between branches are attributed and which academic year an application belongs to. Record the rule in the report so a later user can understand it.
Make duplicate enquiries manageable
A family may use a different phone number for a second enquiry, and siblings may share a contact. Do not merge records solely because a phone number matches. Present likely duplicates for review and preserve each child’s application context.
Maintain a dated interaction history and record contact preferences. Store only the information needed for the enquiry. A public form should save to a controlled queue; access to the queue should belong to authorised admissions staff, not everyone with a website login.
A weekly admissions review that leads to action
Use the review to remove blockers. If many families ask the same unanswered fee question, improve the information given before the visit. If demos are booked but not attended, check whether the time, format and reminder were agreed clearly. A CRM should make these patterns easier to investigate.
- Review new enquiries without an assigned owner.
- Check overdue follow-ups and missed demos.
- Separate families waiting for information from those who declined.
- Record a reason for closures without blaming the family.
- Review sources by attended visits and applications, not clicks alone.
Test the CRM before the admission season
Submit a labelled synthetic enquiry through every source you intend to use. Confirm that it reaches the correct queue, receives the expected branch assignment and keeps its source. Book both an online demo and a campus visit, then reschedule one and inspect the history.
Finally, convert a test application through the approved handover and verify that the enrolled student is created once. Do not judge a CRM only by its dashboard: follow the record through the complete workflow.
Questions institutions ask
What fields are essential for a school enquiry?
Begin with the interested family’s contact details, student or programme context, source, branch, owner and next action. Add fields only when they support a clear decision.
Can a CRM guarantee more admissions?
No. It supports organised follow-up and measurement. Admission outcomes also depend on demand, programme quality, fees, communication and family choice.
Editorial note: This is a practical workflow guide. Examples are illustrative, not customer results. Product availability and institution-specific requirements must be confirmed separately.
← Back to all articles