The operational decision
Give the operator authority to stop a failing route while preserving the firm contact path. A reliable intake workflow needs an owner after launch. Staff availability, practice scope and public contact routes change, so the operating record should explain who can update the system and how changes are verified.
Prepare the workflow
Specify defects that require a pause, the responsible role and the tested rollback; do not rely on editing around a serious boundary failure mid-call.
Example wording for approval
“If the example assistant gives legal advice or falsely confirms acceptance, pause that workflow and restore the approved firm contact route before further testing.”
Worked example
A fictional test produces a confident answer saying the firm accepts the matter immediately. The operator should pause the affected intake path, restore the approved firm contact route and send the defect to the designated reviewer. Changing one adjective while leaving the acceptance logic untouched is not enough. Restart requires a corrected version and passing acceptance-boundary tests. The incident record should identify the behavior and configuration, using synthetic evidence rather than circulating a real person's confidential inquiry.
Handoff record
Record these task-specific fields: defect category, pause owner, restore route, restart evidence.
Acceptance check
Trigger a fictional false-acceptance result. The operator should identify the immediate containment step and the evidence needed before reactivation.
Legal intake capacity calculator ↗
Try Ava with your business’s public information ↗