Enrolment Funnel and CRM Automation for a Nairobi and Nakuru Education Provider

Context

The client runs a private education provider with campuses in Nairobi and Nakuru offering a mix of secondary level and vocational diploma programs. Enrolment happens twice a year around the January and September intake windows, which means the marketing calendar is really two intense sprints separated by long stretches of lower activity, a rhythm that had never been properly reflected in how the client planned campaigns or staffed follow up.

Parents and prospective students, often the same family weighing multiple institutions at once, typically start researching options three to six months before an intake, comparing fees, facilities, and outcomes across several schools in Nairobi, Nakuru, and sometimes further afield. The client's annual marketing budget of roughly KES 4.5 million was split across the two campuses and spent mostly on Facebook ads and a handful of local radio spots in Nakuru, with almost nothing invested in the systems needed to manage the enquiries that spend generated.

The Problem

The enquiry to enrolment journey was long, involving campus tours, fee discussions, and often multiple family decision makers, and the client's process for managing it was a shared spreadsheet updated inconsistently by admissions staff at each campus. Enquiries came in through Facebook lead forms, a website contact form, walk ins, and phone calls, and none of these were unified anywhere. It was common for a family that had enquired online to walk into the Nakuru campus a week later and be treated as a fresh enquiry because nobody could see the earlier record.

Follow up was inconsistent by design of the process rather than by staff failing individually. Admissions officers, juggling walk ins and phone calls, simply did not have time to systematically follow up every digital enquiry within a useful window, and by the time some families were contacted, they had already toured or paid a deposit at a competing school. Fee sensitive families in particular needed multiple touchpoints, information on payment plans, M-Pesa paybill details for deposits, and clarity on what was included in termly fees, and none of that was delivered proactively.

There was also no visibility into where the budget was actually working. The client could see Facebook's own reported lead numbers but had no way to connect which leads from which campaign, campus, or program actually enrolled, which meant campus principals were making renewal decisions on gut feel about which channels felt like they were working.

What We Did

1. Implemented a shared CRM across both campuses. We selected and configured a CRM that unified enquiries from Facebook lead ads, the website, phone, and walk ins into a single record per family, visible to admissions staff at both Nairobi and Nakuru so a family engaging with either campus was recognized immediately.

2. Mapped and rebuilt the enrolment funnel stages. We defined clear stages from initial enquiry through information sent, tour booked, tour completed, fee discussion, deposit paid, and enrolled, replacing the informal spreadsheet categories that had made it impossible to see where families were actually dropping off.

3. Built automated follow up sequences for each funnel stage. New enquiries triggered an immediate automated response with program information and next steps, followed by scheduled SMS and email nudges timed to the intake calendar, so a family that enquired in October for the January intake received a different cadence than one enquiring in December.

4. Created a fee and payment clarity workflow. We built a dedicated automated sequence addressing the fee questions that came up most often in admissions calls, including a clear breakdown of termly fees, available payment plan options, and step by step instructions for paying deposits via M-Pesa paybill, which removed a recurring back and forth that had been slowing decisions down.

5. Set up campaign and campus level attribution. We connected CRM enrolment outcomes back to the original campaign, campus, and program a family had engaged with, giving the client, for the first time, a real view of cost per enrolment by channel rather than just cost per lead.

6. Trained admissions staff on CRM discipline and handoff. We ran hands on training sessions with both campus admissions teams on logging every interaction and using the automated sequences as a support rather than a replacement for personal follow up, since the automation was designed to keep families warm between human touchpoints, not to replace the tour and conversation that ultimately closed most enrolments.

Results

Enquiry drop off, meaning families who enquired but were never successfully re contacted or converted to a tour, fell 44% once the automated follow up sequences and unified CRM record eliminated the gaps that had previously let leads go cold. Enrolment conversion rate, from qualified enquiry to paid deposit, rose 2.2x across the two campuses over the following intake cycle compared to the equivalent cycle the prior year.

The decision cycle, meaning the average time from first enquiry to enrolment, shortened by 29%, which the client's finance team valued highly because it meant deposit revenue arrived earlier and more predictably ahead of each intake, easing the cash flow pressure that had previously built up right before term start.

What We Would Do Differently

We built the CRM and automation before fully training admissions staff on the discipline of logging every interaction, and in the first month several enquiries were still handled off system out of habit, undermining the unified view we had just built. Sequencing the training first, even a lighter version of it, before the technical rollout would have produced cleaner data from day one.

We would also introduce campus specific automated sequences earlier, since Nairobi and Nakuru families asked meaningfully different questions, transport and boarding questions were far more common in Nakuru, and the generic first version of our sequences did not reflect that until we revised them after the first intake cycle.