Enquiries, registrations and waitlist status move between Enrol HQ and HubSpot, so marketing can see which campaigns lead to enrolments.
A custom-built integration designed around your business logic, not a plug-and-play connector.
Enrol HQ holds your enquiries, tour bookings, registrations and waitlist. Your marketing team runs campaigns, forms and paid ads in HubSpot. Without a connection, nobody can say which campaign produced which enrolment.
Enquiries captured on your website sit in HubSpot while the enrolments team works in Enrol HQ. Families end up in two places with two different histories.
If your enquiry record is split across two systems, neither team has the full picture.
Enrol HQ stays the source of truth for enquiries and registrations. HubSpot owns campaigns, forms and nurture communications.
A shared record ID links each family across HubSpot and Enrol HQ, so each sync updates the same record.
Enquiries captured in Enrol HQ, including form submissions, phone enquiries and tour bookings, sync to HubSpot contacts and families.
Registrations and waitlist status sync to HubSpot with the intended entry year and year level. Your team can nurture families by stage.
Enquiries captured through HubSpot forms, landing pages and paid lead ads are written to Enrol HQ, so the enrolments team keeps a complete record.
With registrations in HubSpot, marketing can report from first campaign touch to enrolment.
If your school uses Enrol HQ for admissions and HubSpot for marketing, this integration connects them. It also works alongside a school management system such as TASS, with one record ID across all three.
Writing enquiries back to Enrol HQ depends on the API access your Enrol HQ account provides. We confirm this during scoping.