Add a New Church Voice Agent
Provision a new church on the multi-tenant voice agent — insert the church_voice_agents DB row with config, no redeploy needed; the agent routes automatically by phone number
Provision a new church on the multi-tenant voice agent — insert the church_voice_agents DB row with config, no redeploy needed; the agent routes automatically by phone number
End-to-end explanation of the ChurchWiseAI voice agent — body analogy, service map, call flow, and fallback chain
Complete lifecycle of an inbound church phone call — Twilio SIP trunk, LiveKit Cloud SIP gateway, Railway agent worker, church routing by phone number, agent selection, and post-call DB writes
Canonical reference for all hosting, domains, environment variables, cron jobs, DNS configuration, voice agent deployment, and monitoring across the ChurchWiseAI portfolio
Buy a local Twilio number for a church, configure forwarding to the Cartesia voice agent, and create the church_voice_agents row to make the church live on the agent
Twilio phone numbers and SMS used for voice call forwarding to LiveKit Cloud, callback request notifications, ops SMS alerts, and PewSearch lead notifications
Resilience and fallback design for the voice agent — LLM, TTS, STT provider fallbacks, routing fallbacks, cache stale recovery, and the planned Telnyx migration from Twilio
Step-by-step guide to provisioning a new church on the voice agent — church_voice_agents DB row, Twilio number setup, demo church configuration, and what is automated vs manual
Known voice agent issues, debugging procedures, and resolution steps — LiveKit/SIP routing errors, wrong church routing, tool failures, audio quality issues
Index of voice ops runbooks — add churches, debug call issues, deploy code changes, handle missed calls, review prayer requests, audit call quality, and respond to platform outages