Every fall, admissions offices get buried. Application status questions. Financial aid deadlines. “Did you receive my transcript?” Transfer credit questions. The same fifteen questions, thousands of times, concentrated into about ten weeks a year.
It’s the exact shape of problem voice AI is good at. So it’s strange how few admissions offices have it.
The reason isn’t budget. It’s the record.
The moment a caller asks “what’s the status of my application,” you’re not answering a general question anymore. You’re disclosing information from an education record. In the US, that’s covered by FERPA — the Family Educational Rights and Privacy Act — and it works a lot like HIPAA does for health data: the institution is responsible for who it discloses records to, verified or not, human or automated.
Most voice AI vendors pitching admissions offices never mention this. They demo the happy path — a prospective student asks about deadlines, the bot answers, everyone’s impressed — and never touch the harder case: a caller asking about a specific student’s status, without any way to verify they’re allowed to hear the answer.
Why this trips up generic stacks
A voice AI built the fast way — LLM API, off-the-shelf TTS, no real identity layer — treats every caller the same. It doesn’t distinguish “what documents does the application require” (public, answer freely) from “has my daughter’s file been reviewed” (protected, verify first). Get that distinction wrong once, at the wrong time, with the wrong caller, and the school has a FERPA problem, not a customer service win.
This is the same lesson we wrote about with HIPAA and healthcare voice AI: the stack that’s good enough for a demo is rarely good enough for a regulated record. FERPA just changes which record.
What we built differently for this segment
Optima Voice splits admissions calls into two lanes. Anything without a specific student attached — deadlines, required materials, office hours, general financial aid process — the AI agent answers directly, no verification needed, any time of day. Anything that touches an individual record — status, decisions, aid amounts — routes to a verification step or a human, the same way we treat PHI in the healthcare deployments: don’t disclose it if you can’t confirm who’s asking.
That split isn’t a feature we bolted on. It’s the same compliance-first architecture — AWS end-to-end, tenant isolation, least-privilege access — that we built for healthcare and government customers, applied to a different regulation. One platform, a different record type to protect.
Why this is the segment nobody talks about
Healthcare and government get the compliance attention because the penalties are loud. Education offices don’t get the same scrutiny, so most AI vendors treat admissions like any other small-business receptionist problem — book the meeting, answer the FAQ, move on. That gap is exactly why it’s worth building correctly: the institutions that ask the FERPA question first are the ones still using it in three years.
If you’re evaluating voice AI for an admissions office, ask the vendor one question before anything else: how does it decide when to verify a caller before answering? If the answer is “it doesn’t,” that’s the whole conversation.
Oleksii Kocherev
CEO, Optima Voice
AI Voice Agents for Business, Education & Government
Originally published on Medium.