What is interruption handling?

Interruption handling
Interruption handling is how a voice assistant reacts when a caller speaks while it is still talking, deciding whether to stop, continue, or wait before responding.

What interruption handling means in practice

Humans interrupt constantly and barely notice. Half of it is not really interruption at all, just noises meaning go on.

Stop the moment any sound arrives and a cough kills the sentence. Ignore everything until the reply finishes and the caller is talking to a wall.

Good behavior needs a judgment about what the sound was. A short acknowledgement means keep going; a full sentence means stop and listen.

Getting it wrong is the most common reason a call feels robotic, more than the voice itself does.

What people get wrong

Water through the ceiling, two seconds in

Say a plumbing company's assistant opens with a 12-second greeting: Thanks for calling Ridgeline Plumbing. This call may be recorded. I can book a visit, check on an appointment, or take a message for the team.

Two seconds in, the caller talks straight over it: Yeah, hi, I've got water coming through my kitchen ceiling.

A system with no interruption handling finishes all 12 seconds. The caller's sentence lands on top of the greeting, part of it goes unheard, and they have to say it again, louder and less politely. A system that handles it well stops talking within a few words, takes in the whole sentence, and responds to the ceiling.

Later in the same call, the assistant is reading back an address and the caller says mm-hm partway through. That isn't an interruption. Linguists call it a backchannel, a small noise meaning I'm following, and stopping for it would be as wrong as plowing on was earlier.

Five things to try on a demo call

Talk over the greeting with a full sentence, as above, and see whether your sentence was understood without repeating it.

Say uh-huh or OK in the middle of a long reply. The assistant should keep going. Then cough, or rustle a hand over the phone, and it should keep going through that too.

Call on speakerphone from a car or a kitchen. Speakerphones feed the assistant's own voice back into the microphone, and a weak system hears itself and keeps stopping mid-word.

Finally, interrupt with a correction. When it reads back Thursday at 2:00, cut in with no, Tuesday. Check the transcript afterward to see whether it caught the change.

Run all five from your own phone. A vendor's staged demo uses a good headset in a quiet room, and your callers will be standing in a flooded kitchen.

How GreetKeeper handles it

The assistant stops when a caller genuinely starts speaking, rather than at any noise on the line.

Where it gets it wrong, the transcript shows exactly where the two of them collided, which is usually a wording problem in a long reply.

Short replies are the practical fix. A greeting of eight words gets interrupted far less than one of thirty.

Interruption questions

Can a caller skip the greeting?

Yes. Somebody who starts talking over the opening line gets listened to, which is how a person would behave.

Does background noise cause false stops?

It can, on a bad line. A caller in a car or on a building site is the hardest case, and shorter prompts reduce the damage.

How is it different from barge-in?

Barge-in is the older term from menu systems, meaning pressing a key or speaking over a prompt. Interruption handling covers the full conversational version.

Related terms

Hear it take one of your calls

Two minutes, your own scenario, no card.