The caller hangs up immediately after accepting a time. The booking request is still running. Ending the phone session should not automatically erase the operation or imply that it succeeded.
The call lifecycle and the business-operation lifecycle need separate states.
Record what was authorised before the disconnect
Define the confirmation step required by the business. If the caller disconnected before agreeing to the final details, do not infer consent merely because enough fields were collected.
For a fictional repair booking, preserve the requested service, latest date and location, confirmation evidence, operation reference, and final known state.
| Disconnect point | Recovery question |
|---|---|
| Before agreement | Should this remain a draft request? |
| Before submission | Was the action actually authorised? |
| During submission | Could a remote write have succeeded? |
| After acceptance | Is confirmation delivery still pending? |
These decisions should be explicit rather than a general rule that every hangup cancels or completes the workflow.
Keep recoverable work outside in-memory call state
A durable operation record lets a worker or staff member reconcile the result after the voice session disappears. It should contain only the information required by the approved workflow.
The operation needs a trustworthy customer and tenant boundary. Background reconciliation should not run a broadly privileged lookup based on arbitrary conversational identifiers.
If the remote write succeeded, preserve the record reference. If the outcome is unknown, use the provider's supported reconciliation mechanisms before issuing another booking.
Decide how to contact the caller afterward
Use the business's approved channel and contact preferences. A confirmation message should reflect a verified booking. A pending message should explain that follow-up is still required.
Do not automatically call back repeatedly just because the session ended. The caller may have intentionally stopped, lost connectivity, or decided not to proceed. Contact rules belong in the operating policy.
The callback-completion guide covers ownership after intake. The timeout article covers uncertainty during the external write.
Test disconnects at controlled points
Use fictional calls and pause the booking operation before submission, after remote acceptance, and before the caller hears the result. Restart the worker in one case.
Verify appointment count, final operation state, confirmation delivery, and what staff see. An ended call should not make unresolved work disappear from the dashboard.
For a small pilot, a staff review queue may be easier to operate than fully automatic post-disconnect recovery. Its owner and response expectations still need to be clear.
Early-hangup questions
Does hangup mean the caller cancelled the appointment?
Not by itself. Use the agreed confirmation and cancellation policy.
Can an operation finish after the call ends?
Yes, if the architecture permits it and the action was authorised.
What should we test first?
Test the moment after remote acceptance but before spoken confirmation in a reliability review.