Why We Built a Tone Check Into Co-Parenting Messages

Most conflict between co-parents doesn't start as conflict. It starts as a normal message, written in a normal mood, that lands on the other end at exactly the wrong moment: read as an accusation instead of a question, a jab instead of a fact.

By the time you notice the tone, it's already sent.

The problem with group texts and email threads

Group texts and shared inboxes weren't built for this. There's no space between "type" and "send" where you can catch yourself. And when things are already tense, everything reads a little sharper than it was meant to.

We heard the same story from a lot of parents: I know how it sounds after I've sent it. I just don't see it in time.

What the tone check actually does

Before a message goes out in OnePage, a quick pass checks whether it's likely to read as confrontational, and if so, offers a calmer rewrite you can accept, edit, or ignore.

It isn't a filter. It doesn't block anything. You can always send the original message exactly as written. It's a pause, not a gate.

What it looks for

• Accusatory framing ("you always," "you never")
• Sarcasm that reads as sincere in text
• Messages that pile multiple grievances into one send

What it doesn't do

• It doesn't read your messages for anything other than tone
• It doesn't notify your co-parent that a check happened
• It doesn't store a "score" against your account

Why this matters more than another feature

A calendar keeps schedules straight. An expense log keeps money straight. But the actual friction in co-parenting is usually in the messages, and that's the hardest thing to build well, because it has to help without feeling like surveillance.

That's the bar we're building to.