The bot handles its own trouble in understanding: ambiguity, low confidence, conflicting entities, or missing slots.
- A → U: Signal trouble concisely and offer a candidate understanding or targeted question (disambiguate, confirm, or request a missing value).
- U: Provide clarification or choose an option.
- A: Acknowledge and resume the primary activity at the right step.
- U (Optional): Sequence closer (see sequence completion).
When to use
- Confidence below threshold; overlapping constraints (“size” could mean volume or dimensions).
- Multiple entity candidates, out-of-range values, or required data missing.
Guidance
- Show interpreted intent + parameters and let the user edit.
- If a specific value is required, transition to information capture*.
Repair affordances
- One-tap buttons for options; “Assume default” (with preview); “See how I understood this.”
Metrics
Repair resolution rate on first attempt; turns-to-repair; wrong-action rate after repair; drop-off during repair.
Related patterns
Precedes
- Inquiry (User) — transitions into information capture when a specific required value is missing
- Sequence completion — the primary activity resumes once repair is resolved
Enables
- Conversation — the bot repairs its own misunderstanding — ambiguity, low confidence, missing detail
Complements
- Capability & scope — out-of-scope requests are a form of scope repair
Related
- Inline interface — inline confirmation and correction checkpoints
- Opening (User) — for disambiguating ambiguous or overlapping user openings
