A field guide for the front office

AI for School Operations

Fifteen things a charter front office can hand to a machine — and the rules that keep families, and your data agreement, intact.

You get the guide, then three short notes — one a morning for three mornings. One click stops them, and no part of this is a newsletter.

What is in it

Part one

Decide what to automate

  • Count what you repeat
  • Automate the chase, not the decision
  • Give every sequence an exit
  • Chase documents as their own job
  • Flag the students who need a person
Part two

How it should talk to families

  • Use the student’s full name
  • Use a keypad, not a voice bot
  • Translate the channel, not the text
  • Ground the answer, or flag it
  • Say your own number out loud
Part three

How to stay out of trouble

  • Split consent three ways
  • Make stop granular, and permanent
  • Log it in plain language
  • Test the change before you save it
  • Sign the data agreement first

Who wrote it

Ashley Kerremans ran school operations before she co-founded AskElira, and Alvin Kerremans builds the product. It is written for the person who actually calls down the waitlist in August, not for a procurement committee.

It opens with the case for doing any of this at all — why a slow reply is not a neutral act, and what actually changed about these tools. AskElira does about ten of the fifteen. We say which ones, and where.