EDUCATION & TRAINING CRM

Nepal tutoring centres and private schools tracking student enquiries on paper and fee payments in a notebook are one registration season away from losing enrollments to competitors who respond faster and follow up better

A configured CRM built for Nepal's private education sector replaces scattered WhatsApp threads, manual fee registers, and memory-based enrollment management with a single system that captures every enquiry, tracks every instalment, and follows up automatically.

This is for you if

Who This Is For

Private boarding schools in Kathmandu and other major urban centres manage a multi-stage admissions process — initial enquiry, entrance test, interview, offer, and fee payment — across hundreds of families each year. Most are running this process through a combination of physical registers, Excel workbooks, and personal email accounts. There is no pipeline view of how many students are at each stage, no automated follow-up when a family goes quiet after an interview, and no central record of which families have paid the admission fee deposit and which have not.

Tutoring centres focused on SEE and +2 preparation face a highly concentrated enrollment window each year. In the weeks following SLC and SEE results, centres receive a high volume of enquiries simultaneously — by phone, Facebook message, WhatsApp, and walk-in — and the ability to respond quickly and follow up systematically is the difference between filling batches and leaving seats empty. Without a CRM, the fastest centres to respond are not necessarily the best academically, just the best operationally.

CTEVT-affiliated vocational institutes and IT training centres run multiple batches of courses simultaneously, each with its own start date, fee structure, and student intake. Managing batch registrations across multiple courses without a CRM means staff are manually tracking who is registered for which batch, who has paid, and when the next batch opens. When a batch fills, there is no waitlist management system and no automated notification to students on the waitlist when a seat opens.

Language test preparation centres operate on a calendar driven by IELTS and PTE test dates. Students enrol in preparation courses aligned to a specific test date, and the centre needs to track which test date each student is preparing for, whether they have registered for the test, and whether they need to be moved to a later cohort. This structure requires a CRM that can manage enrollment by cohort and test date, not just by course name.

What's broken

What's Broken

Student enquiries lost in WhatsApp and paper registers

The majority of student enquiries for Nepal tutoring centres and training institutes arrive through Facebook Messenger, WhatsApp, and phone calls. None of these channels create an automatic CRM record. When a parent sends a WhatsApp message asking about the next batch start date, that message lives in a staff member's personal phone. If that staff member is unavailable, leaves the job, or simply forgets to follow up, the enquiry is lost. Centres operating this way have no visibility into how many enquiries they received last month, what proportion converted to enrollments, or which communication channel is generating the most interest. The data required to make basic operational decisions does not exist.

No fee instalment tracking for students on monthly payment plans

Many Nepal private schools and training institutes allow students to pay fees in monthly instalments rather than as a lump sum. This is commercially necessary given household income constraints, but it creates a tracking burden that spreadsheets handle poorly. When thirty or fifty students are on individual instalment schedules, each with a different start date and monthly amount, tracking which students have paid this month and which are overdue requires manual reconciliation. Staff typically do this by checking a notebook against a bank statement. Students who fall two or three months behind are often only identified when the discrepancy becomes large enough to be noticed, by which point recovering the outstanding amount is significantly harder.

Enrollment surge management by memory during registration season

Nepal's tutoring centres and private schools experience a highly concentrated registration window each year. During peak registration weeks, centres may receive ten to thirty enquiries per day across multiple channels simultaneously. Without a CRM pipeline, staff manage this volume by memory and physical lists. There is no system indicating which enquiries have been contacted, which families have submitted documents, which students have paid the registration fee, and which are waiting on an interview. Decisions about batch capacity and waitlist management are made on incomplete information, and families who expressed strong interest but were not followed up systematically enrol elsewhere.

No re-enrollment campaign for students who completed a course

When a student completes a course or a preparation batch, the most likely candidate for the next enrolment is that same student for the next level, the next test date, or a complementary course. Nepal training institutes and tutoring centres almost universally miss this opportunity because there is no automated outreach triggered by course completion. Staff may remember to call a few students, but there is no systematic campaign that goes to every completing student with a relevant offer for the next step. Revenue that should be retained through the existing student base is instead left to chance.

What we engineer

What We Do

Enquiry capture workflow

We build and configure a CRM system tailored to the operational reality of Nepal's private education and training sector. The starting point is always the enquiry capture workflow. We connect the centre's existing Facebook page, WhatsApp number, and website contact form to the CRM so that every inbound enquiry creates a contact record automatically, regardless of which channel it came through. Each contact is assigned to a staff member and enters a defined follow-up sequence — typically a first response within one hour, a follow-up after twenty-four hours if there is no reply, and a third touchpoint after three days.

Multi-stage enrollment pipeline

We configure a multi-stage enrollment pipeline that reflects the centre's actual process. For a tutoring centre this is typically: Enquiry Received, Initial Contact Made, Batch Allocated, Registration Form Submitted, Fee Paid (or First Instalment Received), Enrolled. For a boarding school the pipeline stages are longer and include document submission, entrance test, and interview steps. Every student record moves through this pipeline visibly, and the centre's management can see at any time how many students are at each stage and which ones have stalled.

