Reecall

Transfer tool

Configure transfer destinations and conditions with transfer_conversation. The Channel determines whether Reecall executes the transfer over SIP or delegates it to your WebRTC client.

What is the transfer tool?

The transfer_conversation System Tool transfers ongoing calls to external destinations. The Assistant selects a destination based on the conversation and your configured conditions.

The transfer_conversation tool is configured with a list of possible transfer destinations, each with:

  • destination: the target phone number or SIP address
  • condition: when the Assistant should transfer to this destination
  • preTransferSentence (optional): what the Assistant says before initiating the transfer

Setting up the transfer tool

The API paths below are relative to https://newprd.reecall.io/data_next.

Step 1: fetch the transfer tool definition

Retrieve the transfer_conversation Tool Definition ID:

Code
GET /ai/toolDefinitions?where={"name":"transfer_conversation"}

Use the id from the response as definitionId when creating the Tool:

JSONCode
[ { "id": "9de0f15e-6873-4428-a08f-b29e8c906b05", "name": "transfer_conversation", "description": "Transfer the conversation ...", "configuration": {}, "createdAt": "2025-12-15T08:58:49.942Z", "updatedAt": "2025-12-15T08:58:49.942Z" } ]

Step 2: create the transfer tool

Create a Tool instance with your transfer configuration:

Code
POST /ai/tools Content-Type: application/json Authorization: Bearer <your-api-token> { "assistantId": "your-assistant-id", "definitionId": "9de0f15e-6873-4428-a08f-b29e8c906b05", "configuration": { "transfers": [ { "destination": "+33612345678", "condition": "The caller wants to speak with sales", "preTransferSentence": "I'll transfer you to our sales team now." }, { "destination": "+33698765432", "condition": "The caller needs technical support", "preTransferSentence": "Let me connect you with our technical team." } ] } }

Configuration reference

The transfers array contains the available transfer destinations:

FieldRequiredDescription
destinationYesPhone number in E.164 format (e.g., +33612345678) or SIP address
conditionYesNatural language description of when to transfer to this destination
preTransferSentenceNoMessage the Assistant speaks before initiating the transfer

Example configurations

Single destination:

JSONCode
{ "transfers": [ { "destination": "+33612345678", "condition": "The caller explicitly asks to speak with a human agent" } ] }

Multiple destinations with routing logic:

JSONCode
{ "transfers": [ { "destination": "+33611111111", "condition": "The caller has a billing question or payment issue", "preTransferSentence": "I'll connect you with our billing department." }, { "destination": "+33622222222", "condition": "The caller needs help with their order or delivery", "preTransferSentence": "Transferring you to our orders team." }, { "destination": "+33633333333", "condition": "The caller wants to cancel their subscription", "preTransferSentence": "I'll transfer you to our retention team." } ] }

Behaviour

Condition evaluation

The Assistant evaluates transfer conditions based on the conversation context. The condition field is a natural language description that the LLM interprets during the conversation.

When multiple conditions could apply, the Assistant selects the most appropriate destination based on the conversation flow and caller intent.

Pre-transfer message

If preTransferSentence is provided, the Assistant speaks it before initiating the transfer. Use it to tell the caller where they are being transferred.

SIP vs WebRTC transfer comparison

AspectSIP TransferWebRTC Transfer
Transfer methodCold (SIP REFER)Delegated to client
ExecutionDirect via LiveKit APIVia RPC to your application
Hold audioNo dedicated hold musicYour application can provide hold audio
Context handoffNot supportedOptional conversation summary sent
Transfer outcomeDetermined by SIP responseDetermined by your application
Failure handlingBased on SIP status codesBased on your reason field

What's next

Last modified on