A language change halfway through booking should alter how the assistant communicates while preserving the current business state. Keep confirmed details and recheck only the fields or commitments whose meaning remains uncertain.
Language switches should not reset the operation
Mid-booking language switching occurs when the caller chooses another supported language during an active appointment workflow. The system must retain the current resource, intent revision, verification state, and execution status across that change.
In a proposed design, language preference is a separate session field. Updating it does not create a new booking operation or grant fresh permission. If the switch also contains a correction, process that changed intent explicitly and invalidate any superseded proposal.
Do not assume that confirmation in the first language remains valid when the proposal changes in the second. The relevant question is whether the caller clearly agreed to the same current consequential details.
Follow a fictional booking switch
The caller supplies an address in English and asks to continue in Urdu before choosing a time. The agent retains the confirmed address and offers the actual available times in the supported language. It should not ask for the address again merely because the language changed.
Now place the switch during a pending write. The agent must preserve the operation reference and interpret the result accurately in the new language. A second create request would be a duplicate-effect defect, even if the new conversation sounds like a fresh booking.
| Switch timing | Expected behaviour |
|---|---|
| Before required fields complete | Continue gathering unresolved information |
| During readback | Confirm the current complete proposal clearly |
| Alongside a date correction | Update intent and invalidate the old proposal |
| While write is pending | Retain the existing operation identity |
| After booking completes | Explain the established result accurately |
Evaluate both transcript continuity and final records. Reviewers should check unnecessary repeated questions as well as wrong or duplicate writes.
Keep fallback capabilities visible
If the requested language is not supported for the full booking workflow, explain the actual limit and offer the approved alternative. Do not continue with unreliable comprehension merely because a generic language detector recognises the switch.
Preserving state reduces friction but requires clear field provenance and confirmation tracking. A simpler implementation that restarts everything may avoid some stale-state bugs while frustrating callers and risking duplicates. Separate language preference from operation lifecycle instead.
This design is proposed. The voice platform case study describes related workflows. Pair it with language choice and pending-action corrections.
Mid-booking switch FAQ
Should the agent start the booking again?
No. Preserve valid state and clarify only what changed or remains uncertain.
Can a switch create a second appointment?
It should not. Keep the same logical operation when the confirmed business intent is unchanged.
What if the caller corrects a detail while switching?
Treat it as a new intent revision and obtain any required fresh confirmation before execution.