“Yes” is useful confirmation only when the system knows exactly which action the caller accepted. Bind confirmation to the resource, consequences, and current action details before executing a destructive operation.
Destructive confirmation needs a stable proposal
A destructive action removes or materially changes something the caller may depend on, such as an appointment or stored request. Confirmation is an explicit agreement to a particular proposal. It does not replace identity verification, authorisation, or applicable business rules.
In a proposed cancellation workflow, prepare a proposal containing the appointment reference, date, relevant consequence, and expiry. Read back the essential details in ordinary language. Store confirmation against that proposal revision rather than a general session-wide “caller said yes” flag.
If the appointment or requested action changes, invalidate the confirmation. A caller agreeing to cancel Tuesday’s visit has not agreed to cancel every appointment on the account. Avoid asking a compound question whose answer could apply to several different operations.
Test a fictional ambiguous reply
The assistant asks, “Do you want to cancel the Thursday repair visit?” The caller replies, “Yes, but keep the inspection.” The application should identify which records are affected and clarify any ambiguity before execution. It should not infer that all related visits should disappear.
Next, imagine the caller interrupts the readback before hearing a cancellation fee. Treat the confirmation as incomplete if the policy requires that consequence to be disclosed first. Finishing a sentence internally is not evidence the caller heard it.
| Conversation condition | Expected action |
|---|---|
| Clear agreement to current proposal | Continue to final backend checks |
| Agreement followed by a correction | Invalidate and clarify |
| Silence after the question | Do not treat silence as approval |
| Proposal changed by another employee | Require a fresh proposal |
Evaluate the business record after each test. The acceptance criterion is that only the specifically authorised action occurs, not merely that a confirmation sentence appears in the transcript.
Add friction according to consequence
Reading every internal identifier aloud can overwhelm callers. Use recognisable details, such as service type and date, while retaining the precise reference internally. High-impact actions may need staff approval or a different verification channel according to business policy.
Extra confirmation increases call time and can annoy callers performing routine changes. Keep it focused on the consequences that matter. Do not claim confirmation makes an irreversible action reversible.
This design is proposed. The HVAC request example documents confirmation before saving a request, not unrestricted cancellation powers. Pair this guide with tool permission checks.
Destructive action FAQ
Does every “yes” authorise execution?
No. It must refer unambiguously to the current proposal after required details have been disclosed.
Can confirmation survive a changed appointment date?
It should normally be invalidated when a consequential detail changes.
What if the caller hangs up after confirming?
Follow the explicitly defined execution policy and operation state. Do not infer either cancellation or completion solely from disconnection.