AI Systems
Voice AI: a phone call doesn't wait
Built as a system, not a chatbot that talks
For many businesses the phone is still where customers start, and it's the hardest channel to cover: calls happen in real time, after hours, and at the busiest moments. Voice AI makes it possible to answer, understand and act on calls when nobody is free to pick up.
That only holds when it's built as a system with rules, integrations and a way out to a person. The conversation and the record are kept separate: a call's outcome is saved first and synchronised afterwards, so a downstream outage never loses the call.
Six parts that have to agree
01
Telephony
Where calls arrive
Receives, routes and transfers calls on your existing numbers: every call, after hours only, or overflow.
02
Voice runtime
Hearing and speaking
Speech recognition, the model conversation and speech synthesis, fast enough that a reply feels like a reply.
03
Business rules
What it may decide
Hours, service areas, qualification questions and what it may book on its own, in configuration your team can change.
04
Integrations
What it can do
Bounded actions on your CRM, scheduler and messaging, such as “find a slot” or “create a callback”, never open-ended access.
05
Escalation
The way out
Live transfer or a callback, on conditions written as rules rather than left to the model's judgement.
06
Monitoring
How you know
Every call's transcript, outcome and failures, reviewed and turned into tests for the next version.
When the call goes to a person
The call is saved before anything else
- done
Save the call record
- done
Book in the scheduler
Thu 08:00–10:00
- done
Update the CRM
- done
Text a confirmation
- done
Notify the office
Booked, confirmed and visible to the office before the caller hangs up.
- done
Save the call record
- failed
Book in the scheduler
not responding
- done
Tell the caller
“we'll text to confirm your time”
- done
Retry the booking
10:42, slot still free
- done
Text a confirmation
The call was never at risk. It was saved first, and the booking went through when the scheduler came back.
- done
Save the call record
name, address, issue so far
- not started
Book in the scheduler
- done
Create a callback task
for the office
- done
Notify the office
Half a call is still a lead. What was said is saved, and someone calls back.
What voice AI hands off
In
Out
Worth building when the phone is where work starts
Good fit
- Phone-heavy intake where the questions to ask and the next steps can be written down as rules.
- Calls are missed after hours, during jobs or at peak times.
- There's a CRM or scheduler where the outcome should land.
Not the right fit
- Calls need specialist judgement from the first sentence.
- The consent and recording requirements for AI-handled calls haven't been reviewed for where you operate.
Questions about voice AI
Will callers know they're talking to AI?
They should. The call opens with a disclosure, and consent and recording wording is reviewed for where you operate.
What happens when it doesn't understand?
It asks once more, then offers a person or a callback. It never guesses at an address, a time or a price.
Which voice platforms do you use?
Twilio for telephony and a voice runtime such as Vapi or Retell are common starting points, or a direct voice architecture where that fits better. These are starting candidates, not requirements.
Can it make outbound calls?
It can return calls a caller asked for. Unrequested outbound calling has its own consent rules and is a separate decision.