Give each admissions enquiry a recognised contact, a responsible counsellor and a useful next step without confusing appointments with enrolments.
Connect student interest with responsible follow-through.
A prospective student fills in a website form, sends a social media message and later visits the office. Three counsellors see three enquiries. One calls about a course the student has already ruled out; another assumes a colleague is following up.
The institution has activity, but it does not yet have a reliable view of the person’s enquiry.
CRM software for colleges and consultancies should help staff recognise the enquiry, assign a responsible counsellor and record the next useful step. It should also distinguish an interested person from a completed admission or paid service engagement.
This article uses hypothetical admissions and counselling examples. It does not claim enrolment results, visa outcomes or capabilities currently available in WorkSphere.
One conversation can lead to different programme interests and a useful next appointment.
Separate the person from the opportunity
One person can ask about several programmes or intakes. Keep a stable contact reference, then link the particular course, intake or counselling requirement to it. Do not make a fresh person record every time the same student changes an interest.
Recognise the enquiry and record the student’s relevant next step.
A practical initial record needs the name, a verified contact method, programme interest, preferred intake, enquiry source, assigned counsellor and next action. Record the student’s preference for contact and the context in which details were supplied. Avoid collecting identity documents merely to answer a first enquiry.
Frappe CRM’s Lead documentation illustrates ownership, status, activity history and linked tasks in a lead record. Those are useful workflow concepts, rather than evidence that a particular W3 integration is live.
For a college, the next step might be a campus visit or a programme discussion. For a consultancy, it might be an initial counselling appointment. The later processes differ, so the two pipelines should not be forced into identical stages.
Keep the person’s identity stable while tracking each programme or intake separately.
Define stages using evidence
“Interested” is too broad to explain what a counsellor should do tomorrow. Agree what moves an enquiry forward and what remains unconfirmed.
| College enquiry stage |
Evidence to keep |
| New enquiry |
Contact and programme interest received |
| Contact established |
Relevant conversation recorded |
| Visit or counselling booked |
Appointment time confirmed |
| Application in progress |
Application reference and missing requirements |
| Enrolled |
Institution’s actual admission confirmation |
A consultancy can use appointment, counselling and application-service stages relevant to its own process. Keep an external university decision or visa outcome separate from the consultancy’s internal service status. A booked meeting is not an admission, and payment alone does not establish an external decision.
A booked appointment and an application each need their own evidence; enrolment is a separate decision.
Check duplicates without merging different people
A shared family phone number does not prove two enquiries belong to the same person. Compare the name, verified contact information and context before merging records. Preserve the original source references and an explanation of any merge.
ERPNext’s CRM settings documentation shows that email-duplication behaviour is configurable. A duplicate rule is a business decision to test, not an assumption to leave hidden in the software.
In a hypothetical intake review, the team receives 50 enquiry submissions. Eight are confirmed repeat submissions about the same opportunities. The review therefore contains 42 unique enquiries, each counted once in its current stage.
| Current stage |
Unique enquiries |
| New and awaiting first contact |
10 |
| Contact established |
12 |
| Appointment booked |
8 |
| Application in progress |
7 |
| Enrolled with confirmation |
5 |
| Total |
42 |
The check is 50 submissions − 8 confirmed repeats = 42 unique enquiries, and 10 + 12 + 8 + 7 + 5 = 42. These are current positions, not cumulative stage totals. They are not an institutional conversion benchmark. Repeated calls and messages must not increase the count of unique enquiries.
Count each unique enquiry once in its current position.
Make follow-up useful to the student
Each active enquiry should have an accepted owner and a specific next action. “Follow up” could mean almost anything. “Confirm whether the student can attend the Saturday counselling slot” gives the counsellor a clear purpose.
After a conversation, record what was discussed, the student’s relevant preference and the agreed next step. When a colleague takes over, they should be able to continue without making the student repeat the whole history.
Avoid sending the same reminder from several channels simply because the system allows it. A request to stop promotional contact needs a clear route through the institution’s actual communication process. Staff should know who may view or export records and how access ends when a counsellor leaves.
These are proposed operational controls, not a claim about Nepal privacy-law compliance. Confirm the institution’s legal and retention requirements before designing document storage or mass messaging.
Make the next useful action clear enough for another counsellor to continue the conversation.
Connect enquiries to admissions work without losing boundaries
A CRM can show the customer-facing next step while Task Management holds document checks or appointment preparation. HRM availability references may help schedule the appropriate counsellor. Accounting should identify the actual payer, approved fee and receipt reference when money is collected.
Keep follow-up understandable when another counsellor takes over.
Keep those links explicit. Marking an enquiry “enrolled” should not automatically issue a receipt or suggest that every required admission check has been completed.
For planned WorkSphere connections, first agree the institution’s fields, permissions, stages and approval evidence. Website forms, social lead capture, messaging and accounting links need individual scope confirmation. Do not assume a channel integration exists because a CRM product can store a phone number.
When discussing W3’s software services, bring examples from both a successful enquiry and one that stalled. The differences often reveal what the workflow must record.
Admission evidence and financial authorisation are separate controls.