Fee instalment tracking

Fee instalment tracking is built as a structured payment schedule linked to each student record. When a student is enrolled on a monthly instalment plan, the agreed schedule is entered into the system — amount, due date, and number of instalments. The CRM generates an automated reminder sent to the student or parent by WhatsApp or SMS three days before each instalment due date, and a second reminder if payment is not received by the due date. Staff see an overdue payment dashboard showing all students with outstanding instalments, without needing to manually reconcile a spreadsheet.

Batch and course management

For centres running multiple course batches simultaneously, we configure batch and course management objects in the CRM. Each batch has a capacity, a start date, a current enrollment count, and a status — Open, Full, or Waitlisted. When a student is enrolled in a batch, the batch enrollment count updates automatically. When a batch reaches capacity, subsequent enquiries are automatically placed on a waitlist and notified when a seat opens.

Re-enrollment and retention campaigns

Re-enrollment and retention campaigns are configured as automated sequences triggered by course completion. When a student's course end date is reached and their status is marked Complete, a campaign triggers that sends a personalised message acknowledging their completion and presenting a relevant next step — the next test preparation cohort, the advanced course level, or a complementary certification. These messages are sent via WhatsApp or SMS, the channels with the highest open rates in Nepal's market.

Source tracking system

We also build a source tracking system so that every new enquiry record captures where it came from — Facebook, referral, walk-in, phone call, or the centre's website. After ninety days of data, the centre has a clear picture of which channels are producing enquiries and which are producing enrolled students, which are not the same thing.

What changes

What Changes

Before
After
Before The majority of student enquiries for Nepal tutoring centres and training institutes arrive through Facebook Messenger, WhatsApp, and phone calls. None of these channels create an automatic CRM record. When a parent sends a WhatsApp message asking about the next batch start date, that message lives in a staff member's personal phone. If that staff member is unavailable, leaves the job, or simply forgets to follow up, the enquiry is lost. Centres operating this way have no visibility into how many enquiries they received last month, what proportion converted to enrollments, or which communication channel is generating the most interest. The data required to make basic operational decisions does not exist.
After After the system is live, the centre's management sees the full enrollment pipeline in a single dashboard view rather than asking staff for status updates. Every enquiry that arrives through Facebook, WhatsApp, or the website is captured automatically — no enquiry is lost because a staff member was busy or forgot to log it.
Before Many Nepal private schools and training institutes allow students to pay fees in monthly instalments rather than as a lump sum. This is commercially necessary given household income constraints, but it creates a tracking burden that spreadsheets handle poorly. When thirty or fifty students are on individual instalment schedules, each with a different start date and monthly amount, tracking which students have paid this month and which are overdue requires manual reconciliation. Staff typically do this by checking a notebook against a bank statement. Students who fall two or three months behind are often only identified when the discrepancy becomes large enough to be noticed, by which point recovering the outstanding amount is significantly harder.
After The automated follow-up sequence means every enquiry receives a first response within an hour and continues to receive follow-up messages on a defined schedule without staff needing to remember who to call. Centres that implement this consistently see a measurable improvement in enquiry-to-enrollment conversion rate in the first full registration season after the system is live.
Before Nepal's tutoring centres and private schools experience a highly concentrated registration window each year. During peak registration weeks, centres may receive ten to thirty enquiries per day across multiple channels simultaneously. Without a CRM pipeline, staff manage this volume by memory and physical lists. There is no system indicating which enquiries have been contacted, which families have submitted documents, which students have paid the registration fee, and which are waiting on an interview. Decisions about batch capacity and waitlist management are made on incomplete information, and families who expressed strong interest but were not followed up systematically enrol elsewhere.
After Fee collection improves because students on instalment plans receive automated reminders before each payment is due rather than only being chased after they fall behind. Overdue payments are identified within days rather than weeks. The outstanding fees balance visible in the dashboard gives management the information to make decisions about whether to allow a student to continue attending while their balance is unpaid.
Before When a student completes a course or a preparation batch, the most likely candidate for the next enrolment is that same student for the next level, the next test date, or a complementary course. Nepal training institutes and tutoring centres almost universally miss this opportunity because there is no automated outreach triggered by course completion. Staff may remember to call a few students, but there is no systematic campaign that goes to every completing student with a relevant offer for the next step. Revenue that should be retained through the existing student base is instead left to chance.
After Batch management becomes a scheduled operational process rather than an ad hoc one. When a batch fills, the waitlist captures subsequent enquiries automatically and notifies students when seats open. When a new batch is opening, a campaign can go out to all waitlisted students and to all students who completed the previous equivalent cohort.
How it works

