Agents
Voice AI
Agents that handle spoken conversations, with the same boundary and the same escalation path as everything else.
Voice is the same machinery as a text agent with a different input. The rules, the tools and the boundary are identical; what changes is that the person on the other end cannot scroll back, cannot re-read, and is considerably less patient.
That impatience shapes the design more than the technology does.
What does an AI voice agent do?
An AI voice agent answers or places calls, understands what the caller wants, looks up what it needs in your systems, and either resolves the call or hands it to a person. Compared with the voice menus most people have encountered, the difference is that the caller talks normally instead of choosing from four options.
It says what it is
Every voice agent identifies itself as an automated system at the start of the call. That is not only a legal position, though in several jurisdictions it is heading that way. It is a practical one: a caller who works out halfway through that they have been talking to software feels tricked, and that feeling attaches to the company rather than to the vendor.
Handover happens mid-conversation
The hard part of voice is not understanding speech, it is knowing when to stop. A caller who becomes frustrated, a question outside the documented scope, a request that touches money: each of those is a trigger to bring in a person.
When that happens the call transfers with what has been established so far, so the caller does not start again from their name. A handover that loses context is worse than no automation, because the caller has now spent time twice.
What it is not used for
Not outbound sales calls to people who did not ask to be contacted. Not conversations about a complaint. Not anything where the caller is likely to be distressed.
Those are all technically possible. Each of them trades a real reputational risk for a modest saving, and none of them is a good trade.
Transcripts
Every call produces a transcript, kept for the period agreed in the data processing agreement and searchable afterwards. That serves the same three purposes as any other log: resolving disputes, improving the rules, and being able to answer the question of what exactly was said.
More on agents
The other parts of this chapter.
Agents
The core of the platform. An agent reads a request, checks it against your rules, acts in one of your systems, and reports what it did.
Agentic tools
The specific actions an agent may take in your systems, granted one at a time rather than as blanket access.
Workflow logic
The written rules that decide what an agent does in each situation, including the situations nobody thought of.
Where this shows up
The services this part of the platform does its work in.
Which task would you hand over first?
Tell us which part of your operation eats the most hours. We map out what an agent can take over and what it cannot.
