The call that didn't come
It was a Tuesday afternoon. Our daughter had fallen over at daycare and needed to be picked up. The staff called the contact number on file — and it wasn't mine.
I'm a software developer. I work from home most days. I'm usually the more available parent by a significant margin. But I wasn't on the form, not really. My wife was — she's an economist at a busy consultancy, in back-to-back meetings most afternoons, fielding calls she can rarely take. She was the one who'd filled in the forms during the initial enrolment. Her number went first.
By the time she got out of her meeting and called me, forty minutes had passed. I could have been there in ten.
The imbalance nobody planned
My wife hadn't planned to be the default parent. She has a demanding job — often more demanding than mine, with less flexibility in her schedule. If anything, I'm usually the better person to take a call at 2pm on a weekday. But the system didn't know that, and we'd never set it up to reflect reality.
What we had instead was the same pattern millions of Australian families have: one number on every form, one parent fielding every interruption, one person carrying the mental weight of being reachable at all times.
My wife was exhausted by it. Not just the calls themselves, but the expectation — the assumption baked into every enrolment form and GP record that she was the point of contact, full stop.
And I was frustrated in a different way. I felt peripheral. Like the backup, not a co-parent. Schools and doctors and childcare centres had built their entire relationship with our family through one phone number, and it wasn't mine.
We tried the obvious things first
We updated forms. We added my number as the emergency contact. We asked the daycare to call me first.
It helped, sometimes. But the infrastructure kept pulling toward the same default. New staff would see one number used more often and follow the pattern. Online portals had one "primary contact" field. The GP's system showed one account holder. There was always friction.
What we really needed was a single number that could reach either of us — one that didn't pick sides, didn't favour whoever happened to fill in the paperwork first, and adapted to who was actually available.
Building the thing we needed
I'm a developer. When I can't find a solution, I build one.
What I wanted was simple: an Australian phone number — a real local number that would look right on a school form — that would ring both our phones at once. Whoever picked up first handled the call. No hierarchy. No default. Just whoever was available.
I'd used similar tools in professional contexts. Call routing, virtual numbers, forwarding logic — none of it was new technology. But nothing was designed for a family. Everything assumed you were a business.
So I built it for us. It took a few weekends. The first version was rough. But it worked. The daycare called our family number, my phone rang, I answered, I picked up our daughter.
That felt like a small thing. It wasn't.
What it actually changed
The practical change was obvious — I started getting calls. I started knowing what was happening. I stopped being the last to find out.
But the bigger change was subtler. My wife stopped feeling like the single point of failure for our family's logistics. The mental load didn't disappear, but it distributed more naturally. When she was in a meeting, she wasn't anxious about missing something urgent — because I'd get it. When I was available, I actually got the chance to be.
We stopped having the conversation about who should have their phone on loud at dinner. Both of us needed to be reachable, and now both of us were.
Why we made it a product
We're an Australian family. We know this isn't a problem unique to us.
Most families with two working parents are navigating some version of this — one parent over-indexed as the contact, the other under-involved by default, both a bit resentful about it. It's not a values problem. It's an infrastructure problem.
KinOnCall is the infrastructure fix. A shared Australian number, flexible call routing, and nothing more complicated than it needs to be.
If you're the parent who never gets the calls — this is for you. If you're the parent who always gets them — this is for you too.