Parent-Communication AI Agent

What this agent does

Sends the message, not the notice

Ingest contacts, enrollment status, language preferences and restriction flags from supported SIS.

Normalise households and contact roles, and carry each recipient forward with the record that authorises them.

Reason

Re-check entitlement before every send: rights pass to the student at majority or on entering postsecondary study.

Check each recipient against custody orders, protective orders and safety plans, and fail closed on a stale flag.

Apply the district's message categories, consent records and opt-outs, and honour a revocation across all of them.

Decide

Hold any notice that carries a legal consequence — discipline, special education, a deadline — for a person to release.

Route a family's language need to a qualified human translator.

Out

Retain the rights check, the recipient list, the release and the delivery record against the message.

Execute write actions only inside the approval boundaries agreed during implementation.

→ Product statement

The agent sends routine notices to cleared contacts; a person decides who is entitled to a record, and what an operative notice says.

Example workflow

One message, request to delivery

AgentHuman

1Message requestedAttendance event, calendar change, staff request or special-education workflow

2Entitlement assembledHousehold contacts, entitlement status, restriction flags and language preference, each with its source

3Message preparedCategory, recipient list, language route and confidence

4Rights checks runEntitlement re-check, restriction and safety-plan check, category and consent rules, and confidence threshold

No human action required

Nothing is sent in the first four stages, and no recipient is cleared by the agent alone — the release lane opens at the confidence gate.

5DecisionSplits on the rights check

Recipient confirmed

Goes to the named staff member to release.

Recipient in doubt

Adds a records-office check first.

Staff release

The message is held with its recipient list, the checks it passed and the confidence.

Release · Correct · Send to the records office

Released — delivery recorded▼

6Notification systems updatedOnly where write access and contact policy allow it

7Delivery evaluatedEntitlement misses, restriction breaches, opt-out compliance and errors found after delivery

Recalls

Every staff correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Deciding whether a parent may receive an adult student's record.

Determining a student's tax-dependency status.

Resolving a custody, protective-order or contact-restriction question.

Making a health-or-safety emergency determination.

Automation boundaryAgent acts unaided

✓Send closure, delay and schedule-change notices to cleared contacts.

✓Send unexcused-absence notifications inside.

✓Confirm event responses and conference bookings.

✓Answer published calendar, bell-schedule and transport questions.

Any send happens inside the boundaries agreed at implementation, never ahead of the rights check.

Authoring or approving special-education prior written notice.

Approving the translation of a legally operative notice.

Making a mandated child-abuse or neglect report.

Communicating a disciplinary outcome or its appeal rights.

Example output

One outbound message, annotated

Everything the agent prepares is attached to the record that authorised it.

Communication output · single messageIllustrative example

Message

What it says

Recipients cleared

Source of record

Confidence

Language route

Early dismissal

Your child's day ends early on Thursday and the bus runs to the altered timetable

One guardian, one held

SIS contact record, current

93%

Qualified translator queued

As receivedTaken from the contact record and the restriction flags on file.

Checks used Entitlement status on file Custody and safety flags Language preference on file

Why this recipientOne guardian is cleared and one is held by an order and a person still decides.

ActionReleaseCorrectSend to the records office

What the score decidesBelow the configured threshold the message picks up a records-office check before anyone.

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value landsValue 01 – 04

Every outbound messageFrom the contact record

03Preparation

Prepare from the record

Getting the recipient wrong is not a paperwork problem — it is a child's schedule or location reaching an adult a court has excluded.

01Approved path

Reach the guardian who matters

Routine closures, schedule changes and absence notices go out already checked.

02Human review

Send staff where the risk is

Restricted households, transferred rights and language needs are marked, so staff time goes to the sends that can do harm.

04Build an evidence trail

Each message keeps the rights check behind it and who released it.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

Notification platformsParentSquare · Remind
Blackboard Connect · SchoolMessenger

Student information systemsPowerSchool SIS
Infinite Campus

Classroom communicationClassDojo
Seesaw

Agent

Parent communication

Reads the record
Prepares the message
Holds for release

Special educationFrontline Special Education
PowerSchool Special Programs

Observability & evaluationOpenTelemetry · Langfuse
Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the send

Each wraps the last. The map below names what each one lets through.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modeHold every send and queue it for a person when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt, category-rule and contact-configuration changes.Track

L4TraceabilityRecord the checks, the recipient list, the release and the delivery time.Record

L3Staff releaseHolds the message for a named person; it governs who releases, not whether a delivered message can be taken back.Gate

L2Policy guardrailsTest each send against entitlement, restriction flags, category and consent rules; a failure returns the message.Restrict

L1Confidence thresholdsRoute low-confidence recipient lists to a records-office check before release.Require review

Model coreMessage prepared — category, recipient list, language route and confidence

L1 – L2Test whether a message may stand

L3Puts the release in a person's hands

L4 – L5Preserve who was told what, and on what basis

L6Holds sends and queues them for a person

How Nestack evaluates it

Evaluate the whole send path — not only the message that lands.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the message the family receives

Depth of coverage ▼

E1Final-output evaluationDid every recipient clear the entitlement and restriction checks?

E2Step-level evaluationDid the agent use the right contact record, flags and language preference?

