Do `transfer_to_number` tool client_message, agent_message parameters are generated by runtime? ht

[opaque ridge]

AI-generated Answer for programminglanguage.

Short answer: yes—client_message and agent_message are provided by the LLM at runtime when it invokes transfer_to_number, not at agent creation.

Evidence from the docs:

• The tool’s function-call schema lists client_message and agent_message as required arguments of transfer_to_number. (elevenlabs.io)
• The Transfer to human page explicitly notes: “When the LLM decides to call this tool, it needs to provide: transfer_number, client_message, agent_message.” (elevenlabs.io)

At agent creation, you only enable the transfer_to_number system tool and configure transfer rules (destination number/SIP URI, transfer type, conditions, optional SIP REFER headers), and optionally a tool description to guide when the LLM should trigger a transfer—there’s no field there for client_message or agent_message. (elevenlabs.io)

Sources:
System tools | ElevenLabs Documentation
Transfer to human | ElevenLabs Documentation
Transfer to human | ElevenLabs Documentation

[dusky wharf]

Can I put what agent should say to client (when waiting for transfer) and what agent should say to person who receives call in tool description?