Most groups manage the first two stages in marketing tools, the middle stages in admissions and the last stage in the student information system. The handoffs between them are where families are lost, and where reporting breaks.
Why does one record per family matter?
The buyer and the student are usually different people. A parent enquires, a grandparent may pay, and the child is the one enrolled. Siblings follow years later. A CRM built around single contacts loses that picture.
We design the record around the family: parents and guardians as contacts, linked to each other and to the student, with every enquiry, visit and conversation on the timeline. HubSpot lists a Courses object among its standard objects, and custom objects, which HubSpot says require an Enterprise subscription, can model programmes, intakes or campuses where the standard objects do not fit (HubSpot Knowledge Base).
How should enquiries and visits be handled?
In much of the region, parents prefer messaging to forms. HubSpot connects WhatsApp Business natively to its conversations inbox on Marketing Hub or Service Hub Professional or Enterprise (HubSpot Knowledge Base). That puts each enquiry on the family's record and makes response time measurable by campus.
Visits are the strongest signal in the journey. HubSpot's scheduling pages let families book time directly, and its round robin pages show the availability of a whole admissions team; HubSpot says team pages need Sales Hub or Service Hub Starter or above (HubSpot Knowledge Base). Route bookings by campus and language, send reminders, and record attendance, so that “booked” and “attended” are two different numbers.
Where do AI agents help admissions teams?
Admissions teams answer the same questions every intake: fees structure, age requirements, curriculum, transport, intake dates and visit times. That is the right first job for an agent.
HubSpot's documentation says Customer Agent can be deployed to WhatsApp, Facebook, live chat, forms, email and custom channels, with calling in beta, and that you can set its working hours and the percentage of conversations it handles (HubSpot Knowledge Base). For a school group, that means an agent can answer routine questions after hours and offer a visit, while a person takes every conversation about a specific child.
Keep with people: anything about a child's needs, wellbeing or assessment results, fee negotiations and scholarships, complaints, and every conversation with a family that is already unsure. An agent should make the admissions officer's first call better informed, not replace it. Our Customer Agent in practice piece sets out how we write handoff rules.
How do you connect the student information system?
The student information system stays the record for enrolled students, classes and grades. The CRM holds the relationship before enrolment and the family relationship after it. The two must agree: enrolment status flows back to the family record, so marketing can report on enrolments, not form fills, and admissions can see which families have siblings due to start. We design this as one integration with a named owner for each field. See our integration approach.
What about data protection for families?
Enrolment data is personal, and much of it is about children. Collect only what each stage needs, and keep assessment and wellbeing records in the systems built for them. In the Philippines, the Data Privacy Act treats information about an individual's education and health as sensitive personal information (National Privacy Commission). HubSpot hosts customer data in the EU, Canada, Australia and the United States (HubSpot), so for most groups in the region the CRM involves a cross-border transfer that should be documented. Our data protection answer covers the main laws.
What should an education group measure?
- Response time to new enquiries, by campus and channel.
- Enquiry to visit, and visit to application, by source.
- Offer acceptance, and the reasons families decline.
- Cost per enrolled student by marketing source, using real enrolment data.
- Siblings and referrals from current families.
Most groups can report the first measure. Few can report the last two, which is where the long-term value of a family sits.
How should marketing and admissions share the journey?
In many groups, marketing owns the enquiry and admissions owns everything after it. Each team reports its own numbers, and nobody owns the gaps between them. Marketing celebrates enquiries that admissions never converts. Admissions blames lead quality that nobody can check.
One shared journey ends that argument. Agree a shared definition of a qualified enquiry, for example a family with a child of the right age, a target intake and a campus they can reach. Agree how quickly admissions must respond, and what happens to enquiries that are not ready yet: a nurture sequence with campus news and open day invitations, rather than silence until the next intake.
Then report one funnel to the leadership team, from enquiry to first day, by campus and source. When both teams see the same numbers every week, the conversation moves from blame to fixing the stage where families drop out. For groups with several brands or school types, the same principle applies across brands; our multi-brand CRM piece covers the portal design.
Where to start
Pick one campus and one intake. Map the journey from enquiry to first day and mark where families drop out. Bring WhatsApp enquiries into the CRM, book visits from shared calendars, then connect enrolment status from the student information system. Add an agent for first answers once the content it needs is current.
