Voice agents, telephony operations
A service business wins and loses work on the telephone, and for roughly two thirds of every week the telephone is unattended. This is a four-agent voice team built to cover it.
The problem
For a contractor, a missed call is not a missed message. It is a customer who dials the next name on the list while your voicemail is still playing, and you never learn it happened.
The arithmetic is unkind. A working week is 45 hours out of 168. Evenings, nights and weekends are when a panel fails, an alarm sounds and a tenant calls a property manager. The hours when work is most urgent, and therefore most valuable, are precisely the hours nobody answers.
The usual answers are an answering service that takes a name and a number, or voicemail. Both defer the actual work, which is finding out what the job is.
The team
A single agent asked to greet, qualify, sell and support does all four badly. The objectives conflict: a receptionist should be brief, a closer should not be. Separating them means each has one job, one measure, and its own escalation rules.
Answers inbound calls in two languages, establishes what kind of job it is, captures the details a quote will need, and reads urgency. Every call is transcribed and written to a session record that the rest of the operations system reads, so an evening call is a structured job by morning rather than a note.
Calls inbound leads that arrived as web forms or purchased broker leads, while they are still warm, and establishes whether there is a real job before a human spends time on it. Speed matters more than polish here: a lead called back in five minutes converts at a different rate to one called back the next day.
Works the quotes that were sent and never answered, which in most service businesses is the single largest pool of recoverable revenue in the building. It asks what stopped the customer, answers the ordinary objections, and hands anything real to a person rather than pushing.
A number an existing customer can call to ask about their own job. Where their file is, when the technician is due, what the invoice covers. It answers from the live record rather than guessing, and it exists mainly to stop the office being interrupted forty times a day by questions the system already knows the answer to.
Architecture
Speech is a solved problem, and treating it as the product is the common mistake. What makes a voice agent worth paying for is what happens in the four seconds after the caller hangs up.
The call ends, a webhook fires, the transcript and the extracted fields land in a session record, and that record is read by the same pipeline that handles every other kind of enquiry. A call becomes a job in the same shape as a web form. If it does not, you have bought a very expensive answering machine.
In-call tools are what separate a script from an agent: looking up whether this caller is an existing customer, checking a real calendar rather than promising a slot that does not exist, and raising an alert to a human while the caller is still on the line.
Hard parts
An in-call tool that fails does not announce itself. The agent simply carries on sounding fluent while the lookup, the booking or the escalation never happened. This is the single most dangerous property of voice systems: they degrade into confident uselessness rather than stopping. Every tool call needs its own monitoring, tested against a real call rather than a simulator.
Recorded and transcribed calls carry consent obligations, and they vary by jurisdiction. The disclosure has to be in the opening line, worded so it does not cause a hang-up in the first five seconds, and it applies to outbound calls as much as inbound ones. It is the sort of detail that is trivial to build in and expensive to retrofit.
An agent that will not hand over to a human is worse than no agent. Emergencies, angry callers and anything the agent has failed twice to understand should escalate immediately, and the escalation path itself has to be tested, because it is the one path nobody exercises until it matters.
Transfer
Any business where the phone rings outside office hours and the caller has an urgent problem.
Fire and life safety, electrical, mechanical, elevator, restoration, facilities. The common shape is an emergency line, a dispatch obligation, and an office of two to seven people who cannot cover 168 hours a week no matter how committed they are.
The measure is not how human it sounds. It is how many enquiries became structured jobs without a person reading them, and how many callers stopped dialling the next name on the list.
Contact
If you know roughly what your phone does after five o'clock, tell me. If you do not, that is usually the more interesting answer.