Transfer-rule authoring is available. A stored destination does not prove a live handoff, context transfer, or authorization to use the receiving agent. Conversation execution remains gated.
Add a transfer rule
You need an editable source agent and a destination you can identify and review.1
Open Transfer to Agent
On the source agent’s Tools > System tools panel, enable Transfer to Agent. Its configuration opens before activation. Select Add Rule in Agent transfer rules.
2
Choose the destination and condition
Choose the Agent and write a specific Condition. For example, distinguish an order-status request from a technical-support request. The editor requires at least one rule, with a nonblank condition and destination for every rule.
3
Review the handoff wording
Review Transfer message, Delay before transfer (ms), and whether the receiving agent’s first message is requested. Avoid wording that announces success before a transfer result exists.
4
Save and read back
Select Save to update the working copy. For API persistence, place the reviewed definition in a complete server draft, then inspect each destination and condition in the returned draft.
Transfer fields
Useconversation_config.agent.prompt.built_in_tools.transfer_to_agent, with params.system_tool_type: "transfer_to_agent" and params.transfers as the rule list.
For API-authored node transfers, use the node identifier from the intended workflow. A node ID and an agent ID identify different resources.
Frequently asked questions
Why can I not save an empty rule?
Why can I not save an empty rule?
The dashboard requires a condition and the appropriate destination before it activates the tool. An empty list is not a completed editor configuration.
Does the receiving agent inherit every setting?
Does the receiving agent inherit every setting?
Do not assume that it does. Review the receiving configuration separately. The voice-override preference does not establish complete prompt, tool, knowledge, or runtime-state inheritance.