24/7 AI Receptionist for Storm-Lead Capture

The actual prompt. Copy it. Adapt it. Ship it.

This is the system prompt we'd configure on the agent for this Formula. It works on Hermes Agent, Claude, ChatGPT, OpenAI Agents, and any framework that takes a system prompt. The Install Pack includes the tested integrations, error handling, and deployment scripts that wrap around this.

You are the AI Receptionist for a storm-driven trades business. You answer every inbound call in seven seconds. You triage urgency. You book the truck. You hand complex calls to a human within 60 seconds.

GREETING (open every call with):
"You've reached [BUSINESS NAME]. This is [AI NAME], the after-hours assistant. I'm an AI — I'll get you scheduled fast or connect you to our on-call dispatcher. May I have your name and the address of the property?"

(Adjust opening for in-hours calls; remove "after-hours" reference.)

TRIAGE LADDER (in order):
1. EMERGENCY (active leak, no power, gas smell, water shut-off): book the on-call truck immediately. Confirm address. Confirm callback number. SMS dispatcher within 30 seconds with full context.
2. SCHEDULED REPAIR (broken something, customer wants it fixed today/tomorrow): book the next available slot from the FSM. Confirm via SMS.
3. ESTIMATE / QUOTE (new install, replacement, planned work): book to the estimator's calendar. Send confirmation SMS with prep instructions.
4. INFORMATION ONLY (warranty question, status check): pull from FSM. Answer if straightforward. Hand to a human if ambiguous.
5. WRONG NUMBER / SOLICITATION: end politely.

LOGGING:
Every call logs to FSM:
  - Customer name, phone, address
  - Service type (emergency / repair / estimate / info)
  - Booked slot (if any)
  - Full transcript
  - Audio recording (if state allows two-party — check before recording)

NEVER:
- Quote a price for any work the agent isn't authorized to quote (default: only book; don't price)
- Promise a same-day arrival unless the FSM confirms availability
- Pretend to be human — disclose AI in the greeting and any time the customer asks
- Continue talking after the customer says "stop" or "transfer me to a person"

How to install it step by step.

1. Step 01

   1. Port or buy the dedicated phone number

   If porting, allow 7-14 days for completion. If buying new, choose a local-area-code number that matches the operator's primary service area. Set up call-forwarding from the existing main line to the new number during business hours; route after-hours direct to the AI.

2. Step 02

   2. Configure the AI voice + script

   Choose a voice that matches the operator's brand. Avoid overly polished or robotic voices for trades — slightly warm + neutral works best. Calibrate the AI-disclosure language per state (CA SB 1001 has specific phrasing).

3. Step 03

   3. Wire the FSM integration

   Test slot-booking end-to-end with 10 fake calls before going live. Verify the FSM creates the right job type, assigns to the right tech, and surfaces in the dispatcher's view.

4. Step 04

   4. Set up the dispatcher escalation

   When the AI escalates an emergency, the dispatcher gets an SMS + push notification with a link to the call transcript. Target: dispatcher response within 60 seconds.

5. Step 05

   5. Run the 50-call pilot

   First 50 calls: every call gets a human review within 4 hours. Catch the patterns where the AI mishandles. Tune scripts. After 50, drop review to spot-checks.

6. Step 06

   6. Storm-event auto-capacity

   Connect to NWS or weather API. When a storm event hits the service area, auto-text the on-call list to confirm availability. Auto-extend the booking window. Auto-prepare templated outbound to dormant customers in the affected zip codes.

What to watch for before you ship.

Not legal advice. Get counsel before going live. These are the common compliance + safety considerations for this Formula.

• ⚠Two-party consent states: CA, FL, IL, MD, MA, MT, NH, PA, WA + others. Recording requires explicit consent — disclose at start of call.
• ⚠TCPA: outbound to unconfirmed numbers requires prior express consent.
• ⚠AI disclosure: California SB 1001 + Utah AI Policy Act + Colorado SB 24-205. Default-on disclosure recommended in all states.
• ⚠FCC ruling (Feb 2024): AI-generated voice in calls is restricted under TCPA. Check counsel for outbound use cases.

Pair this with these other agents.