Dial Zero
Our kids want to reach us while we're out. We don't want to give them smartphones. This used to be a solved problem — every house had a phone on the wall and every kid knew how to use it.
TinCan phones are popular at their school, and for good reason. They're well-designed, screenless, and built for exactly this. But I'd been building a family operating system that already knows our schedules, contacts, and routines. It felt like the phone should be able to tap into that. So I built a landline. Dial 0 and you get an AI-powered family operator.
The phone
Transparent corded phone, neon lighting inside. You can see the circuitry through the clear housing. The keypad glows. It flashes when a call comes in. I found it on PhonesOnSale.com — huge variety of landline phones, most under forty dollars. It looks like something from 1996, which is exactly why my kids love it.
An analog telephone adapter plugs it into the internet. A Twilio SIP trunk gives it a real phone number. A few cents per minute, no subscription.
The kids own this phone. They dial out whenever they want. Friends, parents and grandparents. Pick up the handset, dial the number, talk. It's their phone and their independence. They don't ask permission to use it any more than I asked permission to use the kitchen phone when I was nine.
The invisible guardrails
What makes this work for me as a parent is what the kids don't see.
Inbound calls are whitelisted. Every number in our contact list rings through. Everyone else gets a polite rejection. The kids never hear an unknown caller. They don't know the filtering exists because they've never experienced the alternative.
Quiet hours kick in at 9:00 on school nights. Family bypasses the cutoff. Everyone else waits until morning. The phone doesn't announce this. It just stops ringing.
These controls are invisible by design. The kids experience a phone that works. I experience a phone I don't have to supervise. That's the gap most kid-phone products are trying to close, and it's the right gap. I just wanted the controls defined in a YAML file I could edit, not in someone else's app.
The operator
Dial 0 and you're talking to the family AI.
Her name is Maeve. She runs on Claude, with speech-to-text and text-to-speech in a real-time loop. She sounds like a person, responds in a sentence or two, and stops talking when my kid interrupts her.
What makes her useful isn't the voice. It's that she reads the same structured files that run the rest of our household system. School schedules, weekly activities, daily routines, travel plans, contacts. When my son asks "do I have soccer today?" she checks the actual schedule and tells him. When my daughter says "can you call Nana?" Maeve looks up the number and transfers the call live.
She can leave messages too. "Tell Dad to bring home milk" sends a text to my phone, attributed to whoever's calling. She knows who's on the line by caller ID. When the call comes from the landline, she assumes it's a kid and shifts her tone. Playful, patient, age-appropriate. She helps with homework by asking questions, not giving answers. She tells jokes if you ask. She says goodbye when you say goodbye.
She doesn't record conversations or report back to parents. No transcripts, no tracking. The call ends and the only trace is a log line showing it happened.
The shape of the thing
A smartphone gives kids communication and takes everything else. A screenless phone gives them communication and nothing else. The second one is right.
No browser. No notifications. No feed. No camera. No group chat. The phone sits on the kitchen counter. There's no pocket to carry it in, no screen to pull them back. They pick it up, use it, put it down. The physicality is the point.
The whole thing is a few hundred lines of code and a Saturday afternoon. The hardest part was the analog telephone adapter manual, which was written for telecom engineers in 2008.
My kids talk to grandma. They make plans with friends. They ask Maeve what time tennis starts. Then they hang up and go outside.