The complete module catalogue
Academic core, portals, operations, staff, inclusion and compliance — grouped into six clusters with what each one actually does.
Browse every moduleMatric and O Level, side by side
A school running a national stream and a Cambridge stream runs both in one CampusFlo tenant — separate ladders, separate grading, one student record.
See how it worksConfiguration, never a fork
A profile sets the level ladder, term structure, grading scheme, attendance model and the vocabulary itself. Every value stays editable afterwards.
One product, every countrySee it on your own scenario
A screen-share run against your levels, your grading scheme and your board — not a slide deck. Bring your student count and campuses.
Schedule a demoA parent walks into the office, or rings during break, and right now that enquiry lives on a diary page or in somebody’s WhatsApp thread. Here it becomes a record with a counsellor, a stage and a date for the next call — so nothing quietly goes cold.
Walk-ins · calls · website · WhatsApp · referrals
Most school enquiries still arrive in person — a parent at the front desk asking whether there is a seat in Class 1. Every source is recorded the same way, so the walk-in is as trackable as the form submission, and you find out at the end of the intake which one actually filled the seats.
The source is not a dropdown nobody fills in. It carries through to the conversion report, so “the flyers brought forty enquiries and two admissions” is a number you can read rather than a feeling you have.
An enquiry moves through named stages instead of sitting in a list marked “pending”. The seven below are seeded for schools; a school that runs an interview round or a fee-discussion step inserts its own stage and the reports follow it.
“Not interested” is a stage with a reason attached, not a delete. Next year’s planning reads better when you can see that eleven families walked because Class 4 had no seat.
A generic CRM offers you Company, Website and Estimated Value. A school needs to know which parent is asking, for which child, for which class, and whether that child will even be old enough on the cut-off date. Those fields are the product.
Convert to application opens the admission form already filled in from the enquiry, and runs the admissions checks before it lets you through — intake open, class offered, age on the cut-off date. Nobody retypes a parent’s phone number that has already been written down once.
This page ends where the application begins. Everything after conversion — the form, the entrance test, the merit list, the offer and the admission — belongs to the admissions module.
Every open enquiry has an owner and a next date, and the desk opens on what is overdue rather than on everything ever recorded. An enquiry nobody has touched for seven days is flagged whether or not anyone remembered it.
What the counsellor sees first thing in the morning.
Assignment is a setting, not a convention people remember.
When a number that already exists is entered again, the earlier enquiries appear before a second record is created. Usually it is not a duplicate at all — it is the same family asking about a second child, and that is a sibling, not a mistake.
A matching mobile or WhatsApp number surfaces every earlier enquiry from that family, at the moment of entry rather than in a cleanup later.
The new enquiry is linked to the family instead of duplicating the parent, so both children stay visible on one record.
Counting each of them as a separate unrelated lead is how a pipeline stops resembling the school.
CampusFlo holds the enquiry. Foxaf talks to the family. They are both IT Vision products and the split is deliberate: a school-management system has no business growing a second, worse marketing-automation tool inside itself.
The record, the pipeline and the school’s own rules.
The conversation with the family.
Replies and Foxaf form submissions flow back into the enquiry timeline, so the counsellor reads one story rather than checking two screens. CampusFlo’s own notices — fee challan, attendance, results — can go out through the same Foxaf WhatsApp channel, so a school runs admissions marketing without buying a third tool.
Consent is enforced, not assumed. An enquiry is pushed to Foxaf only when WhatsApp consent has been recorded. Without it, the number is withheld and the contact is tagged so campaigns exclude it — which is what Meta’s opt-in policy requires, and what a parent who never agreed to be messaged is entitled to.
At the end of an intake the useful questions are which sources converted, which counsellor is carrying the desk, and which classes were asked for more often than there were seats. Each is a report rather than a spreadsheet somebody rebuilds every year.
A closed enquiry keeps its reason, and the reasons are the shortlist a school actually hears at the front desk.
There is a public enquiry page you can link to, and an embed you can paste into your own site so the form sits on your pages and still lands on the enquiry desk. Submissions arrive in the same queue as walk-ins, with the same stages and the same follow-up rules.
A form submission is an enquiry like any other — no second inbox to remember to check.
A honeypot field and a submission throttle, so the desk is not filled with junk overnight.
A consent box, recorded against the enquiry, which is what decides whether the contact can be messaged later.
Where the visitor came from is carried into the record, so campaign spend reconciles against admissions.
The enquiry desk is the front of the funnel, and it hands over cleanly rather than living on its own.
Whatever it lives in now — a diary, a WhatsApp group, a spreadsheet — we will walk it through the desk and show you what the follow-up queues and the source report would have told you at the time.