Project 03 · Acquisition / Service
AI Receptionist Pilot Spec
A two-week pilot designed to validate — not deploy — a 24/7 voice agent at a propane distributor, where gas safety is the central concern.
Executive summary
Enderby handles a steady volume of inbound calls — delivery scheduling, tank monitoring, billing questions, emergency triage — all routed through a human dispatcher. That model works for complex situations and breaks down for everything else: after-hours calls go to voicemail, routine billing eats dispatcher time, and no-heat calls during cold snaps create handle-time spikes the team can't absorb.
The AI Receptionist is a voice-based frontline agent designed to answer calls 24/7, capture intent, resolve routine questions, and escalate urgent issues to the right human channel — without changing how Enderby fulfills service.
The business problem
Enderby's current call-handling model is fully human-driven. Effective for complex issues, but it creates five operational gaps that directly impact customer satisfaction, dispatcher capacity, and revenue:
- Missed calls. After-hours calls roll to voicemail. No-heat situations, tank outages, and delivery concerns wait until morning — creating delayed response and next-day call spikes that overload dispatch.
- Lost leads. New-customer inquiries that arrive after hours or during peak hold times go cold before a CSR can call back. In a low-switching-cost market, lead-capture velocity matters.
- Slow response time. During peak season, hold times climb. Long waits and repeated transfers create a perception of poor service even when internal effort is strong.
- Manual scheduling burden. Dispatchers spend hours per week on calls that require no judgment — confirming windows, answering "when is my next fill," capturing basic new-customer info.
- No consistent documentation. Call notes live in dispatcher heads, paper notepads, and inconsistent Cargas entries, so the next CSR starts over and patterns are invisible.
Pilot objectives
The pilot is designed to validate, not deploy. It must prove three things during the two-week window: that an AI agent can resolve at least 60% of routine calls without a human, escalate emergencies with at least 90% accuracy against human-reviewer judgment, and cut after-hours voicemail volume by at least half. If those benchmarks hold, the pilot becomes the foundation for a production deployment.
Workflow — six steps on every call
- Customer calls. A standard greeting identifies the agent as AI and offers immediate human handoff.
- AI answers. Twilio/Vapi receives the call and streams audio to the model, which asks an open-ended intent question.
- AI qualifies intent — billing, delivery status, tank level, new customer, or emergency. One clarifying question, then escalate if still unclear.
- AI books, routes, or summarizes using the NotebookLM knowledge base (sourced from Project 2's SOPs).
- Business gets a clean follow-up — a structured summary to the dispatcher queue; emergencies trigger an immediate notification, not just a summary.
- Caller gets confirmation of the next step. For escalations, the caller is told a human is being connected.
System architecture
| Layer | Tool |
|---|---|
| Voice intake | Twilio Voice / Vapi |
| Reasoning | Claude / GPT-4o |
| Knowledge base | NotebookLM (Project 2 SOPs) |
| Scheduling | Google Calendar (API) |
| Lead tracker / CRM handoff | Google Sheet (Cargas API in production) |
| Follow-up | Twilio SMS + Gmail |
| Transcript storage | Google Drive |
| Reporting | Looker Studio dashboard |
Risks & guardrails — the part that matters most
The risk profile of a voice agent at a propane distributor is non-trivial; gas safety is the central concern. The spec includes four explicit guardrails:
- Emergency calls route to a human. Any gas odor, suspected leak, CO alarm, no-heat with a vulnerable resident, or critically low tank → immediate handoff. No diagnostics, no troubleshooting, no holding.
- Ambiguity escalates after one clarification rather than letting the agent keep probing. A needless escalation costs a few dispatcher minutes; mishandled ambiguity in this domain costs much more.
- Consent & recording disclosure in the opening greeting, reviewed against Texas telephone-consumer regulations; callers who decline route to a human.
- Human review of every call touching an emergency, vulnerable resident, or legal-risk statement within 24 hours — building the audit trail for a go/no-go decision.
Pilot cost (simulated)
All numbers are based on publicly available pricing and are simulated for portfolio purposes. The pilot is constrained to free or low-tier plans — estimated total cost under $500 across the two weeks.
| Tier | Volume | Est. monthly cost |
|---|---|---|
| Prototype | < 20 internal test calls | Engineering time only |
| Light | 100 calls / month | $25–$45 |
| Standard | 500 calls / month | $120–$220 |
| Heavy | 1,000 calls / month | $250–$450 |
Success metrics
| Metric | Target | Why it matters |
|---|---|---|
| Missed calls reduced | ≥ 50% | Captures volume that previously went uncaptured |
| Response time | < 15 sec | Customer-perceived speed |
| Booking rate | ≥ 60% | Dispatcher load reduction |
| Lead capture | 100% | Revenue protection |
| Manual admin time | ≥ 30% less | Team capacity recovery |
| Escalation accuracy | ≥ 90% | Safety and trust |
Go / no-go decision logic
Go
All six KPIs hit target, zero safety incidents, and dispatchers confirm operational value during the weekly sync.
No-go
Any safety incident, escalation accuracy below 80%, or dispatcher feedback that the agent created more work than it removed.
Appendix — a mock call
Simulated for demonstration: a no-heat call with no safety risk, where the agent handles intake, screens for danger, gathers structured information, and routes to dispatch.
- AI
- Thank you for calling Enderby Gas. I'm an AI assistant. I can help with deliveries, tank levels, billing questions, and emergency triage, and I'll connect you with a person if you'd prefer. This call is being recorded. How can I help today?
- Caller
- Yeah, hi. I think we're out of gas. The heat just stopped working.
- AI
- I'm sorry to hear that. Before we go further, is anyone in the home elderly, an infant, or in a medical situation where the cold is an immediate concern?
- Caller
- No, it's just me and my husband. We're fine, just cold.
- AI
- Thank you. And do you notice any gas smell, hissing sounds, or anything that seems unusual?
- Caller
- No, nothing like that. The tank's just empty I think.
- AI
- Got it. Can I have the service address please?
- Caller
- 4421 County Road 217, Gainesville.
- AI
- Thank you. I'm going to send a same-day delivery request to dispatch right now. Someone will follow up by phone within the next 30 minutes with a delivery window. In the meantime, please don't attempt to relight any pilots or appliances yourself — a technician will handle that when the tank is filled. Anything else?
- Caller
- No, that's it. Thank you.
- AI
- You're welcome. Stay warm. Goodbye.
Businesses that benefit from this pattern
A voice-agent pilot can make sense for businesses with high inbound volume, after-hours demand, repeatable questions, and a clear human escalation path. It is not a fit when calls are mostly high-risk, emotionally sensitive, or impossible to resolve without expert judgment.
A practical first engagement
Start with a specification, not a production phone line: map call intents, define prohibited behavior and escalation triggers, create realistic test calls, establish success metrics, estimate cost, and make a go/no-go decision before deeper integration.
Enderby Gas is a real company used with the owner's permission. All names, customer data, and operational figures are simulated for portfolio purposes; cost and impact figures are based on publicly available pricing and industry benchmarks. No proprietary records were used.
Back to all projects