Case Study

Case Study: School Admissions & Parent Automation

We built a connected set of automations for an independent day school: an education CRM for enquiries, tours and open days, admissions document chasing and enrollment forms, an AI assistant that answers parents' routine questions from approved pages, and same-day attendance messages with reply logging. Admissions staff work from one pipeline and one checklist, the office answers fewer repeat questions, and the attendance officer starts each morning with a list of replies instead of a list of calls.

School type
Independent day school, primary and secondary
Team involved
Head, admissions team, school office, attendance officer, designated safeguarding lead
Systems connected
MIS through Wonde, CRM, website, Microsoft 365, Twilio, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Enquiries arrived by web form, phone, open-day sign-up and social messages, and admissions tracked them in a spreadsheet when time allowed.

Admissions spent weeks each year chasing reports, references and forms by email, and offer deadlines were tracked by hand.

The office answered the same questions about term dates, fees, uniform and transport many times a day, often for families who speak another language at home.

Same-day absence calls took most of the morning for one member of staff, and replies were recorded in the MIS by hand.

Goals

What the project had to change

  • Every enquiry lands in one pipeline with a quick reply and an owner.
  • Every application has a visible checklist, and families are reminded automatically.
  • Routine parent questions are answered from approved pages at any hour, in their language where approved.
  • Parents of absent pupils hear from the school promptly, and replies reach the attendance officer in one list.

What we built

What we built, as one connected system.

01

Education CRM

We connected web forms, open-day registrations, phone notes and social lead forms to one CRM pipeline with tour booking, follow-ups, call-back tasks and a weekly source report.

Service details
02

Admissions and enrollment

Each application now has a checklist, families get reminders with a secure upload link, assessments are booked online, offer deadlines are tracked and enrollment forms are collected before the first day.

Service details
03

AI assistant for parents

An assistant on the website answers term dates, fees, uniform, transport and admissions questions from approved pages, in several approved languages, and hands anything about a child or welfare to staff.

Service details
04

Attendance and parent messages

After registration, unexplained absences are read through Wonde, priority contacts get an approved message and replies are listed for the attendance officer, with an escalation list for families who do not reply.

Service details

Architecture

How the school's workflows connect

Website Forms and chat MIS via Wonde Register, contacts Applications Forms, uploads n8n Four services AI assistant Approved answers CRM pipeline Enquiries, offers Messages Text and email Office, admissions Lists, replies Safeguarding lead Welfare concerns Logs and reports Weekly summary
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Website forms and chat, applications and MIS register data feed one n8n instance.
  2. 2 The CRM holds enquiries and offers, the AI assistant answers routine questions and messages go to families.
  3. 3 Office and admissions staff work from shared lists; welfare concerns go straight to the safeguarding lead.
  4. 4 Every step is logged, and a weekly summary shows the measures the school agreed to track.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What families see

  • A quick reply and a tour booking link after enquiring
  • A clear list of documents still needed, with an upload link
  • Answers to routine questions at any hour
  • A same-day message if their child is absent without a reason

What staff see

  • One enquiry pipeline and one admissions checklist
  • Hand-offs from the assistant with the conversation
  • A morning list of absence replies and an escalation list

What the automation does

  • Captures, reminds and chases on schedule
  • Answers only from approved information and routes sensitive topics
  • Logs every step and alerts the office manager if anything fails

Edge cases and fallbacks

A parent raises a welfare concern in chat
No AI answer; the safeguarding contact route is shown and the designated safeguarding lead is alerted.
A contact restriction is recorded for a pupil
Only permitted contacts are messaged, using MIS flags agreed at discovery.
An offer deadline passes without reply
Admissions is alerted; nothing is withdrawn automatically.
The register is taken late
Absence messages wait for the agreed cut-off.
Twilio, Wonde or n8n has an outage
The office returns to phone calls and email, and the office manager gets an alert.

Integrations

What we connected

All integrations

Wonde

MIS data platform (UK)

Students, contacts, attendance and write-back of attendance marks where the MIS supports it.

Wonde API, with webhooks for write-back status.

HubSpot

CRM

Families, learners, employers, enquiries and follow-ups.

HubSpot CRM REST API.

Twilio

SMS

Absence messages, reminders and replies.

Twilio Programmable Messaging API, with A2P 10DLC registration in the US.

Microsoft 365 and Teams

Email, storage and alerts

Inboxes, document storage and staff alerts.

