Skip to content
SignalMD
All posts

Voice agent interrupts callers when they pause for ~1 second

By Andrew

A voice agent interrupts callers in one common way. They pause mid-answer to think, and the agent jumps in.

It is one of the most common problems in voice agents. Dates, numbers and addresses get hit most. A caller stops before the year they were born, or inside a policy number. The agent hears the silence and moves on with half an answer.

The fix is often small. The hard part is knowing it worked on real calls, and that it stays fixed. This post walks through both.

Why a voice agent interrupts callers

A voice agent waits for a short silence, then replies. That silence is its only clue that the caller is done. Make the wait too short, and every thinking pause looks like the end.

Here is how it sounds on Northwind Insurance Claims, a synthetic demo agent. Noah calls about a cracked windshield, and the agent asks for a date of birth.

“Right, it’s June 5,” Noah says. Then Noah stops to think of the year.

About a second later, the agent says “Thanks. Let me pull up your policy.” Noah says “1955.” right over it.

The moment the caller is cut off Two lanes, caller above and agent below, time running left to right. The caller says "Right, it's June 5," and pauses for about a second. The agent starts "Thanks. Let me pull up your policy." The caller's "1955." lands on top of it, and both talk at once for about 2 seconds. Caller Agent Right, it's June 5, pause ~1 second 1955. Thanks. Let me pull up your policy. Both talking: ~2 seconds
The moment in two lanes. Noah pauses for ~1 second, the agent starts, and the year lands on top of it.

Noah got lucky. The year came late, but the agent still found the policy. Next time it may save “June 5” and lose the year. Or it asks again, and sounds like it was not listening.

Nobody sees it on the dashboard

On version 7 of the demo agent, 12 calls went like this. Every one still booked an inspection. Nobody hung up.

A chart of outcomes would glow green. To find it by hand, you would play calls one by one and catch the right second.

SignalMD spots it and names the step

SignalMD reads every call, moment by moment. Here it raised one issue, on the step called Identify caller. It comes with a cause and a fix.

Issue page: the agent takes the caller's pause as the end of the answer, on the Identify caller step. The suggested fix gives that step more time and accuracy, and leaves the rest of the agent as fast.
The issue names the step. The boxed fix changes that step only.

Open any of the 12 calls, and the moment is marked for you.

Transcript where the voice agent interrupts the caller: the caller says 'Right, it's June 5,', the agent replies 'Thanks. Let me pull up your policy.' with a note 'Caller cut off at a pause', then the caller says '1955.'
The note sits where Noah was cut off, just before the year.

Want to see this on your own calls? Join the waitlist.

Fix the step where callers get interrupted

The tempting fix is one slider: make the whole agent slower to reply. It works here, and it costs you everywhere else.

Every reply would wait, even at steps where nobody is cut off. Greetings drag. Quick yes-or-no answers drag. Callers fill the gap with “Hello?”

The cut only happens where callers give a date of birth. So the fix goes there.

Retell lets you change speech settings on a single step, which Retell calls a node. Version 8 changed two of them on Identify caller:

  • More time to finish. The agent waits longer after the caller stops, before it replies. Retell’s builder calls this response wait time.
  • Accuracy mode. The step writes down what the caller says with accuracy first, speed second.

The rest of the agent kept its quick setting.

The change from version 7 to version 8: Identify caller waits longer after the caller stops, and transcribes the caller for accuracy, both on that step only. The old values are struck out.
Two settings, one step. The old values are struck out.

The values in the demo are only an example. Start small on your own agent, then check the calls.

Version 8 carried other edits too, as most releases do. What matters is whether the moment comes back.

How to check the fix is working

A quiet board is not enough. Fewer cut-offs could just mean fewer callers paused.

So start with the callers. They did not change. On version 8, 23 calls still had a caller pause mid date of birth.

The agent waited through every one of those pauses. Not one caller was cut off.

A version 8 call: the agent asks for a date of birth, the caller says 'It's September 24,' then pauses, then says '1973.' The agent does not speak in between.
Version 8. The caller pauses after "September 24," and the agent lets them finish.

Then comes the verdict. SignalMD lines up the two versions on this one moment.

Verdict by version: 'v8 fixed it: none of its 257 calls over 9 days shows it, against 12 of 296 before.'
The verdict in one sentence: fixed on version 8.

Nine days in, none of the 257 calls on version 8 shows it. Version 7 had 12 of 296.

Callers who paused mid date of birth, per day, October 3 to 23 On version 7, from October 3 to 14, the agent cut off every caller who paused: 12 calls, one or two on most days. From October 14, on version 8, 23 callers paused the same way, up to 4 a day, and the agent waited every time. No caller was cut off. Cut off Agent waited 0 1 2 3 4 Oct 3: 2 cut off Oct 4: 2 cut off Oct 6: 1 cut off Oct 8: 1 cut off Oct 9: 2 cut off Oct 11: 2 cut off Oct 12: 1 cut off Oct 14: 1 cut off Oct 14: 2 waited Oct 15: 2 waited Oct 16: 4 waited Oct 17: 1 waited Oct 18: 2 waited Oct 19: 3 waited Oct 20: 4 waited Oct 21: 1 waited Oct 22: 2 waited Oct 23: 2 waited Version 7 Version 8 Oct 3 Oct 10 Oct 17 Oct 23 Calls a day
Callers who paused mid date of birth, per day. Cut off on version 7, waited for on version 8.

After a week with no sign of it, the issue closed itself as fixed. If the cut comes back, it opens again. The guide to comparing versions shows how each verdict reads.

Keep a watch so it stays fixed

The copilot is the chat built into SignalMD. You ask it about your calls in plain words. Here someone asks how often callers are cut off at a pause, by version.

The question 'How often are callers cut off at a pause, by version?' and the copilot's answer: v7, 12 of 296 calls. It offers to make a watch.
Counts by version. Only version 7 has any.

Then they ask for a watch. A watch is a rule your calls should keep. This one covers calls that reach Identify caller. There, the agent must not take a pause as the end of the answer.

The person types 'Make a watch for this'. The copilot's card for calls that reach Identify caller now reads 'Draft created', with a link to open the watch.
Saved as a draft. It does not switch itself on.

On the watch page, a person marks a few sample calls right or wrong. Then they press Turn on. From then on, every new call that reaches Identify caller is checked.

The watch page, marked Draft, with a Turn on button. It applies to calls that reach Identify caller and must not take the pause as the end of the answer. Below, a sample call to mark right or wrong.
The draft watch waits for a person to turn it on.

If a later version brings the cut back, the watch flags it.

Check your own agent

Pull five calls where a caller gives a date, a number or an address. Listen for the agent starting while they are still mid-thought. Or let SignalMD find those moments in every call.

Want to see it on your own agent? Join the waitlist, book a demo, or see the plans.

Common questions

Why does my voice agent interrupt callers?

It replies after a short silence, and a thinking pause sounds the same. Dates, numbers and addresses have the longest pauses. Those answers get cut first.

Should I lower responsiveness for the whole agent?

Usually not. Every reply would wait, even where nobody is cut off. Give more time only on the step where callers pause. In Retell, that is a setting on the node.

How do I know the fix worked?

Check that callers still pause on that step, and that the agent now waits. Then compare the two versions on that same moment. Keep a watch on it, so a later change cannot bring it back unseen.

See what your agent should fix first.

Book a demo to see the whole loop on a real board, from an issue to the verdict on its fix.

We're letting teams in a few at a time. Join the waitlist and we'll email you when it's your turn.