Process

  1. 01

    Diagnostic call

    We begin with a sixty-minute call covering the centre's current enrollment process from first enquiry to first day of class, the current fee structure and instalment arrangements, and the communication channels the centre uses to reach students and parents. We also identify which existing tools — WhatsApp, Facebook, Excel, registers — are currently in use and what can be integrated versus replaced.

  2. 02

    Pipeline and workflow design

    Based on the diagnostic, we document the enrollment pipeline stages, the follow-up sequence timing and message content, the fee instalment tracking structure, and the batch management configuration. We present this as a workflow map before building anything, so the centre's management can confirm the logic reflects how they actually operate.

  3. 03

    CRM build and configuration

    We build the CRM — typically GoHighLevel for Nepal's market — configuring the pipeline stages, contact record fields, batch and course objects, payment schedule structure, and automation sequences. We connect the Facebook page, WhatsApp number, and website contact form to the CRM so that inbound enquiries flow in automatically.

  4. 04

    Message templates and automation

    We write and configure all message templates: the initial enquiry response, the follow-up sequence messages, the fee instalment reminders, the batch confirmation message, the waitlist notification, and the re-enrollment campaign. Templates are written in Nepali and English, and reviewed by the centre before activation.

  5. 05

    Staff training

    We run a two-hour training session with the staff members who will use the system daily — covering how to manage the pipeline, how to update student records, how to handle payment entries, and how to interpret the reporting dashboard. We provide a written reference guide specific to the centre's configured system.

  6. 06

    Go-live and thirty-day review

    The system goes live, and we monitor for the first thirty days — checking that enquiries are being captured correctly, that automations are triggering as expected, and that staff are using the pipeline consistently. At thirty days we run a review call, address any workflow issues, and make configuration adjustments based on what the data shows.

Common questions

FAQ

What CRM should a private school or tutoring centre in Nepal use — GoHighLevel or HubSpot?

GoHighLevel is the more practical choice for most Nepal education businesses because it includes WhatsApp and SMS automation natively, supports multi-pipeline management, and is priced in a way that makes sense for a business with limited technology budget. HubSpot's free tier is functional for basic contact management but does not include WhatsApp automation or the payment plan tracking structures that Nepal tutoring centres need. For a centre whose primary communication channel is WhatsApp and whose fee structure involves instalments, GoHighLevel covers the core requirements without requiring additional integrations. HubSpot becomes relevant for larger institutions that already have a marketing team and are running email-heavy communication workflows.

How do I build a student fee instalment tracking system for a Nepal-based education business?

A fee instalment tracking system in GoHighLevel is built by creating a custom object for payment schedules linked to each student contact record, with fields for instalment amount, due date, and payment status. Each student on an instalment plan gets a payment schedule record created at enrollment, and an automation triggers a WhatsApp reminder three days before each due date and a follow-up if the payment is not marked received within two days of the due date. Staff update payment status when funds are received, and the management dashboard aggregates all overdue instalments in a single view. This removes the need for any manual spreadsheet reconciliation.

How do I manage a seasonal enrollment surge for an SEE/+2 tutoring centre in Nepal using a CRM?

Managing a seasonal enrollment surge requires the CRM to be fully configured before the surge period begins, not during it. The enrollment pipeline stages are defined in advance, batch capacities are set in the system, and the automated follow-up sequence is activated so that every new enquiry receives an immediate response and enters a follow-up flow without staff needing to remember each individual contact. During the surge, staff work from the pipeline view — seeing all active enquiries at each stage — rather than from a phone contact list. Batch enrollment counts update as students are enrolled, and when a batch reaches capacity, the system switches automatically to waitlist management.

How do I automate re-enrollment outreach for students who completed a course at a Nepal training institute?

Re-enrollment automation is triggered by a status change in the student's record: when a student's enrollment status is updated to Complete and their course end date is reached, an automation sequence begins. The first message — sent via WhatsApp — acknowledges the completion and presents the next relevant course or batch with a specific start date and fee. A second message follows five to seven days later if the student has not responded. The sequence is configured once and applies to every completing student going forward without staff needing to initiate it manually. The message content is personalised using the student's name, the course they completed, and the specific next step recommended for their profile.

How do I track the source of student enquiries (Facebook, referral, walk-in) in a CRM for a Nepal education business?

Enquiry source tracking in GoHighLevel is implemented through a combination of automatic source attribution for digital channels and a required intake field for non-digital channels. Enquiries that come through Facebook Lead Ads or a website form are automatically tagged with their source by the CRM. Enquiries that come through walk-in or phone call are entered manually by staff, who select the source from a dropdown field — walk-in, phone, referral, or other — at the time of entry. Referral enquiries include a secondary field capturing the name of the referring student or family, which feeds a referral tracking report. After ninety days, the source report shows which channels produce enquiries, which produce enrolled students, and which produce students who pay in full versus on instalments.

Start here

Closing CTA

Nepal's private education sector is adding students every year, and the centres that convert the most enquiries to enrollments in the next registration season will not necessarily be the ones with the best teachers or the strongest academic results. They will be the ones that respond to enquiries within an hour, follow up systematically, track every fee instalment, and contact completing students before a competitor does. That is an operational advantage, and it is available to any centre willing to configure the right system.