When an intake call drops, the recovery workflow should already know what to do.

The post-call workflow first classifies the original inbound call and checks whether recovery is appropriate. It does not call test or demo records, explicit do-not-call contacts, emergency calls, completed transfers, booked appointments, already scheduled callbacks, calls without a reliable caller number, or a number that resolves to the firm itself.

A durable one-call claim prevents duplicate workers from placing multiple recovery calls for the same original interaction. A failed safety or persistence check suppresses the callback instead of dialing optimistically.

The return call begins with a firm-identified opening that says the earlier call ended before completion. It then waits for the caller to choose: continue a fast intake, receive the configured secure form, or request help from firm staff. It is treated as a return call, not cold outreach.

If the original call ended in a configured non-English language, the workflow can reuse that language when it remains active on the line. If the localized opening cannot be loaded safely, the call is not placed.

Recovery calls can reach voicemail, a switchboard, or an automated phone menu. The recovery lane has answer-detection and runtime guardrails intended to stop an agent from delivering intake into a machine, navigating an IVR, or remaining on a no-progress call indefinitely.

These controls reduce avoidable failure; they do not guarantee that every carrier or answering-machine verdict is correct. The firm should review recovery outcomes during a pilot.

The outbound recovery session preserves the original call identifier, recovery reason, language choice, and placed or failed status. The return call can continue intake or create the configured form or staff-follow-up outcome without pretending the interrupted first call was complete.

If text recovery is enabled, separate gates check prior form or SMS delivery, caller texting permission, pause state, consent policy, and whether another follow-up already resolved the need. Voice and SMS recovery should never create duplicate pressure on the caller.

Simulate an early hangup with a reliable caller number, an explicit do-not-call request, an emergency, a completed transfer, a booked appointment, a scheduled callback, an unavailable translation, voicemail, an IVR, and two workers processing the same event. Confirm which calls are placed, suppressed, or stopped.

Review the opening, caller choice, final disposition, duplicate protection, language behavior, form or staff handoff, and the record staff receives before enabling the workflow broadly.