Teacher.contact is a verified communication platform built for schools — giving parents, students, and staff a clear, secure channel to reach teachers without exposing personal data.
🔒 No personal data is made public. School-controlled access only.
Teacher.contact removes the friction from school communication. There's no app to download, no complicated forms — just a structured, verified process.
Search the school-managed directory by name, subject, grade, or campus. Every listing is confirmed by the school before appearing.
Sign in with school-issued credentials or a verified role — parent, enrolled student, or staff member. No anonymous messages.
Send a message through the platform. Teachers receive it in their dedicated inbox and can respond on their own schedule.
Every feature is designed with school administrators in mind — giving them full control, with minimal disruption to existing workflows.
A structured, school-managed roster of teachers with verified identities. No outdated PDFs, no generic email addresses — just accurate, role-confirmed contact points.
Every user — parent, student, or staff — holds a verified role credential. Communication channels are shaped by who you are in relation to the school, not just who you claim to be.
One inbox for teachers. Messages from parents, students, and administrators arrive in a single, organized stream — with role labels so teachers always know context.
A practical, optional assistant that helps route messages, suggest response templates, and surface common FAQ answers. It assists — it does not intercept, surveil, or decide.
Principals and district administrators retain full control. Staff rosters, access policies, communication rules, and audit logs all live in the school's own admin panel — not a third-party server outside their authority.
We believe AI should make teachers' lives easier — not add surveillance to an already complex environment. Here's what we're building toward, honestly.
Teacher.contact is designed from the ground up to minimize data exposure — not maximize data collection. Schools control what's shared, when, and with whom.
Teacher contact information is never publicly searchable. Access requires a verified identity linked to a participating school. Nothing is visible without login.
When a parent contacts a teacher, the teacher sees their verified role and relationship to the school — not their home address, phone number, or personal email. Appropriate context, not full exposure.
Your school's data belongs to your school. We don't aggregate, sell, or use student or teacher data for advertising, analytics products, or third-party services of any kind.
We collect only what's necessary for the platform to function. We don't retain message content longer than the school's own policy requires. Deletion requests are honored promptly.
All messages and identity data are encrypted in transit. Stored data is encrypted at rest with keys managed at the school or district level where technically feasible.
The platform is being designed with FERPA requirements in mind from day one. Student records, communications involving minors, and educational data are handled with the specific protections the law requires.
Teacher.contact doesn't stand alone. It's designed as one component of a broader, interoperable school communication infrastructure — adopted piece by piece, not all at once.
The foundation layer. School.contact manages the verified identity records for every person associated with a school — staff, students, and parents — and issues role-based credentials used across the ecosystem.
PlannedThe central access point for reaching teachers securely. Draws on verified identities from school.contact to gate access and provide context for every message sent.
In DevelopmentA structured email system for parents using verified @parents.email addresses — replacing anonymous Gmail accounts with role-confirmed identities tied to their enrolled child's school record.
PlannedEach component can be adopted independently. Schools don't need to implement the full ecosystem to benefit from Teacher.contact.
We're not announcing a finished product. We're building one transparently — in partnership with educators who know what actually works.
Working with a small group of schools to test the core directory and messaging system. Gathering real feedback on verification flows, teacher experience, and admin tooling.
Opening to additional school districts based on pilot learnings. Introducing role-based identity integration and optional AI communication assistance for participating schools.
Long-term direction includes voice-first interfaces and full ecosystem integration with school.contact and parents.email. Timeline depends on pilot feedback and partnership development.
Teachers appear in a school-managed directory. Verified parents and students can send structured messages. The core communication loop works reliably before anything else is added.
Role-based credentials from school.contact feed into Teacher.contact. @teachers.email and @parents.email domains become part of the verification flow.
An opt-in voice interface allowing parents to call and leave structured messages that are transcribed, tagged, and routed — with teacher consent and control at every step.
We'd rather give you a clear picture now than over-promise and disappoint later.
Not publicly. We're in an active pilot phase with a small number of schools. The core directory and messaging system is functional in those environments. We're not releasing to the general public until the pilot produces stable, tested results.
Verification happens at school onboarding. Schools upload their staff rosters and enroll parent/student records from their existing student information system (SIS). Each person receives a role credential — not based on self-reporting, but on official school records. There's no way to claim you're a parent of a student if the school hasn't confirmed it.
No. AI features are strictly opt-in and off by default. In Phase 1, there is no AI involved in message handling at all. When AI is introduced in Phase 2, it will only activate for schools and teachers who explicitly enable specific features — and teachers retain the ability to disable any AI feature at any time.
Standard email is unverified, unstructured, and unmanaged. A parent can email a teacher from any address with no context. Teacher.contact ensures the teacher knows the sender's role, relationship to the school, and that they're genuinely who they say they are — while keeping personal contact details on both sides private.
Yes — teacher control is a core design principle. Teachers can set communication hours, define which types of messages they accept, pause their inbox, and choose whether any AI assistance is active. The platform works for teachers, not around them.
Pricing for the pilot phase is still being determined in collaboration with participating schools. Our goal is a model that's sustainable for schools of all sizes — we'll publish clear, transparent pricing before any broader rollout. No school will be locked in during the pilot.
Whether you're a school administrator, a teacher, or a district leader — we want to hear from you before we build, not after.
Bring Teacher.contact to your school as a pilot partner. Shape the product through real use, not a survey.
Get notified when Teacher.contact opens beyond the current pilot — and be first in line for your district.
Have a concern, a question, or an idea? We're actively listening. Educator input is steering this project.