---
title: "FERPA, TCPA and AI Admissions Agents: US Contact Rules"
description: "FERPA TCPA AI chatbot admissions: what US colleges need to know on consent, AI voices, opt-outs and student records before an agent contacts applicants."
url: "https://www.skolbot.ai/en-US/blog/ferpa-tcpa-ai-agents-contacting-applicants-us"
language: "en"
dateModified: "2026-11-18"
---

# FERPA, TCPA and AI Admissions Agents: US Contact Rules

Updated on November 18, 2026

FERPA TCPA AI chatbot admissions: what US colleges need to know on consent, AI voices, opt-outs and student records before an agent contacts applicants.

## The short answer: FERPA and the TCPA answer different questions

FERPA decides who may see a student's education records. The Telephone Consumer Protection Act (TCPA) decides whether you may call or text a phone number, and with what permission. An AI agent in admissions touches both, but at different moments: the TCPA when the agent reaches out, FERPA once the person becomes a student.

This guide is for enrollment, marketing and compliance teams at US colleges. It is not legal advice, and no article can replace your general counsel and registrar. We stick to what the primary texts say as of November 18, 2026, and we flag what is about to change.

## Where an AI agent sits in the contact flow

A chat widget on your own website is the least risky place for an AI agent, because the visitor opens the conversation. The TCPA question begins when you take a phone number and then send a text, place a call or schedule an automated follow-up. That follow-up is where consent, wording and opt-out handling have to be right.

| Moment | Main US rule to check | Typical owner |
|---|---|---|
| Prospect chats on your site | Your privacy notice; state privacy law | Marketing / counsel |
| Agent asks for a mobile number | Consent language shown at that moment | Counsel |
| Text or call sent afterwards | TCPA consent and opt-out | Counsel / admissions ops |
| Voice call using an AI voice | TCPA rules on artificial voices | Counsel |
| Admitted student shares records | FERPA | Registrar |

The rest of this article takes each row in turn.

## TCPA: what the FCC rule text says

The FCC's calling rules are in [47 CFR 64.1200](https://www.law.cornell.edu/cfr/text/47/64.1200). Paragraph (a)(1) bars initiating a telephone call using "an automatic telephone dialing system or an artificial or prerecorded voice" unless it is an emergency call or has the called party's prior express consent. For calls that include an advertisement or constitute telemarketing, paragraph (a)(2) raises the bar to "prior express written consent".

The same section defines that term as an agreement, in writing, bearing the signature of the person called, that clearly authorizes the seller to deliver advertisements or telemarketing messages and names the telephone number. Do not assume a pre-checked box meets that standard; ask counsel to approve the exact form.

What does this mean for an admissions office? An informational reminder about a campus tour the student requested and a promotion for a scholarship event are not the same category. The first generally needs consent; the second sits in the written-consent tier. Keep the two consents, and the two sets of wording, separate.

## AI voices count as artificial voices

The FCC has said so directly. In the Federal Register notice for its proposed AI rules, the agency states that it "has recently confirmed that the TCPA's restrictions on the use of 'artificial or prerecorded voice' encompass current AI technologies that resemble human voices". The practical consequence: a voice agent that calls prospects needs the same consent a prerecorded call would need, and a friendlier voice does not change that.

