call.transfer.failed webhook event fires once after Apten starts dialing the human agent and the transfer does not connect. Subscribe to this event if you want to take different actions depending on why the handoff failed.
This is the terminal failure counterpart to
call.transfer.connected. After a warm transfer starts, Apten emits exactly one of those two events. Cold transfers do not emit call.transfer.connected; a cold transfer that fails after the agent is dialed still emits this event.If the lead never answered a dedicated outbound transfer call, Apten did not dial an agent. That case stays on call.attempted with isTransfer: true. It does not emit call.transfer.failed.Failure codes
Treat unknown codes as a generic transfer failure so later codes do not break your handler.
Payload
Properties
The same outcome is on
GET /calls/{callId} as transferStatus and transferFailureCode. Use that to reconcile or backfill. Do not infer failure from a missing call.transfer.connected.
