Mixed-language numbers and dates need explicit interpretation before they become business data. A plausible timestamp is not enough when the caller intended a different day, time, or house number.
Numeric meaning depends on context
Mixed-language numeric intake captures values expressed through more than one language or notation. It can involve spoken digits, full number words, local calendar expressions, and a written representation used by the backend.
In a proposed field model, retain the raw recognised phrase, intended field, interpretation context, and caller-confirmed normalised value. Resolve ambiguity before a consequential write. A date parser should not choose silently between competing locale conventions.
Separate display format from the stored meaning. A date can be shown in the caller’s preferred language while the system stores an unambiguous representation with the required timezone. The conversion must preserve the agreed business time.
Exercise a fictional date and number correction
A caller says an appointment date in English, then corrects the day using Urdu. Later, they give a house number as separate digits in a different language. The expected fixture should identify the final intended date and address independently from whatever the recogniser first produced.
Add a written fixture containing “04/05” with no locale context. The expected behaviour is clarification, not assuming that the model’s default date convention matches the caller’s. A valid parsed date can still be the wrong appointment.
| Ambiguous input | Expected resolution |
|---|---|
| Numeric date without locale | Ask for the month or explicit date |
| Correction in another language | Update the current field revision |
| House number versus quantity | Interpret within the active field |
| Time without timezone context | Establish the business location or zone |
| Unclear digit under noise | Request a focused repeat and confirm |
Test both the spoken readback and the persisted value. The assistant might say the correct date while an adapter stores a differently interpreted timestamp.
Clarify only the consequential uncertainty
Asking callers to repeat an entire address because one digit is unclear increases friction. Identify the uncertain part and keep already confirmed information. If a correction changes a pending action, invalidate the superseded proposal before proceeding.
Normalisation makes records searchable and interoperable, but aggressive coercion can hide ambiguity. Prefer explicit unresolved states over fabricated precision. Native-speaker review should validate expected interpretations and acceptable clarification wording.
This intake design is proposed. The HVAC case study documents service-address capture without claiming multilingual numeric benchmarks. See stale-state prevention.
Mixed-language values FAQ
Is a successful date parse evidence of caller intent?
No. It establishes only that one interpretation was syntactically valid.
Should the latest number always replace the earlier one?
Only when the context establishes that it is a correction to the same field.
What should happen when ambiguity persists?
Keep the field unresolved and use the approved clarification or staff path before a dependent action.