Plain-English answers
Every AI voice agent runs the same three-part loop for the whole call: speech-to-text transcribes the caller in real time, a language model decides what to say and what to do, and text-to-speech speaks the reply in a natural voice. That loop is shared technology across the industry. What separates a useful agent from a demo toy is everything wrapped around it — the written instructions, the integrations, and the guardrails.
Last updated: July 2026
Our plain-English explainer covers what an AI voice agent does on a call. This page is for the people who want to know how — what is actually happening in the second or two between a caller saying something and the agent answering. You don't need any of this to use one, but knowing the moving parts makes it much easier to judge vendors and understand why some agents feel sharp while others feel like a laggy phone menu.
The caller's audio is transcribed into text in real time, while they're still talking. Good systems handle accents, background noise from a job site, and people talking over the agent.
The transcript goes to a language model — the same family of technology behind modern AI chat tools — along with instructions about the business: what it does, what it charges, what counts as an emergency, what information to collect, when to transfer. The model decides what to say next and, crucially, what to do: book the slot, flag the emergency, take the message.
The reply is synthesized into a natural-sounding voice and played back to the caller. Modern neural voices breathe, pause, and inflect; this is why callers often don't clock that they're talking to software.
Then the loop repeats. The whole round trip has to happen fast enough to feel like conversation — long gaps are the tell of a poorly built agent, and it's one of the first things to listen for when you test one on a live call. It's also what separates this from a phone tree, which never leaves the menu it was recorded with — see AI receptionist vs. IVR phone tree.
The three-part loop is largely shared technology across the industry. What separates a useful agent from a demo toy is everything wrapped around it:
The written instructions that define what this agent knows, what it's allowed to promise, and what it must never do. A generic template says "I'll have someone call you back." A custom-built agent knows your service area, your after-hours rules, and that you don't do commercial work.
Real usefulness comes from actions: checking a calendar and booking into it, writing the caller into a CRM, sending a follow-up text, transferring the call to a human. This is integration work, which is why it's the part we build custom to each business.
Rules that keep the model from improvising where it shouldn't — quoting prices it wasn't given, agreeing to work outside the service area, or talking when it should be transferring.
There's no box in your office. The agent runs in the cloud, attached to a phone number. Calls can go straight to that number, or your existing number can forward to it after hours, on overflow, or full time — your current phones and number stay exactly as they are.
The loop above is powerful but not magic. Agents mishear in heavy noise, and a well-built one asks to confirm rather than guessing. They only know what they've been given, so a question outside their instructions should trigger a message or a transfer, not an invented answer. The craft is in building the agent to fail gracefully — when a call goes past what the agent was built for, the right behavior is to say so and hand off to a person.
Three components in a loop: speech-to-text transcribes the caller in real time, a language model decides what to say and do based on written instructions about the business, and text-to-speech plays the reply in a natural voice. The differentiating work is in the instructions, integrations, and guardrails around that loop.
No hardware — the agent runs in the cloud attached to a phone number. Your existing number can forward to it after hours, on overflow, or full time, so your current phone setup stays as it is.
Each conversational turn requires transcription, a model response, and voice synthesis. Poorly engineered agents stack up delay in that round trip, which is why long pauses are one of the clearest signs of a weak build. Testing an agent on a live call reveals this immediately.
From the instructions and data it's built with: your services, pricing rules, service area, emergency criteria, and booking calendar. A custom-built agent is configured to your operation rather than a generic template, which is the difference between taking a message and actually handling the call.
Our demo line is answered by one of our own agents — interrupt it, ask it something odd, and listen to how it recovers. If you want one built around your business, the first agent is free to build: no cost, no contract, and you decide afterward whether to keep it.
Ask Custom Voice Automations
Usually replies instantly