Fixed quote after a free call

Parent communication and attendance alerts that run on time

Every morning someone in the office checks the register and calls or texts families of absent pupils, then chases replies. We build a workflow that reads unexplained absences from your MIS or SIS, sends an approved message to the right contacts, logs replies for the attendance officer, and adds trip, payment and event reminders in each family's preferred language and channel. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why same-day absence calls eat the school morning

Same-day absence follow-up matters for safety and for attendance, yet it depends on a busy office getting through a list of calls before mid-morning. Replies come back by text, email and phone and have to be recorded in the MIS by hand.

Routine notices have a similar problem. Trip consent, payment deadlines and event reminders go out in one language by one channel, and families who miss them are chased individually.

What we build

What our parent communication automation includes

Absence check

Unexplained absences read from the register after it closes, through Wonde, Clever, OneRoster or your SIS.

Same-day messages

An approved text or email to the priority contacts for each absent pupil.

Reply logging

Parent replies collected in one list for the attendance officer to record, with write-back where your MIS route supports it.

Escalation list

Pupils with no reply by a set time listed for staff to call, following your attendance and safeguarding policy.

Reminders and notices

Trip, payment and event reminders by each family's preferred channel, with a link to the consent or payment form.

Language preferences

Routine notices in the family's recorded language, from wording the school approves.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Register closes

    Unexplained absences are read from the MIS or SIS.

  2. 02 Automated

    Parents messaged

    Priority contacts get an approved same-day message.

  3. 03 Automated

    Replies collected

    Replies are gathered for the attendance officer.

  4. 04 Staff review

    Office records

    Staff record reasons and call families with no reply.

  5. 05 Head of school or programme lead decides

    Welfare concerns

    Any concern about a child's welfare is handled by the designated safeguarding lead.

How it behaves

How attendance alerts behave

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

What parents see

  • A same-day message when their child is absent without a reason
  • A simple way to reply
  • Reminders and notices in their preferred language

What the office sees

  • One list of replies to record
  • An escalation list of families with no reply
  • Forms and payments returned against each trip or event

What the automation does

  • Reads absences after the register closes
  • Sends approved messages to priority contacts
  • Never closes an absence case by itself

Edge cases and fallbacks

Contact details missing or wrong
Pupil goes straight to the call list.
Court order or contact restriction recorded
Only permitted contacts are messaged, read from the MIS flags agreed at discovery.
Register taken late
The run waits for a set cut-off rather than messaging early.
MIS, Twilio or n8n outage
The office calls as before and gets an alert.

Architecture

Attendance alerts and parent messages at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
MIS or SIS Register, contacts n8n workflow After registration Parent messages Text or email Reply list Reasons given Attendance officer Records, calls
  • Input
  • Logic and services
  • Output
  • Data
  • People

How it flows

  1. 1 After the register closes, unexplained absences and contacts are read from the MIS or SIS.
  2. 2 Priority contacts get an approved message by their preferred channel.
  3. 3 Replies are collected into one list, with write-back where the MIS route allows.
  4. 4 The attendance officer records reasons and calls families with no reply, following school policy.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Attendance alerts & parent communications project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Attendance process, MIS or SIS access, contact priorities, languages and channels.

  2. 02

    Design

    2 to 3 days

    Message wording, timing, escalation rules and reply handling.

  3. 03

    Build

    1 to 2 weeks

    Absence check, messages, reply list, reminders and language rules.

  4. 04

    Shadow run

    About 1 week

    Messages go to a test phone while the office runs its usual calls.

  5. 05

    Launch

    1 to 2 days

    Switch on, ideally at the start of a half term.

  6. 06

    Support

    Ongoing

    Wording changes and new notice types.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Wonde API (UK MIS data and attendance write-back where supported) Clever or OneRoster for US rostering Twilio SMS and your email provider Stripe Payment Links for trip payments

Cost estimate

What it costs, line by line.

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

    Attendance process, wording and escalation rules.

    $200 – $400

  • Build

    Absence check, messages, reply list and reminders.

    $500 – $1,300

  • Integrations

    MIS or SIS route, messaging and payments.

    $150 – $400

  • Testing and shadow run

    Test messages alongside the office's usual calls.

    $100 – $250

  • Launch and training

    Switch-on and office walkthrough.

    $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. Attendance write-back depends on your MIS route. Messaging, data platform and n8n costs are billed to you directly.

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). A2P 10DLC registration also applies.
  • MIS data platform: Your Wonde, Clever or SIS plan where applicable.
  • 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
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: FERPA and service providers

Attendance is part of education records. A provider can act as a school official only if it performs an institutional function and is under the school's direct control for using and maintaining records.

Source: www.govinfo.gov

UK: lawful basis

UK GDPR Article 6 sets the lawful bases for processing; the school records which applies to attendance messages before go-live.

Source: www.legislation.gov.uk

US: texting families

Messages are informational and go only to recorded contacts; anything promotional needs prior express written consent and runs separately.

Source: www.law.cornell.edu

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.

FAQ

Attendance alerts & parent communications questions, answered.

It is a set of workflows that use your MIS or SIS and the channels you already have. If you already use a parent communication app, we connect to it and automate what it does not.

After the register closes, the workflow reads unexplained absences and sends your approved message to the priority contacts. Replies are collected for the attendance officer.

Where the route supports it, such as Wonde attendance write-back for supported MIS platforms, yes after staff confirm. Otherwise replies are listed for staff to record.

They go to an escalation list at a set time for staff to call, following your attendance and safeguarding policy. The workflow never closes a case by itself.

Yes. Families' recorded language preferences decide the version they get, from wording the school approves.

Time from register close to message sent, share of absences explained by a set time, calls made by staff and payment or consent forms returned on time.

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.

Book a free 20-minute call