I built the receptionist I couldn't afford to hire.
AI Jane wasn't dreamed up in a boardroom. It was built by someone who spent more than a decade on the other side of the front desk.
Noam Sonnenfeld
I ran an allied health clinic for more than a decade. I was the practitioner, the business owner, and the receptionist I couldn't afford to hire. I know what it feels like to check voicemail between patients and find three missed calls. Each one was a person who chose my practice, and then chose to wait, or chose someone else.
“I didn't study this problem. I lived it. And when AI got good enough, I built the thing I wished I'd had.”
The trouble is, every other product I looked at saw its job as getting an appointment into a calendar. That's the easy part. What nobody was solving was everything that happens before and after that booking. The work that actually fills a clinician's day and quietly drains a clinic.
I felt the absence of three things in particular:
A developer without that lived experience wouldn't have known to build triage, or distribution. They'd have built another booking tool. So I built the one I needed: intelligent triage that matches a caller to the right practitioner, automatic distribution that balances new patients across a team without a spreadsheet or an awkward conversation, and two-way SMS that turns a 9pm cancellation into a refilled slot by morning.
My background sits across both worlds: a Bachelor of Health Science in Chinese Medicine and a Bachelor of Business Systems in IT. The Chinese medicine instinct is to treat the root, not the symptom. The booking bot is the symptom. Missed revenue, uneven distribution and unactioned SMS are the conditions. Jane was designed to treat all three.
Every Jane is tested before a single real call comes through. Your practice listens, gives feedback, and signs off. Nothing goes live until it sounds right. That's not a feature. It's the only way I'd have trusted someone with my own phone.