The same [2024 notice](https://www.federalregister.gov/documents/full_text/text/2024/09/10/2024-19028.txt) is a proposal, not a final rule. It would define an AI-generated call as "a call that uses any technology or tool to generate an artificial or prerecorded voice or a text", and require callers to disclose the use of AI at the start of a call. We did not find a final rule adopting those proposals in the Federal Register search we ran for this review, so treat them as pending and ask counsel whether anything has changed since.

Even without a final disclosure rule, telling a prospect they are talking to an AI is good practice. It protects trust, and it makes the consent you collected easier to defend, because the person knew what they agreed to.

## Revoking consent: the rule changes on November 25, 2026

The rule text published in the eCFR says a called party "may revoke prior express consent, including prior express written consent" by "any reasonable method" that clearly expresses a desire not to receive further calls or texts. Replies using words such as "stop," "quit," "end," "revoke," "opt out," "cancel" or "unsubscribe" count per se. Requests must be honored within a reasonable time "not to exceed ten business days", and callers may not designate an exclusive means to request revocation.

That text is changing. On October 26, 2026 the FCC published an order, effective November 25, 2026, that according to the Federal Register abstract [modifies the revocation rules](https://www.federalregister.gov/documents/full_text/text/2026/10/26/2026-21821.txt). Among other things, it lets callers treat a revocation as covering only the category of informational robocall it targeted, and lets callers set an exclusive revocation method. Revoking consent to telemarketing messages still covers all future telemarketing of that type from the same caller.

A companion document published the same day asks for comment on further changes, including shortening the time to honor revocations and requiring two-way texting. Comments were due November 25, 2026, and reply comments December 28, 2026. Those proposals are not rules.

Two operational points hold whichever version applies:

- **Wire the opt-out into everything.** If a student replies "stop" to the AI agent, the CRM, the nurture sequences and any other texting tool must all see it. A suppression list that lives in one system is the usual failure.
- **Do not make the student fight the bot.** An agent that answers "stop" with another question is a revocation problem waiting to happen. Treat reasonable opt-out language as a hard stop.

## FERPA: who is protected, and when

FERPA protects students. The Department of Education's [Student Privacy site](https://studentprivacy.ed.gov/ferpa) points to the regulation: a student is "any individual who is or has been in attendance at an educational agency or institution". Education records are records directly related to a student and maintained by the institution or by a party acting for it.

The consequence for recruiting is that an anonymous website visitor or a prospect who has not enrolled is generally not a student under FERPA. That does not make the data free to use. State privacy laws, your own privacy notice and your contracts still apply, and the TCPA applies to every phone number regardless of FERPA status.

The line moves when a person is admitted and enrolls. Records tied to a student's attendance, such as financial aid, advising and grades, belong to the registrar's world. If an AI agent can see or discuss those records for enrolled students, confirm with your registrar and your vendor contract how the provider handles them before launch. An agent that answers only from public program information carries much less risk than one wired into the student information system.

## What a compliant admissions workflow looks like

Build the workflow backwards from the consent you can prove.

1. **Collect consent at the moment of the phone number.** Show unchecked-box language that names your institution, the channel (text or call), the type of message and how to stop. Store the wording, the version and the timestamp.
2. **Separate service from marketing.** A reply to a question the student asked is a service interaction. A scholarship promotion is marketing and needs its own consent.
3. **Disclose the AI.** State plainly that an automated assistant is sending the message or placing the call.
4. **Honor opt-outs everywhere.** One "stop" updates every system, quickly, and the student receives a single confirmation.
5. **Keep a human behind it.** Route aid appeals, visa questions, decisions and distress to named staff. Our pieces on [WhatsApp opt-in and handoff](https://www.skolbot.ai/en-US/blog/whatsapp-admissions-2026-opt-in-templates-pricing-handoff) and [summer melt outreach](https://www.skolbot.ai/en-US/blog/reduce-summer-melt-ai-agent-admitted-students) show how consent and handoff look in practice.
6. **Draw the FERPA line in writing.** Decide with the registrar which conversations may reference student records, and which never will.

For community colleges, where open enrollment and fast deadlines push offices toward automation, the same steps apply; see [our community college enrollment guide](https://www.skolbot.ai/en-US/blog/ai-chatbot-community-college-enrollment-guide). If you also recruit in Europe, the picture differs again, and our [GDPR guide for student data](https://www.skolbot.ai/en-US/blog/gdpr-student-data-guide) covers that regime.

## Questions to put to any vendor

Ask these in writing and keep the answers:

- Where is consent captured, and can you export the proof for one phone number on request?
- Does an opt-out reach every channel and every connected system, and how fast?
- Does the product place calls with synthetic voices, and if so, how is the AI disclosed?
- Which student records can the agent read, and under what contract terms?
- Who reviews rule changes, such as the November 25 revocation update, and how are customers told?

Skolbot builds AI agents for admissions teams, and we expect these questions from every buyer. A vendor that cannot answer them clearly is a risk to your institution, not a shortcut.

## FAQ

### Does the TCPA apply to a chatbot on my website?

Not by itself, in general. A visitor who opens a chat on your site is not receiving a call or text from you. The TCPA matters once you send texts or place calls to a phone number, including follow-ups an AI agent triggers after the chat. Have counsel confirm how your setup is classified.

### Are AI voice calls to prospects allowed?

Only with the consent that applies to the call. The FCC has confirmed that the TCPA's limits on artificial or prerecorded voices cover current AI technologies that resemble human voices, so an AI caller needs at least the consent a prerecorded call would need, and written consent if the call is telemarketing.

### Is FERPA a barrier to contacting applicants?

Generally not. FERPA protects students who are or have been in attendance, so applicants who never enrolled are outside its core protections. Other rules, including the TCPA and state privacy law, still govern how you contact them. After enrollment, FERPA governs what the agent may access and say.

### What changes on November 25, 2026?

An FCC order revising the consent-revocation rules takes effect. According to the Federal Register abstract, it lets callers limit a revocation to the category of informational robocall it targeted and set an exclusive revocation method. A separate proposal on faster handling and two-way texting is still open for comment.

### Should we ask students to confirm each text?

Counsel should decide. At minimum, collect clear consent at the point of the phone number, keep the evidence, and make "stop" work instantly across every system.

---

<a href="/en-US/demo" className="cta-button">Request a personalized Skolbot demo</a>
