Phone System (optional)
Your existing PBX/softphone (e.g., Teams, RingCentral, 3CX). Can ring your team first, then forward to the AI line.
Works with your existing phone system and CRM. Swap examples below for your stack.
If your team answers first, the AI handoff is skipped—business as usual.
Your existing PBX/softphone (e.g., Teams, RingCentral, 3CX). Can ring your team first, then forward to the AI line.
Owns the number and routes calls (e.g., Twilio, Telnyx, Plivo). We configure a secure SIP route to the AI.
Runs the voice AI: speech‑to‑text, understanding, and lifelike text‑to‑speech—optimized for lead capture and triage.
Our always‑on cloud service that tracks sessions, logs outcomes, and posts results to your automations.
Source control. When we push changes, production auto‑redeploys (zero downtime).
Receives webhook JSON and runs steps (e.g., Zapier, Make, n8n) such as create/update records and send notifications.
Where your team sees new requests—works with HubSpot, Salesforce, Zoho, ServiceTitan, Jobber, Google Sheets, email, etc.
If your team answers first, the AI route is skipped.
What happens if any service has an outage?
Calls still start on your carrier/phone system. If forwarding or SIP is down, the fallback is for your team to answer as usual (or voicemail). Issues in the orchestration app/VoiceExcel only affect the AI handoff.
How do we pause the AI?
Disable the forwarding rule or SIP route, or ask us to pause the orchestration app.
Where do the results go?
Into your chosen destination—CRM, helpdesk, Google Sheet, or email. Automation history shows each step and any errors.
How do we change the script?
We edit the configuration/code, push to GitHub, and production auto‑redeploys.