Interrupting the assistant’s speech must not silently change whether a booking executes. Test the audio boundary and the business-action boundary separately, especially when the caller corrects a date during confirmation.
Interruptions can carry different intent
An interruption may be a correction, a question, background speech, or a request to stop. The agent needs to identify the relevant conversational intent while the application manages any pending operation independently.
For a proposed test plan, place interruptions at known points: during a question, during readback, after confirmation, while a tool runs, and after a write completes. Each point has a different expected state. Stopping playback is not evidence that a queued write was cancelled.
Record speech events, intent revisions, tool start and completion, and final business state under one interaction reference. Without that timeline, a reviewer may hear a natural recovery while missing that the old appointment was also created.
Exercise a fictional date correction
The assistant reads back “Tuesday at ten,” and the caller interrupts with “Thursday, please.” If confirmation has not occurred, update the proposal and ask for confirmation of Thursday. No Tuesday appointment should be created.
If the interruption arrives after the booking commits, the system must treat it as an amendment request. It should establish the existing appointment state before making another write. Telling the caller “I stopped that” would be inaccurate unless cancellation actually succeeded.
| Interruption point | Expected invariant |
|---|---|
| During date readback | No implied confirmation from partial playback |
| Before write begins | Superseded proposal cannot execute |
| While write is uncertain | Reconcile before replacement |
| After confirmed booking | Use the authorised amendment path |
| Unrelated background speech | Avoid inventing a new caller instruction |
Use precise harness timing and repeat boundary cases. Human testers interrupting approximately at the same phrase may miss the narrow race that creates duplicate or stale writes.
Recovery should preserve usable context
A good interruption response resumes from the current intent, not from the beginning of intake. Retain confirmed identity and contact details while invalidating any consequential proposal that changed. Ask a focused follow-up when the interruption is ambiguous.
More aggressive interruption detection can make the agent responsive but also vulnerable to background speech. Less aggressive detection can force callers to talk over long readbacks. Measure both incorrect interruptions and missed corrections alongside task outcomes.
This test design is proposed. The voice platform case study describes related workflow work. Pair it with pending-action cancellation for the execution-side controls.
Booking interruption FAQ
Does stopping speech stop the booking?
No. Playback and tool execution need separate state transitions.
Should an interrupted readback count as confirmation?
Not unless the workflow obtains a clear, valid confirmation of the complete current proposal.
What should happen after a late correction?
Determine the original operation’s outcome, then use the supported amendment or cancellation process.