---
schema_version: "1"
id: bf6614f546c50b18ab1db294cb9836cfef0082c96d9ff0f31a75b44bceaebf34
title: Orchestrate Other Agents (Beta)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_agentforce_multi_orchestrate.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_agentforce_multi_orchestrate.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 539940361aeaa91bc18da07004c530e849f840ee534a8b038658496edac8c43c
description: Extend your agent’s capabilities with Multi-Agent Orchestration for Agentforce (Beta). Connect your Agentforce agent with other specialized Agentforce agents in your Salesforce org. Together they can collaborate seamlessly on complex tasks. By providing a single, unified point of contact, connected subagents help your users accomplish more without juggling multiple disconnected sessions.
products:
  - Cross Cloud
release: "262"
---
# Orchestrate Other Agents (Beta)

Extend your agent’s capabilities with Multi-Agent Orchestration for Agentforce (Beta). Connect your Agentforce agent with other specialized Agentforce agents in your Salesforce org. Together they can collaborate seamlessly on complex tasks. By providing a single, unified point of contact, connected subagents help your users accomplish more without juggling multiple disconnected sessions.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-262-0-0-production-enus/e945111b-3e0a-4011-accc-d5949363bfcc/images/icon_note.png)

Note Multi-Agent Orchestration for Agentforce is a beta service that is subject to the Beta Services Terms at [Agreements - Salesforce.com](https://www.salesforce.com/company/legal/) or a written Unified Pilot Agreement if executed by Customer. Use of this beta service is at the Customer's sole discretion.

**Where:** This change applies to Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions with Foundations or Agentforce 1 editions.

**When:** Multi-Agent Orchestration for Agentforce (Beta) features start rolling out the week of May 4, 2026. Certain features may come in a subsequent roll out. For example: support for custom variables and a unified trace view in NGA that shows a connected subagent's trace in detail.

**How:**

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-262-0-0-production-enus/e945111b-3e0a-4011-accc-d5949363bfcc/images/icon_note.png)

Note For customers who didn't participate in the Multi-Agent Orchestration for Agentforce (Pilot) program, before using an agent with Multi-Agent Orchestration for Agentforce (Beta):

- If the agent was built using the new Agent Builder, create and activate a new version of it.
- If the agent was built using the legacy Agentforce Builder, upgrade it to the new Agent Builder. See [Upgrade an Agent from the Legacy Builder to the New Builder](https://help.salesforce.com/s/articleView?id=ai.agent_setup_create_upgrade.htm&type=5&language=en_US).

In Agent Builder, open an agent in a draft state. This agent serves as your orchestrator agent. From the Explorer panel, click **+** and select **Connect Agent as Subagent (Beta)**. Select one or more available agents that you want your agent to connect to, then select **Add to Agent** to add your selections to the Explorer.

![Connected subagents in Agentforce Builder Explorer.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-262-0-0-production-enus/e945111b-3e0a-4011-accc-d5949363bfcc/salesforce_release_notes/images/rn_agentforce_orchestrate_explorer.png)

For each connected subagent, customize its description to govern its behavior within the context of your orchestrator agent.

![Agent card for a connected subagent in Agentforce Builder with the description field highlighted.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-262-0-0-production-enus/e945111b-3e0a-4011-accc-d5949363bfcc/salesforce_release_notes/images/rn_agentforce_orchestrate_agent_card.png)

If your orchestrator agent uses Agent Router, specify any logic or instructions for routing conversations to the connected subagent. In Canvas view, manually add each connected subagent under **Actions Available for Reasoning**. Then use the @ symbol to reference it in the Instructions.

![Agent Router in the Canvas view: the Instructions field references a connected subagent, and the same subagent appears under Actions Available For Reasoning.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-262-0-0-production-enus/e945111b-3e0a-4011-accc-d5949363bfcc/salesforce_release_notes/images/rn_agentforce_orchestrate_agent_router.png)

#### See Also

- [_Salesforce Help_: Multi-Agent Orchestration (Beta)](https://help.salesforce.com/s/articleView?id=ai.agent_multi_orch.htm&language=en_US)