A caller hangs up while the AI is saving an appointment. Cancelling the local task immediately may leave the business unsure whether the remote system accepted the booking.
For engineers handling disconnections, separate conversation lifetime from business-operation lifetime. A telephone session ending does not automatically undo an action already submitted elsewhere.
What changes when the caller disconnects?
The application can stop speech and call-specific listening, but it must evaluate pending actions according to their current state and prior authorisation. Some work can be cancelled safely; other work needs completion or reconciliation.
Do not infer permission to perform a new action merely because the caller was present earlier. Preserve the confirmed request and the point at which it was authorised.
Classify work before deciding cancellation
Use this proposed state table for a booking workflow. The actual remote API and business policy determine the implementation.
| State at disconnect | Expected handling to define |
|---|---|
| Caller has not confirmed | Do not create the proposed appointment |
| Read-only lookup pending | Cancel when safe and useful |
| Confirmed write not submitted | Apply explicit policy for proceeding |
| Write submitted, response unknown | Reconcile remote state before retrying |
| Appointment verified | Preserve record and approved follow-up |
The difficult case is an uncertain write. A timeout or cancelled local request cannot establish that the remote server rolled the operation back.
Keep durable operation evidence
Record the intended action, authorised inputs, operation identifier and known delivery state in the appropriate controlled storage. The application should be able to inspect the remote result without relying on the ended voice session's memory.
Avoid replaying the whole conversation after restart. Recover the specific operation with duplicate protection and a defined resolution owner. If the provider cannot support an unambiguous lookup, the workflow may need manual review instead of an automatic retry.
The cross-system tracing guide helps connect the session to the remote record evidence.
Make post-call communication match the result
Send any approved confirmation only after the relevant outcome is verified. A disconnected caller should not receive a success message based solely on the AI's intention to save.
My voice intake demonstration illustrates a bounded administrative flow. It does not prove a remote booking integration's cancellation semantics; inspect the actual provider and test the uncertain states.
Keep these scenarios in the fictional test set, including disconnects before confirmation, during submission and after remote completion. Record expected mutations and forbidden effects for each case.
Does hanging up cancel a remote write?
Not necessarily. Inspect the operation state and destination evidence rather than assume rollback.
Should all pending work continue after disconnect?
No. Decide from prior authorisation, action type, submission state and the business's approved policy.
What should we test first?
Choose a controlled uncertain-write scenario and define its expected remote state in the voice AI project brief.