/voice-agent-builder
Agent 86: Voice Agents, Any Platform (S7 Builders)
Builds a production AI voice agent on any platform other than GHL: a purchased Twilio number, a hosted TwiML webhook running a Claude-driven script, and the same disclosure/consent defaults as /ghl-voice-agent-builder (#84). Inbound-only by default; outbound calling enabled only with a recorded prior-express-consent source. No card number ever asked for or spoken.
verified (fixture) 2026-09-08 · needs-connector: twilio · manual-fallback: an Exelo-hosted line is set up in its partner portal (no public API)v0.2.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #86 — Build voice agents (any platform) · as #84
Example requests
- “build us a voice agent that isn't on GHL”
- “give our AI receptionist its own phone number”
- “build a sales voice agent on our own stack”
- “voice agent builder”
What it needs, and what it hands back
Needs connected
- twilio
- vercel
Uses create_repository, create_git_project, get_deployment, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/<business-slug>/plans/voice-agent/<date>.md (script, webhook design, disclosure/consent record, and once live: number-configuration read-back and test-call result)
Stops and asks
- purchasing a real Twilio number
- enabling outbound calling for a named agent
Steps it cannot do through an API, and hands you instead: Exelo (C51): no public API exists, so an Exelo-hosted line is set up in its partner portal by hand per the guide row's checklist; the number is recorded in master.md and nothing is read from the portal.
How it runs
These are the headings of its own written instructions — 227 lines you can read and change.
- Step 0 — Environment, connection, and profile
- Step 1 — Design the agent and its script
- Step 2 — Build the webhook (the conversation engine)
- Step 3 — Purchase the number and wire the webhook (once connected)