I build production voice agents. Currently: Evercall.
When an Australian emergency plumber can't answer, we book the job. Day job: agent runtimes at Salesforce.
Evercall — divert for Australian emergency plumbers: triage, book the job, SMS the owner. Browser agent is live; the phone wire (DID → SIP → Neon) is what I'm closing now.
At Salesforce I work on agent runtimes. Before that: SMS platforms serving billions of messages, app-certification systems, home-network security. Nine-plus years across Salesforce, Amazon, and McAfee.
The writing is the part most tutorials skip: latency, barge-in, turn-taking, tools that must not lie — with runnable code.
- Voice Agents: The Hard Problems — latency, barge-in, turn-taking
- LiveKit Voice Agents — the state machine you were about to write already exists
- Building Evercall — one line per week that actually shipped
Evercall — when they can't answer, we book the job
AU divert line for emergency plumbers. Not an "AI receptionist" landing page. The product is a booked job and an SMS to the owner.
Voice AI · LiveKit · Python · Next.js
Also shipped, parked: OneCue · VibeFrames · Paymint · AI SDK Patterns






