“I did not understand” is not a conversation strategy. After hearing it twice, the caller only knows the machine is stuck. A repair loop changes the question and has a defined exit.
Three attempts with different jobs
- Confirm the part that was understood.
- Ask only for the missing detail using two clear options.
- After another failure, hand off or capture a callback.
“When would you like to come?” becomes “Was that Tuesday or Thursday?” The assistant gets narrower, not louder. Names, emails and numbers are repeated slowly for confirmation.
Handoff with context, not a restart
- The caller's goal in one sentence.
- Details already confirmed.
- The open question and reason for handoff.
- Consent and verification state where relevant.
The threshold may be two failed repairs, earlier when the caller is upset and later for a simple spelling task. Measure abandonment, repair success and repeats per intent. A high handoff rate is not automatically failure; a correctly rescued call beats a wrong booking.
Sensitive changes also need caller verification. Our AI phone assistant is designed around bounded actions and explicit handoff.
Sources
FAQ
How many retries are reasonable?
Usually one or two targeted repairs, followed by a human or another channel.
What context should transfer?
Intent, confirmed details, the unresolved question and reason for escalation.
Is every handoff a failure?
No. For exceptions and sensitive cases it is part of the intended service.
Which metrics matter?
Repair success, abandonment and wrong execution matter alongside completion rate.