Can Organizations Text Minors? Consent and Age Rules

Yes, organizations can text minors, schools, youth programs, pediatric clinics, and churches do it every day, but the consent analysis changes when the recipient is under 18, and it changes sharply when they are under 13. The rules come from four different directions at once: federal privacy law (COPPA), telephone consent law (TCPA), education records law (FERPA) for schools, and carrier content rules that require age-gating for certain categories.

No single statute answers "can we text kids?" This guide assembles the pieces into one reference, so youth-serving organizations can build programs that are both effective and defensible.

COPPA: The Under-13 Line

The Children's Online Privacy Protection Act (COPPA, 15 U.S.C. 6501-6506) and the FTC's COPPA Rule (16 CFR Part 312) govern online collection of personal information from children under 13 by operators of websites and online services directed to children, or with actual knowledge they are collecting from under-13s. A phone number is personal information under the Rule.

What that means for texting programs:

• Collecting a phone number from a child under 13 through your website, app, or online form triggers COPPA, requiring verifiable parental consent before collection, along with notice and data-handling obligations.
• The clean pattern is to collect the parent's number instead. Programs serving young children should be built parent-facing: the parent opts in, the parent receives the messages.
• Age screening matters. Online sign-up flows for youth programs should ask date of birth or grade neutrally and route under-13 registrations to a parental consent path.

COPPA is enforced by the FTC with civil penalties per violation, and it applies to nonprofits operating commercial-equivalent online services as a practical matter of risk even where technical coverage arguments exist.

TCPA: Consent Capacity and Whose Consent Counts

The Telephone Consumer Protection Act (47 U.S.C. 227) requires prior express consent for autodialed texts to cell phones, and prior express written consent for marketing, without setting an age threshold. Two principles fill the gap:

1. Consent must come from someone with authority to give it. For young children, that is realistically the parent or guardian, both because contract-law capacity of minors is limited and because the phone plan typically belongs to the parent.
2. Teens with their own numbers occupy a middle zone. A 16-year-old who texts JOIN to a youth group keyword has expressed consent in the ordinary sense, and informational messaging on that basis is common practice. For marketing content, and for any program serving under-13s, parent-side consent is the defensible architecture.

Document consent the same way you would for adults, the standards are laid out in our guide to SMS opt-in and opt-out requirements, and honor STOP from whoever holds the phone, immediately, regardless of age.

FERPA: The Schools Layer

For schools and districts, the Family Educational Rights and Privacy Act (FERPA, 20 U.S.C. 1232g; 34 CFR Part 99) governs what student information can flow through any communication channel, texting included:

• Texting a parent about their own student is core school-home communication; texting content drawn from education records to third parties is where FERPA problems arise.
• Rights under FERPA belong to parents until the student turns 18, when they transfer to the student.
• Messaging vendors handling student information should operate under the school official exception with proper contracts.

The full treatment, including directory information nuances and platform requirements, is in our guide to FERPA-compliant student texting, and district-wide program design is covered on our K-12 education solutions page.

Carrier Rules: Age-Gating and Content

Carrier requirements under the CTIA Messaging Principles and Best Practices add a content dimension: restricted categories, alcohol most prominently, require verified legal-age recipients, which by definition excludes minors. For youth-serving programs the practical rules are simpler:

• Keep content appropriate and program-relevant; carriers act on complaint patterns regardless of audience.
• Register campaigns honestly: a school notification campaign should be declared as such.
• Never use age data collected for gating to market to the minor.

The Program Design That Works

Assembled into practice, youth-serving texting programs converge on one architecture:

Add the universal mechanics: documented opt-in with the language preserved, immediate STOP handling, and clean separation between informational and promotional streams.

Enrollment Flows That Get This Right

The difference between a defensible youth program and a fragile one is usually visible in the enrollment flow itself. Patterns that work:

1. Ask age or grade first, neutrally. A date-of-birth or grade field early in sign-up lets the flow branch before any number is collected: under-13 registrations route to a parent contact step, teens route to a teen-plus-parent step. Asking after collecting the number defeats the purpose.
2. Enroll the parent alongside the teen. Dual enrollment, teen receives program logistics, parent receives the same or a digest, satisfies the consent-capacity concern, keeps families informed, and gives the program a stable contact when teens change numbers.
3. Re-confirm each season or year. Youth programs turn over: students graduate, families leave, phones change hands. An annual re-confirmation message, reply YES to stay enrolled, prunes stale numbers before they become wrong-recipient problems, which matter more when the audience is minors.
4. Train staff on the boundary. The rules above govern the program; individual staff texting individual minors from personal phones is a different and worse pattern, which youth-protection policies in most organizations already prohibit. Keep every conversation on the organizational platform where it is logged and supervised.

These flows cost little to build and convert the legal patchwork into a handful of form fields and defaults, which is where compliance belongs.

When Things Change: Turning 13, Turning 18, and Leaving the Program

Age-based rules have a property adult programs never deal with: every subscriber's status changes on a schedule. A program built for the enrollment moment can drift out of its own rules as its audience grows up. Three transitions deserve explicit handling:

1. Turning 13. COPPA's collection rules stop applying prospectively, and a parent-mediated enrollment can convert to a teen-facing one, but only through a real re-enrollment step, not a silent switch of recipient. The parent enrolled; the parent stays the subscriber until someone affirmatively changes it.
2. Turning 18. In school contexts, FERPA rights transfer from parent to student, and consent capacity questions dissolve. Programs serving graduating cohorts should re-permission alumni as adults rather than carrying childhood enrollments forward indefinitely.
3. Aging out or leaving. Youth program rosters churn annually. Enrollment tied to a season, team, grade, or program year should expire with it, with re-confirmation at each cycle, because messages to families who left reads as spam and, worse, erodes the trust youth organizations run on.

Handled as calendar events with default expirations, these transitions run themselves; handled never, they accumulate as quiet compliance debt.

Frequently Asked Questions

Is it illegal to text a 15-year-old?

No statute flatly prohibits it. The questions are consent (who validly opted in), content (age-appropriate, non-restricted categories), and context (FERPA rules if you are a school, COPPA if a number was collected online from an under-13). A properly consented informational program serving teens is lawful and routine.

Does COPPA apply to text messages themselves?

COPPA governs the online collection of personal information from under-13s, so it attaches at sign-up (collecting the number through an online service) rather than to each message. Offline paper collection sits outside the COPPA Rule, though parent-facing design remains the sound pattern regardless.

Can a teen's opt-in count as written consent for marketing?

Minors' capacity to enter binding agreements is limited by state law, which makes teen-signed marketing consent fragile. For anything promotional, obtain the parent's written consent and direct appeals at the parent.

What if a parent opts in but the phone is used by the child?

Consent from the account-holding parent covering messages the child will see is the standard structure for family programs. Honor STOP from the device whoever sends it, and re-confirm enrollment periodically so lapsed arrangements do not linger.

Do we need different rules for texting college students?

Students 18 and over are adults: standard TCPA consent rules apply, and FERPA rights belong to the student. The under-18 architecture in this guide applies to K-12 and youth-program contexts.

Youth Programs, Built on the Right Consent

FRANSiS supports parent-facing enrollment, documented consent per contact, instant opt-out handling, and FERPA-aware messaging workflows for schools and youth organizations. Contact us to design a program that reaches families the right way.