Use case
Co-parenting after separation
A shared alias that delivers school, medical, and activity comms to both parents simultaneously — so neither becomes the gatekeeper of information about their child.
Best for
Co-parents in different homes who want their children's information to flow to both of them, equally and automatically.
The workflow
How it runs end to end
- 01 Set up a co-parent alias for each child's institutions
- 02 Give it to schools, GPs, dentists, sports clubs, and music tutors
- 03 Both parents receive every message in real time
- 04 Configure who sees what — some things you both need, some only one
- 05 Adjust as circumstances change without involving the institutions
A category of friction worth removing
In separated and co-parenting households, a recurring pattern is that one parent — usually whoever provided the contact details to the school originally — ends up as the implicit gatekeeper of child-related information. The other parent has to ask, wait for forwarding, or set up parallel logins.
Even where there’s no acrimony, it’s logistical friction. Where there is acrimony, it’s a power dynamic that nobody chose and nobody really wants.
A neutral routing layer
A shared alias for the child — given to the school, the GP, the dentist, the football club — that fans every message out to both parents at once. Neither parent has to forward; neither institution has to maintain two contact records; both parents learn things at the same time.
The alias is owned by neither parent specifically — it’s owned by the routing rule. If circumstances change (a new step-parent, a custody adjustment, a school change), the routing changes; the institutions don’t have to be told anything.
What this is not
This isn’t a tool that resolves co-parenting disagreements. It’s a tool that removes one specific friction — the asymmetry of information access — so the harder conversations can happen on a level playing field. Plenty of co-parents who get on perfectly well still find it useful, simply because no one wants to be the one forwarding emails every evening.
Practical setup
Most families set up one alias per child, named neutrally (e.g. child-firstname@yourdomain) and shared with the institutions that actively send messages. For things only one parent needs to action — say, a particular activity that one parent runs the logistics for — you can route those specific senders to one inbox only, while the rest go to both.
The alias persists through changes — a new partner, a different school, a move — without ever needing to give the institutions a new contact.