Shipped build · Home services
Every call answered. Six paths. Everything logged.
Watch it work
What it does
- Routes six call paths: estimates, general questions, transfers, emergency help, booking, FAQs
- Checks the caller's zip against a service-area sheet — at call time
- Quotes standard prices from a pricing sheet the client edits
- Writes every detail to structured tables: call logs (intent, transcript, summary, outcome), services, clients
In the demo
Caller asks for an estimate, gives zip 2001. Agent confirms it's in the service area.
Asks name and service type. Quotes $100–250 for drain cleaning.
Asks: one drain or several? Books a callback. Every field logged correctly.
How it’s engineered
Global routing node
A conversational flow with a global routing node — any path reachable from anywhere in the call.
Four functions
Emergency hours, pricing, service-area checks, and post-call analysis.
Sheets read at call time
Zips and prices live in two spreadsheets. Changes go live without a deploy.
Full structured logging
Every call auditable after the fact.
The system
Inbound calls hit a flow engine with a global router across six labeled paths; four functions handle emergency hours, pricing, service-area lookups, and post-call analysis, reading client-edited sheets at call time and writing structured logs — intent, transcript, summary, outcome — to Airtable.
Stack
- Retell
- Make.com
- Google Sheets
- Airtable