> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qall.io/llms.txt
> Use this file to discover all available pages before exploring further.

# call.transferred

> Sent when a caller is handed to a person.

Fires when a [transfer](/tools/call-transfers) is attempted, with whether it
worked.

```json theme={null}
{
  "id": "73af09d6c1e24b8fa5302e9b7c6d1480",
  "type": "call.transferred",
  "created_at": "2026-10-02T09:13:55.771000+00:00",
  "message": {
    "type": "call-transferred",
    "call": { "id": "call_elster_hotel-en" },
    "transfer": {
      "mode": "warm",
      "destination": "+4930222222",
      "status": "success",
      "reason": null
    }
  }
}
```

## Fields

| | |
| - | - |
| `call.id` | The call being transferred |
| `transfer.mode` | `cold`, `warm` or `rich` |
| `transfer.destination` | Where it went |
| `transfer.status` | Whether it succeeded |
| `transfer.reason` | Why it failed, when it did — busy, no answer, declined, or voicemail |

## Using it

Two things worth doing with this.

**Route the follow-up.** A call that ended in a transfer was handled by a person,
so it probably shouldn't go into the same queue as one your assistant resolved.

**Watch the failures.** A rising number of `reason` values saying nobody answered
usually means the destination is understaffed at a particular hour, which is
something you can chart and fix.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.