Judge the Voice Agent on Handoff and Resolution, Not the Demo
Voice agent demos are built to succeed. Callers ask questions the scripts expect, the voices answer cleanly, and the room hears a natural reply. That is the happy path.
Place the call yourself, against a brief the business has already written. Listen for three things: whether the voice stays inside approved facts, whether it stops when a person must take the job, and what that person receives. Handoff and resolution live there.
The calls below are examples of what to ask, not measured results.
Start with the page the voice is allowed to use. It should fit on one screen that a manager can edit and include the business name, the hours, what "closed" means, what the business offers, what it declines, and how a standard booking works. Prices that change by job stay off the page. So does any promise about when someone will call back, unless a named person already keeps that promise, including after hours.
An answer missing from the page means the voice stops. A polite voice with an empty brief will fill the gap, and the caller will repeat that invention to someone who never approved it. Name who updates the page the day hours or services change. An unowned page fails the test on its own.
Does it stay inside approved facts?
Call from a number the system does not already know, on a line you can hear.
Example, first call. Ask one question copied from the approved page, such as "Do you work in this city?" You should hear that fact as written or a short restatement of it. A new city, a new service, or a softer policy than the page allows is a miss.
Example, second call. Ask something absent from the page: a price the business quotes case by case or a job it does not offer. Listen for a number, a discount, a timeline, or any sentence that commits the business to unlisted work. The acceptable reply is a plain stop. The answer sits outside what the voice might give, and a person or a message is the next step.
Phrases such as "typically," "most customers," "around," and "we should be able to" smuggle in estimates nobody wrote down. An approved answer is language someone can point to on the page.
When it must stop
Write the stop list before the meeting, then make the voice hit it:
- The caller asks for a person, by name or with words such as "representative" or "someone who works there."
- The caller is upset, or is reporting a problem with work already done.
- The question is absent from the approved page.
- The voice has failed to understand after a second try.
- The next step is hard to undo: a refund, a cancellation, or an exception to a written policy.
Example. Midway through a routine question, say "I need to speak to a person." The voice should leave the help path on that turn, hand the call over, or take a message that records the request. Another troubleshooting question, however warm, is a miss.
A completed stop has a sound. The caller hears one clear sentence: a person is taking this, or a message has been taken and a named role will see it. After hours, that sentence points to a record a named person will open. A transfer into a queue or a phone nobody answers leaves the caller without a destination. Complaints, custom quotes, and policy exceptions stay with the person who can settle them.
What the person receives
A call can sound finished and still leave no work behind. Treat resolution as the packet on which a person can act. Open the record and read it without a guide from the meeting. It should carry the following:
- Who called, and a number the team can use.
- What the caller asked, in the caller's terms.
- What the voice said, especially any fact it stated.
- The outcome: booked, message, or handoff.
- The owner of the next step, and the backup if that person is unavailable.
Example. The caller asks for a service absent from the approved list. A completed resolution names the request, states that it sat outside the list, and lands with a person who can decide. The caller hears that a person has it. The person can see what was promised without replaying the audio.
Apply the same test to booking. A time the voice offers should already appear on the calendar the team trusts, and it should be a time the business can keep. When that calendar is unready, collect preferred times in a message. A slot composed on the call is an unapproved fact. If the number matches an existing contact, put the packet there so the handoff has one home.
Five checks in the room:
- Read the approved-facts page before any feature list. That page is what the voice must obey.
- Place the approved question and the unapproved question yourself. The second call must stop.
- Ask for a person, and confirm the voice stops on that turn.
- Open the record and confirm the outcome, the owner, and the backup. If you need a tour to find them, the team will miss them.
- Ask what happens when the named owner does not pick up, including after hours. The answer should name a backup and a record the morning owner will see.
Rules about recording a call, and about telling a caller they are speaking with software, vary by place. Take those questions to the buyer's own advisor.
A demo shows that a voice can speak a rehearsed path. The call you place shows whether the business still owns the facts, the moment the system must stop, and the packet a person receives. Judge the voice agent there.
James Weir is founder and owner-operator of Ember Army, an artificial intelligence automation and business-systems company in Rockwall, Texas.