Replace the corrected selection, preserve unaffected details and recheck dependent answers before carrying the state into the next turn.
The old answer has a dependency
“Sorry, A5.” The caller has changed one detail. A response that politely acknowledges the correction and then repeats “40 sheets” has still answered for the wrong notebook.
Start with a small description of the active request. In this fictional example, it is an A4 notebook, plain pages, green cover, and a question about sheet count. The supplied source lists 40 sheets for A4 and 24 for A5. Correcting the size should replace A4 with A5 while retaining the other details. The sheet count needs checking again because it depended on the old size.
This article rehearses a read-only information conversation. The products and dialogue are invented. The exercise below can be completed on paper. It makes no claim about speech recognition, a microphone, a live assistant or any particular platform’s ability to handle interruptions.
Trace the change before looking up the answer
Copy this fictional source into your review sheet. It is the entire catalogue for this exercise: NB-A4 is an A4 notebook with 40 sheets; NB-A5 is an A5 notebook with 24 sheets. Both are available with plain pages and a green cover. There is no A6 entry. These are invented products and quantities.
Begin with the active request: size A4, page style plain, cover green, sheet count 40, evidence NB-A4. Write the caller's next turn beside it: “Sorry, A5.” Before consulting the new source, record the expected intermediate state:
| Field | Before | After the correction, before rechecking |
|---|---|---|
| Size | A4 | A5 |
| Page style | Plain | Plain |
| Cover | Green | Green |
| Sheet count | 40 | Unknown pending the new lookup |
| Sheet-count evidence | NB-A4 | Invalid for the new selection |
Now consult NB-A5. Record 24 sheets and NB-A5 as its evidence. An illustrative response is: “A5, with plain pages and a green cover. The A5 notebook has 24 sheets.” Follow with “And how many sheets did you say?” The expected answer remains 24 for A5.
Your output is a trace with the caller turn, before state, replacement, retained fields, invalidated facts, new source and later-turn check. Keep a separate blank column for observed implementation behaviour. Filling in the expected answer here does not establish that a real voice product passed.
Week 27 · Fictional local practice
Make the correction visible
Use the complete fictional source in the article. Record choices, retained evidence and unresolved limits.
Use fictional, non-sensitive values only. Entries remain in page memory. No uploads, storage or network requests are made by this activity. Copy and print occur only when selected.
Stationery A v1
NB-A4: A4 / plain / green / 40 sheets.
NB-A5: A5 / plain / green / 24 sheets.
A6 is deliberately absent. No other products are implied.
Active request
Question: sheet count. Source: Stationery A v1, row NB-A4.
Transition trace
No turns applied. Starting state: A4 / plain / green; question: sheet count; sheets: 40; answer: verified; source: Stationery A v1, row NB-A4; clarification: clear.
Fictional text simulation correction-trace-v1 Language: English. No microphone, live assistant, ordering or measured product results. Active state: A4 / plain / green; question: sheet count; sheets: 40; answer: verified; source: Stationery A v1, row NB-A4; clarification: clear
Use the text-only exercise
The complete unchanged manuscript remains readable if the controls are unavailable.
Return to Trace the change before looking up the answerA comparison leaves the selection alone
For a separate case, start again from the original A4 request and use “Does the A5 version have fewer sheets than the A4?” The supplied source supports a comparison: 24 versus 40, so A5 has 16 fewer sheets. The selected notebook remains A4. Merely mentioning A5 has not expressed a replacement.
That distinction matters when a caller explores alternatives before deciding. A useful repair record separates what was discussed from what was selected. The trace can contain both sizes; the active selection must be unambiguous.
An unclear correction needs a narrow question
“That’s wrong” identifies a problem without saying what should replace it. Keep the known details visible and ask which detail is wrong: size, page style, cover colour or sheet count. Do not guess A5 just because it is the other item in this small source.
In this exercise’s expected behaviour, clarification remains required even if the caller asks for the sheet count again. A new, explicit size correction resolves that ambiguity. In a real conversation, the clarification must also support other fields; this bounded example rehearses size changes only.
Microsoft’s HAX correction guidance encourages making it straightforward to edit, refine or recover from an AI error. The field-level trace is one way to turn that principle into something inspectable.
When the new entry is missing, keep the answer unknown
Try “Sorry, A6.” The source deliberately contains no A6 entry. Rechecking therefore leaves the sheet count unknown. The presence of an earlier 40 or 24 in the trace provides no basis for attaching it to A6.
The same discipline applies beyond notebooks. If a caller changes a service variant, location or date, identify which earlier facts depended on that choice. Check those facts against the new source. Preserve genuinely unaffected details, and keep unresolved facts explicit.
An explicit later “Actually, A4” is a new instruction and can select A4 again. A later sheet-count question alone cannot revive it. This makes the latest clear selection govern the answer without treating historical mentions as new choices.
Carry the expected state into a real test
For each case, retain the fictional source version, exact caller turn, expected field changes, expected response and a later-turn check. Add an observation column for the actual implementation. Leave that column empty until someone runs it.
- Test a correction before, during and after an answer, where the chosen platform supports those timings.
- Try a repeated correction, a second explicit replacement, a comparison and a missing source entry.
- Check meaning and source use rather than demanding one exact sentence.
- If the correction remains unclear, stop guessing and use the established alternative information route. This written exercise cannot establish audio interruption, response time, privacy or transcript deletion. Removing A4 from the active request changes conversational state; it does not mean historical logs have been erased.
Read the design guidance with its date attached
Google’s still-readable confirmation and correction guidance describes one-step corrections and asking what should change without forcing a full restart. It is legacy Actions-era design material. Google ended Conversational Actions on 13 June 2023; these examples do not establish a currently available Google implementation path.
For the earlier channel decision, read Website Chatbot or Voice Assistant? Choose the Right First Channel. This rehearsal becomes useful once you know why a spoken conversation suits the task.
Practical next step
Sources checked 4 October 2026
Sources & review
Primary sources checked on . The checklists and planning examples are AI-assisted editorial guidance, not source quotations or reported client results.
- Microsoft HAX Support efficient correction
- Legacy Google Conversation Design Confirmations
- Google Conversational Actions sunset
This AI-assisted guide uses fictional examples for practice. It does not report client results or establish that a live system will behave the same way.
Originally published: .