E3Tool evaluationDid it read the correct household and write to the correct delivery log?

E4Confidence calibrationDo low-confidence recipient lists actually attract more staff corrections?

E5Slice evaluationHow far apart do error rates sit across specific household types?

E6Business outcomeHow many messages were corrected, and how many were caught only after delivery?

Floor — the message the family receives

Failure modes

Where each failure originates in the agent

Seven modes across the delivery lifecycle.

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

GD-03

Cached contact list

A list that predates a restriction flag includes the held parent.

Stage gathersContacts, entitlement status, with the source each came from

02 · Reasoning2 modes

GD-04

Transfer of rights missed

A dual-enrolled minor is treated as covered by parental rights.

GD-06

Category misread as urgent

An engagement campaign goes out as attendance messaging.

Stage proposesThe category, the recipient list and confidence

03 · Tool / write2 modes

GD-02

Machine-translated notice sent

A suspension notice goes out translated, its deadline wrong.

GD-05

Message reads as formal notice

A meeting summary starts a safeguards clock nobody authorised.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

GD-01

Reply reads as closure

A parent's safety disclosure is answered, and no person is paged.

Stage returnsThe message the family reads and acts on

05 · Change / Version1 mode

GD-07

Opt-out preferences reset

A platform upgrade resumes messaging to families who revoked.

Stage tracksModel, prompt, category rules and contact config

Sev-1 · a held adult receives a child's Sev-2 · an operative notice goes out unverified Sev-3 · contact data degrades

See the complete Education failure-mode catalogue →

Affected slices

A low average over a very uneven set

The baseline is the error rate across every message the district sends, and it is low. Three cohorts sit several times above it Nestack reports it by slice rather than in aggregate..

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
Households with a restriction on file	7.0%	3.9×	Review
Notices to families with a language need	6.1%	3.4×	Review
Students whose rights have transferred	2.7%	1.5×	Watch
Routine notices to cleared contacts	0.9%	0.5×	Normal

Bar: error-rate lift vs. the all-message baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

A coordinator cannot close a cycle

A cycle is finished when the failure sits in the suite as a case the next release must pass.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Error rate rises in one household cohort.

02Diagnose

The sends, the contact history and the flag version are read together until one of them explains it.

03Improve

The correction carries its version and the messages behind it.

04Verify

The affected cases are re-run before anything ships.

05Learn

It lands in the permanent suite and in the contact rules.

Learn → DetectThe return edge. Every later detection runs against the longer suite.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, contacts, message workflow, evaluation, integration, then production validation and handover.

Workstream Week 1Week 2Week 3Week 4Week 5Week 6

01Communication workflow discovery and scope.

02SIS and notification-platform assessment.

03Entitlement, restriction and message-category mapping.

04Contact ingestion and household resolution.

05Message assembly and rights-check.

06Confidence scoring and release routing.

07Staff release workflow.

08Notification- and SIS-platform integration.

09Delivery regression cases.

10Guardrails and rights controls.

11Delivery-trail instrumentation.

12Deployment, documentation and Agent Care handover.

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tier PilotOne school, one message set ProductionProduction notification systems AdvancedMultiple schools / districts

Introduced at Pilot

Messages to your contact rules✓✓✓

Staff release✓✓✓

Delivery baseline✓✓✓

Introduced at Production

Reporting by household—✓✓

Release workflow in your systems—✓✓

Approved write-back—✓✓

Notification-platform integration—✓✓

Introduced at Advanced

Multi-district and multi-state rules——✓

Multi-stage release approvals——✓

High message volume——✓

Enterprise contact controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, message volume, release controls and deployment requirements.

Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

You bringWe build with it

01Your contact records and where restrictions live → Entitlement and restriction mappingWeek 1

02Representative sends from a past term → Delivery baseline, household normalisation and rights-check bindingWeek 2

03Your message categories and consent records → Entitlement, restriction and message-category mappingWeek 1

04Access to relevant APIs, feeds or exports → SIS, notification and special-education assessment, then integration setupWeek 2

05Messages that reached the wrong adult → Delivery cases and failure-mode testingWeek 4

06Which messages may never send without a rights check → Confidence scoring, release routing, guardrails and rights controlsWeek 3

07Named staff to release held messages → Staff release workflow, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Phases sit where the work is, which is why week 5 holds evaluation and pilot at the same time.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Communication workflow discovery, contact mapping and the automation boundary W2Contact integration and the delivery baseline W3Message workflow, confidence logic and rights controls W4Evaluation suite, restriction checks and failure-mode testing W5Platform integration, a pilot term and targeted corrections W6A term of family communication under the school, then handover

Reading the bandBands cover the weeks their work is named in and no more. The doubled fifth week is real, not padding.

At the end of W6Everything verified on live sends, with Agent Care carrying it forward.

DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Education AI agent

Build a communication agent around your district's contact rules.

Show us your notification platform, your contact records and where custody restrictions are held. If your protective-order flags sit somewhere the messaging platform never reads, that is the first thing to fix; then we map the routing, set the automation boundary and name what stays with a person.

Discuss this agent →

Nestack Agents · Parent communicationAGT-ED-05 · Agent Care available after launch