Education CRM automation for school and course enquiries
Enquiries reach a school or training provider through web forms, phone calls, open-day sign-ups, social messages and agents, and many are tracked in a spreadsheet or not at all. We connect every source to one education CRM pipeline, usually HubSpot or the admissions CRM you have, book tours and taster sessions, automate polite follow-ups and report weekly on enquiries, visits and applications by source. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.
The problem
Why schools lose family enquiries
For an independent school, a college or a training provider, each enquiry is a family or learner deciding where to spend years or a significant fee. They often contact several places at once, and the one that replies quickly and clearly gets the visit.
Admissions teams are small and busy with tours, assessments and current families. Without one pipeline it is hard to say how many enquiries came in after the open day, who has not been called back or which advert brought families who applied.
What we build
What our education CRM automation includes
Every enquiry in one place
Website forms, open-day registrations, phone notes, social lead forms and agent referrals flow into one CRM pipeline.
Stages that fit admissions
Enquiry, information sent, tour or taster booked, visited, application started, applied, offered and enrolled, adapted to your process.
Tour and open-day booking
Families and learners pick a slot online and get reminders, with staff notified of each booking.
Polite follow-ups
A first reply within minutes and a couple of helpful follow-ups, stopping when the family replies or books.
Tasks for admissions staff
Call-back tasks with due dates so no enquiry waits untouched.
Source reporting
A weekly email with enquiries, visits and applications by source, year group or course.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Enquiry arrives
A form, call, event sign-up or social lead creates or updates a contact in the CRM.
-
02
Automated
First reply
The family or learner gets an approved reply with a tour or taster booking link.
-
03
Automated
Stage moves
Bookings, visits and application starts move the record along automatically.
-
04
Staff review
Admissions follows up
Admissions staff call, answer questions and record the outcome.
-
05
Head of school or programme lead decides
Places and offers
Offers, bursaries and places are decided by the head of admissions and the school, never by the CRM.
How it behaves
How the enquiry pipeline behaves
What families and learners see
- A quick, helpful reply after they enquire
- An easy way to book a tour, open day or taster
- A couple of follow-ups at most, stopping once they book
What admissions staff see
- One pipeline with every enquiry and its stage
- Call-back tasks and tour lists
- A weekly report by source
What the automation does
- Captures and de-duplicates enquiries
- Sends approved follow-ups with stop rules
- Never makes or hints at an admissions decision
Edge cases and fallbacks
- Siblings enquire in one form
- One family record with a separate entry per child.
- Current family enquires about a sibling
- Flagged to admissions instead of treated as a new lead.
- No marketing consent ticked
- Gets the enquiry reply only; no newsletters.
- CRM or form outage
- Enquiries are queued and retried, and admissions is alerted.
Architecture
An education CRM pipeline at a glance.
- Input
- Logic and services
- Data
- Output
- People
How it flows
- 1 Enquiries arrive from web forms, open-day sign-ups, calls and social lead forms.
- 2 n8n captures each one, removes duplicates and creates or updates the family or learner in the CRM.
- 3 Approved follow-ups and booking links go out, and admissions staff get call-back tasks.
- 4 A weekly report shows enquiries, visits and applications by source.
Project planner
How the project runs, phase by phase.
Education CRM & enquiry pipeline project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Enquiry sources, admissions stages, current tracking, CRM choice and reporting needs.
-
02
Design
2 to 3 days
Stages, follow-up rules, consent wording, field mapping and duplicate rules.
-
03
Build
1 to 2 weeks
Source connections, pipeline, tour booking, follow-ups and report.
-
04
Shadow run
About 1 week
Enquiries flow into the CRM while admissions keeps its old process, and we compare.
-
05
Launch
1 to 2 days
Switch over and train the admissions team.
-
06
Support
Ongoing
New sources, intake changes and report tweaks.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Sources, stages, consent and reporting.
$200 – $400
-
Build
Capture, pipeline, tour booking and follow-ups.
$500 – $1,300
-
Integrations
CRM, forms, lead forms and messaging.
$150 – $400
-
Testing and shadow run
Side-by-side run with current tracking.
$100 – $250
-
Launch and training
Switch-over and admissions training.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM, messaging and n8n are billed to you directly. Agent portals or a link to your SIS may need a second workflow.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- CRM subscription: Your CRM vendor's own plan.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
UK: lawful basis for processing
UK GDPR Article 6 sets the lawful bases, including tasks carried out in the public interest, which state schools often rely on; independent schools and providers usually use others. We record which one applies before go-live.
Source: www.legislation.gov.ukUK: marketing emails and texts
PECR regulation 22 covers unsolicited marketing by electronic mail, so newsletters and promotions only go to families who agreed, separate from replies to their enquiry.
Source: www.legislation.gov.ukUS: marketing texts need consent
Telemarketing texts to mobile numbers sent with an autodialer need prior express written consent, so follow-up texts only go to families who opted in.
Source: www.law.cornell.eduFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Education CRM & enquiry pipeline questions, answered.
An education CRM tracks prospective families or learners from first enquiry to enrollment. The SIS or MIS holds enrolled students; the CRM holds the admissions pipeline and hands over cleanly once a student enrolls.
Some schools use admissions-specific platforms; others do well with HubSpot because it is flexible and has a documented API. We help you choose based on your intake, systems and budget, and we can build on what you already pay for.
Yes. For training providers the stages become enquiry, course information sent, booked, paid and started, and employer clients can be tracked as companies with several learners.
The CRM covers enquiries to application. Our admissions and enrollment service handles documents, offers and enrollment forms, and the two connect.
No. Each sequence has a few messages at most, stops when they reply or book, and respects opt-outs across every workflow.
Enquiries by source, time to first reply, tours booked and attended, applications started and completed and enrollment by source. We set these up from day one.
Free 20-minute call
Want this for your schools & training?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for schools & training
All servicesAdmissions documents, offers & enrollment
Applications checked for missing documents, reminders sent to families, assessment and interview slots booked, offer and acceptance steps tracked and enrollment forms collected before the first day.
From $1,000 · About 4 to 5 weeks Details
AI assistant for parents & learners
An AI assistant on your website and help inbox that answers term dates, fees, uniform, transport, course and policy questions from your approved information, in several languages, and passes anything personal or sensitive to staff.
From $2,500 · About 5 to 8 weeks Details
Attendance alerts & parent communications
Same-day absence messages to parents from your MIS or SIS, replies logged for the attendance officer, trip and payment reminders, and routine notices sent in each family's preferred language and channel.
From $1,000 · About 4 weeks Details