Your message has been sent to [email protected]. We read every submission and aim to reply within 2–3 business days.
Teacher Contact gives every teacher and student a permanent, phone-number-based identity that works across every school, every year — making communication verified, structured, and safe by design.
⚠️ Not yet publicly available. Beta testing is closed and invitation-only.
A structured, phone-number-based email address where your number is permanent and the domain encodes your role, location, and school level — self-describing, verifiable, impossible to spoof.
Both addresses reach the same teacher. The alias is designed for voice — "one-one-one-eight at teachers dot email" — clear and unambiguous over a phone call or voice interface.
Phone numbers are the most widely verified personal identifier in use — tied to real identity through carrier registration, portable across providers, and familiar to everyone. Teacher Contact builds on an infrastructure schools and families already trust.
The identity system makes each step frictionless — because the address itself tells the platform who you are, what your role is, and whether contact is permitted.
Search the school-managed directory by name, subject, grade, or location. Every listing is confirmed by the school and backed by a verified identity address.
The teacher's name, subject, school, and their alias address — enough to contact them, without exposing their personal phone or home email.
When you sign in, the system reads your structured address and confirms your role — parent, student, or teacher — without you needing to explain who you are. The address does the talking.
Your verified role and structured address. A message from [email protected] is instantly understood: a verified middle schooler at this district.
Messages are routed through the platform, encrypted in transit, and tagged with your verified role. Teachers see context — not just a message from an unknown address.
A message from @parents.email tells a teacher instantly: this is a verified parent of a currently enrolled student.
Every feature is anchored to the identity system — so access is always role-appropriate, and teachers are never reachable by someone who shouldn't reach them.
A school-managed roster where every teacher has a structured identity address. Searchable by name, subject, or location — accessible only to verified users.
One number. One address. One verified identity — that works across every school, every year. No new credentials to memorize. No accounts to create from scratch.
Every message arrives with verified context. Teachers see who the sender is — parent, student, administrator — without needing to ask or guess.
The alias format is designed to be spoken clearly over a phone call or through a voice interface. Numbers are universal and unambiguous across every language.
Schools assign numbers, verify identities, and manage access. The structured address system means administrators can see at a glance who has access to what — without needing a separate permissions dashboard for every edge case. This is a foundational design commitment, not a stretch goal.
The identity system makes AI safer: because every sender is verified, AI can route messages accurately without guessing at context. But AI features come later — the core must work first.
@highschool.email and one from @teachers.email are treated differently, automatically.The structured address system is designed so that anyone contacting a teacher reveals only what's necessary — their verified role and school relationship — while keeping personal data private on both sides.
The local number in an address is derived from a phone number but is not the phone number itself. It cannot be reverse-searched to find someone's personal contact information.
When a parent contacts a teacher, the teacher sees a verified @parents.email address — confirming they're a real enrolled parent — without seeing their personal name, phone, or home email.
Identity addresses are issued and verified by the school at onboarding — not self-claimed. No one can generate a @teachers.email address for themselves. The school is the sole authority.
The structured address encodes everything the platform needs to verify a user's role. We don't need — and don't collect — additional personal data to make the system work.
All messages are encrypted in transit. Stored data uses school-managed keys where technically feasible. The school controls its data — never co-mingled with other schools' records.
Designed for FERPA from day one. Student identity addresses are educational records — handled accordingly. Legal review is ongoing throughout the beta period.
We're in beta testing now. The goal is a publicly available, school-ready platform by 2027 — with the phone-number identity system as its foundation.
A small group of invited schools and educators are testing the identity address system, teacher directory, and core messaging. Gathering real feedback on verification flows.
Refine the identity system based on beta learnings, expand testing to more districts, and finalize student domain lifecycle transitions. No public access yet.
A stable, publicly available Teacher Contact — with the full phone-number identity system, verified teacher directory, and structured messaging. No AI features at launch.
The alias system unlocks voice-first interfaces. AI message routing becomes possible because every sender is already verified. Timeline depends on core platform performance.
Testing whether phone-number-based addresses work reliably at school onboarding — and whether teachers and parents find them intuitive in practice.
Identity addresses, verified directory, and structured messaging. No AI at launch. The identity system is the product — everything else builds on top of it.
The alias format was designed for voice from the start. Once trusted, voice-first features and AI routing follow naturally from the identity foundation.
We'd rather give you a complete, accurate picture than leave anything ambiguous about where this project stands.
No. Teacher Contact is in closed beta testing. It is not publicly available and not accepting public sign-ups. Our target for public launch is 2027.
A structured email address where the local part (before the @) is derived from your phone number, and the domain encodes your role and location. A teacher in San Diego gets:
1118585578@sandiego.california.teachers.email
The number is permanent. The domain is assigned by the school. Neither can be self-claimed.
As a student moves from elementary to middle to high school, only the domain changes — the number stays the same:
3338587392@elementaryschool.email
3338587392@middleschool.email
3338587392@highschool.email
The full ID — like [email protected] — is used for system routing and admin records. The alias — [email protected] — is shorter, voice-friendly, and resolves to the same inbox.
No — and AI isn't part of the current beta at all. AI features are planned for after the 2027 launch and will be strictly opt-in. The identity system works entirely without AI involvement — it's structural, not machine-learning based.
We'd rather launch late and right than early and broken. If 2027 needs to shift, we'll communicate that transparently with everyone following our progress. No hidden delays — this is a public commitment.
We're building this with educators — not for them from the outside. If you're a school administrator, teacher, or district leader, your input matters right now while there's still time to change things.