The phone & chat agent that never misses a lead

A 24/7 AI agent that answers overflow and after-hours calls - and website chats - quotes from the real price list, and cancels or reschedules against the same system my staff use.

The problem: We're in Arizona, so East Coast callers hit closed hours and weekends had nobody on the phones. A small business can't staff 24/7, and every missed call is a booked job walking to a competitor.
The old way: A voicemail black hole - you don't know when it'll be heard or what happens next. Or an answering service reading a script that can't quote a price or book a job.
The AI way: A natural-voice agent greets the caller, captures the lead, quotes through the same pricing engine my staff use, texts a how-to video mid-call, and reschedules or cancels against the same scheduler the humans use. The chat side started as a hybrid - the AI was so good we handed it everything.
The impact: About 17% of inbound is pure voicemail and only ~45% of that is even actionable. Now a qualified lead gets a real ballpark price and answers 24/7 - even though no human has talked to them. The knowledge base was seeded from real sales-call transcripts, so it covered real questions from day one.
The honest edge: Spanish callers are greeted and captured for a callback, not fully handled - a deliberate v1 boundary. And phone calls are solid gold, so the rule is no silent failure: if the tech breaks, the call routes straight to a human.

In his words

These are real customers who need real help. And I should be working as fast and as hard as I can to find solutions for those customers that work.

Derek, on an early dead-air call

Built on:CallRail routingVapi transportDeepgram nova-3gpt-4.1-miniElevenLabs voice18 function toolsReal pricing engineDisaster-recovery failover

Build your own

Everything below is how it was actually built - the real journey, the prompts, and a starter repo you can run.

Build journey & gotchas

“The voice transport is settled.” - the opening line of the plan the next six weeks demolished.
A real, frustrated after-hours caller sat in ~5 minutes of dead air on a socket that looked alive but had stopped sending - that call made the decision to stop owning the phone transport myself.
A digit-spacing rule meant for ZIP codes once spoke a $4,000 quote out loud as “four hundred to five hundred.”
A location-prefix shortcut told a caller 170 miles away they were inside the metro service area.
For two weeks every deploy silently reverted a voice-stability fix - because the fix lived on a branch that never got merged - until a “the voice sounds drunk” report.

The real lesson

Don't own the voice transport layer. Every recurring go-live bug lived there - the brain, the knowledge base, and the tools were always solid. There's a cost ladder from a $100+ packaged VoIP box, to ~$5 managed pipeline, to the ~$1 raw-infrastructure route I tried to be too cute with. Buy the infrastructure; spend your time on the data and workflows only you have.

Prompt pack + starter repo

The real system prompts, tool definitions and guardrails, plus a sanitized voice-agent skeleton you can clone, add your keys to, and have answering calls in an afternoon.

Architecture + ROI model

How the pieces fit end to end, the graceful-failover design so a dropped call still becomes a lead, and what it actually costs per call at your volume.

The build breakdown is coming.

The real journey, the prompt pack, and a runnable starter repo behind this use case are being produced now. Join the early-access list and you'll be first in when it drops.

Join the early-access list See what membership will include →