Human handoff
A human handoff is the transition of an active conversation from an automated agent to a person when the caller's request needs human attention, judgment, or authority.
The handoff can be cold or warm. In a cold transfer, the automated agent sends the caller directly to a destination without first speaking to the recipient. In a warm transfer, the caller waits while the agent contacts the recipient privately, provides a brief, and connects the parties after acceptance. A workflow may also arrange a later human response when nobody appropriate is available, although that is not a live transfer.
A good handoff starts before the transfer itself. The system needs clear eligibility rules, a valid destination, an availability policy, and a fallback for no answer or voicemail. The agent should tell the caller why the handoff is happening and what to expect without promising that a particular person will answer unless that outcome has been confirmed.
Context determines whether the handoff feels continuous. The recipient may need the caller's goal, information already collected, actions already attempted, and the reason human help is required. Passing too little context forces the caller to repeat the conversation. Passing unnecessary context creates avoidable privacy and attention costs. The handoff brief should be limited to what the recipient needs for the next decision.
Human handoff is related to escalation, but the terms are not identical. Escalation is the decision to move a case to a more capable or authoritative path. Human handoff is one way to execute that decision. A call can escalate to a specialized automated flow, and a caller can request a human even when no failure or high-risk issue has occurred.
For AI phone calls, teams should test accepted transfers, declined transfers, unanswered lines, voicemail pickup, and destinations that are closed or misconfigured. They should also review whether the agent escalated early enough and whether the recipient received useful context. The objective is a reliable continuation of service, not simply a successful telephony connection.
In practice on ThunderPhone
ThunderPhone supports cold and attended warm transfers. During a warm transfer, the caller waits on hold while the agent privately briefs the recipient. If the recipient accepts, the call connects; if the recipient declines, does not answer, or reaches voicemail, the agent returns to the caller with the outcome. Warm transfer requires an eligible production number that can place an outbound SIP leg.