Microsoft Graph API and Teams webhooks.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We sat with admissions and the office, mapped enquiry, admissions, parent question and attendance steps, agreed data flows with the data protection lead and confirmed Wonde access.

  2. 02

    Design and access

    Week 2

    Pipeline stages, checklists, message wording approved by the head, safeguarding hand-off wording signed off by the designated safeguarding lead, and Twilio A2P 10DLC registration where US numbers were used.

  3. 03

    Sprint 1: CRM pipeline

    Week 3

    Built and shadow-ran the enquiry pipeline and tour booking; demo and sign-off.

  4. 04

    Sprint 2: admissions

    Week 4

    The pipeline went live. Built the application checklist, uploads and offer tracking.

  5. 05

    Sprint 3: attendance

    Week 5

    Admissions went live for the next intake. Built absence messages and the reply list; messages went to a test phone.

  6. 06

    Sprint 4: AI assistant

    Week 6

    Attendance messages went live. Built the assistant and answer library with the office.

  7. 07

    Sprint 5: testing the assistant

    Week 7

    Ran real, tricky and sensitive prompts; the safeguarding lead signed off the hand-offs.

  8. 08

    UAT and handover

    Week 8

    Staff ran user acceptance testing on every workflow, then we launched the assistant on admissions pages, handed over the run book and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during the first half term, then termly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures enquiries and books tours
  • Checks applications and chases missing documents
  • Answers routine parent questions from approved pages
  • Sends same-day absence messages and collects replies
  • Sends reminders for deadlines, trips and forms

The team does

  • Admissions calls families and runs tours and assessments
  • The office replies to assistant hand-offs
  • The attendance officer records reasons and calls families with no reply

Head of school or programme lead decides

  • The head and admissions panel decide every offer and bursary
  • The designated safeguarding lead handles every welfare concern
  • Leaders approve all wording sent to families

Compliance handled

Privacy, consent and safety, built in.

No AI admissions decisions

AI is not used to score or rank applicants; the EU AI Act lists AI that determines admission as high-risk.

Source: artificialintelligenceact.eu

Children's data and consent

Forms and the assistant are for parents; UK GDPR Article 8 sets 13 as the age for a child's own consent to online services.

Source: www.legislation.gov.uk

Lawful basis recorded

The school recorded its UK GDPR Article 6 lawful basis for each workflow before go-live.

Source: www.legislation.gov.uk

AI disclosure

The assistant says it is automated and offers a person, in line with EU AI Act Article 50 from 2 August 2026.

Source: artificialintelligenceact.eu

Safeguarding first

Welfare concerns are never answered by AI and always reach the designated safeguarding lead.

Outcomes

What changed for the practice

  • Every enquiry lands in one pipeline with a quick reply and an owner.
  • Admissions works from one checklist per application, and families are reminded automatically.
  • Routine parent questions are answered from approved pages at any hour.
  • Parents of absent pupils hear from the school promptly, and the attendance officer starts the day with a list of replies.
  • Sensitive questions reach the right person faster because routine ones no longer queue in front of them.

What we track

The measures the practice watches.

Enquiry response

Time to first reply and tours booked by source.

Application completeness

Applications complete by the deadline and time spent chasing documents.

Assistant coverage

Questions answered without a hand-off and gaps found in the weekly review.

Absence follow-up

Time from register close to message sent and absences explained by a set time.

Enrollment readiness

Enrollment forms complete before the first day.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, data flows, wording and the backlog for all four services.

    $900 – $2,000

  • CRM pipeline module

    Source capture, tour booking, follow-ups and report.

    $700 – $1,600

  • Admissions module

    Checklist, uploads, booking, offers and enrollment forms.

    $800 – $2,000

  • AI assistant module

    Answer library, assistant, hand-offs and testing.

    $1,800 – $4,500

  • Attendance module

    Absence check, messages, reply list and escalation.

    $700 – $1,700

  • Integrations

    Wonde, CRM, Microsoft 365 and Twilio connections.

    $300 – $500

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $300 – $1,200

  • Total project estimate

    $5,500 – $13,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: three workflows and one AI assistant at our fixed ranges. Every school gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing), plus A2P 10DLC registration fees.
  • n8n: Self-hosted Community edition on the school's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • CRM and Wonde: Each vendor's own plan.
  • AI usage: Pay-per-use model fees, usually small at school volumes.

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
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 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. 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. 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. 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

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

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

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built 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.

Book a free 20-minute call