A caller correction must reach every agent whose work depends on the changed field. Updating only the conversational agent can leave a specialist returning stale options or an executor writing the superseded value.
Corrections invalidate dependencies
Cross-agent correction handling updates the current intent and identifies which proposals, lookups, and actions are no longer valid. Not every correction requires restarting the entire workflow, but every dependent stage needs a freshness boundary.
For a proposed state model, give confirmed intent a revision and track relevant field dependencies. Handoffs and results carry their input revision. The orchestrator rejects stale consequential output or reconciles it according to the current task.
Do not assume message broadcast order establishes correctness. Agents can process corrections late, and a remote effect may already be in flight. The execution boundary must check current state independently.
Follow a fictional address change
The intake agent sends a service-area task for 14 Elm Road. The caller corrects the address to 40 Elm Road while the specialist is working. The old coverage result should not authorise a request for the new location.
If a save already began, the system must determine whether it committed before deciding to cancel, amend, or create a new proposal. Merely replacing the address in a summary does not repair a stored request.
| Correction boundary | Expected handling |
|---|---|
| Before handoff | Only current fields sent |
| During specialist analysis | Returned result checked against current revision |
| Before execution | Superseded proposal blocked |
| During uncertain external write | Reconcile original outcome |
| After confirmed write | Use authorised amendment workflow |
Replay the correction at controlled times and inspect all affected records. Include a late specialist response after the revised task completed to ensure it cannot revive old work.
Preserve unaffected confirmed information
A changed address should not erase a verified callback number or unrelated caller preference. Keep field-level relevance where practical and ask only the clarification needed for the new proposal.
Dependency tracking adds state complexity. A coarser revision can be simpler but invalidate more work than necessary. Choose the smallest design that prevents stale consequential actions and produces understandable recovery for staff.
This correction design is proposed. The voice platform case study describes related workflows without claiming this multi-agent controller. Pair it with pending-action cancellation.
Cross-agent correction FAQ
Is updating the coordinator’s summary enough?
No. Dependent work and the final execution boundary must account for the current intent.
Should every correction restart all agents?
Only if necessary. Preserve unaffected valid context and invalidate relevant work explicitly.
What if the old action already completed?
Establish its authoritative outcome, then follow the supported authorised amendment or compensation process.