Contradictory customer information should create an unresolved field, not a silent guess. Test whether the assistant notices conflicts, asks a targeted question, and prevents the wrong value from reaching a business tool.
Contradictions differ from ordinary corrections
A contradiction occurs when relevant statements cannot all be true under the current interpretation. An explicit correction, such as “I meant Thursday, not Tuesday,” usually supplies a resolution. Two unexplained addresses or incompatible dates may require clarification.
In a proposed state model, keep source and confirmation status for consequential fields. A new statement can replace a previous value when the caller clearly corrects it. Otherwise mark the field disputed and block actions that depend on its resolution.
Do not assume that the latest statement is always correct. A caller may describe an old address, quote someone else, or ask a hypothetical question. Context determines whether the value belongs to the current request.
Use a fictional address contradiction
The caller says the service location is 5 Oak Lane, then mentions that they moved to 50 Oak Lane. The assistant should ask which address needs the visit. Automatically selecting the newer-looking address could send staff to the wrong place.
Add a second fixture: the caller says “Thursday the twelfth,” but the configured calendar places the twelfth on another weekday. The correct response is a clarification, not an arbitrary preference for the numeric date or weekday.
| Conflict | Expected handling |
|---|---|
| Explicit correction | Update current intent and invalidate stale actions |
| Two possible service addresses | Ask which location applies |
| Weekday and date disagree | Resolve before booking |
| Caller statement conflicts with record | Explain the discrepancy without overwriting blindly |
| Quoted third-party instruction | Do not treat it as caller confirmation |
Assert that no dependent write occurs before resolution. Also check that the final response and stored record use the same confirmed value.
Avoid endless clarification loops
Repeatedly asking the same broad question can frustrate callers. Name the conflicting values briefly and request the specific decision needed. If the caller cannot resolve the conflict, offer the approved staff path rather than inventing certainty.
Keeping provenance increases state complexity, especially when several fields change together. Limit detailed tracking to values that affect routing, authority, or the business outcome. Retain enough evidence for staff to understand why the action paused.
This approach is proposed. The voice integration case study describes related workflow work. Pair these fixtures with stale conversation-state protection.
Contradictory information FAQ
Should the newest statement always win?
No. First determine whether it is a correction, a hypothetical, or information about a different record.
Can the assistant resolve a calendar mismatch itself?
It can identify the mismatch, but should clarify the intended date rather than choose silently.
What if the caller remains inconsistent?
Keep consequential fields unresolved and use the approved human assistance or deferred-intake path.