Create and orchestrate teams

The complete workflow: from creating a team, dragging agent nodes onto the canvas, drawing connections with interaction types (auto/handoff/delegate), designating the entry node, to configuring guardr

This page explains how to build an Agent Team from scratch: create a team, add agents on the canvas, configure connections and interaction types between them, designate the entry node, and start chatting with the entire team.

Prepare the AI assistants you want to add to the team first. Each node in a team is an existing AI assistant, so create your specialized assistants (e.g., routing, order, returns agents) under "AI Assistants" first, then come back here to compose them into a team.

1. Create a team

1. Go to the team list

From the left menu, navigate to AI Features > Teams. The list shows all teams in your organization, including team name, number of agents, and status. Use the search bar in the upper right to find a team.

2. Create a team

Click Create Team in the upper right corner, fill in the Team name (required) and Description, then create.

After successful creation, the system automatically creates an entry agent and a corresponding Web Chat channel for this team, so you can chat with the entire team right away.

2. Orchestrate the team on the canvas

Click into a team to enter the default Canvas Orchestration view. The screen is divided into three areas: the Agent List on the left, the Canvas in the center, and the Settings Panel on the right (appears when you select a node or connection).

Canvas orchestration is best done on a desktop browser. On small screens like mobile devices, the canvas area will show a prompt asking you to switch to desktop for orchestration.

1. Add agent nodes

In the Agent List on the left, find the agent you want to add and drag it onto the canvas, or click it to add. Agents already in the team are labeled "Already in team" — clicking them will navigate to the corresponding node on the canvas. Use the search box at the top to filter when you have many agents.

Each node displays the agent name, the model it uses, and whether it is in Agent or RAG mode for easy identification.

If node positions are messy, click Auto Layout on the canvas to have the system rearrange them. Node positions are saved automatically.

2. Configure nodes

Click a node to open the Node Settings panel on the right. You can adjust:

Setting	Description
Entry node	When enabled, the team starts processing conversations from this node. A team can have only one entry node.
Per-call token limit	Limits the token count for a single response from this node (optional).
Max iteration count	Limits the number of iterations for a single processing cycle on this node (optional).
Context strategy	Controls what this agent can see: "Visible original user input" determines whether it can read the user's original message (when off, it only sees the processed output from upstream agents); "Visible output sources" lets you specify which nodes' outputs it can see.

3. Draw connections and set interaction types

Drag from one node's connection point to another node to create a directed connection (source -> target). Click the connection to open the Connection Settings panel on the right:

Setting	Description
Trigger condition description	Describe in plain language "when should this connection be used." This description is provided to the AI as a basis for routing decisions — writing it clearly helps improve routing accuracy.
Interaction type	Choose Auto, Handoff, or Delegate (see the table below for differences).
Inherit source agent's tools	When enabled, the target agent can use all tools and resources from the source agent.

Interaction types (descriptions as shown in the settings panel):

Interaction type	Description
Auto (default)	The LLM automatically determines the most suitable interaction type.
Handoff	Hand off control — the source agent goes idle and the target agent takes over the conversation.
Delegate	Delegate a task — the target agent executes and returns the result to the source.

Watch for semantic warnings at the top of the canvas. When the team graph has issues, a yellow notice appears at the top of the canvas, such as: "No entry node set," "Multiple entry nodes — keep only one," "Duplicate connections," or "Connections form a cycle." It is recommended to resolve these warnings before starting a conversation.

3. Configure basic information and guardrails

In the team page, switch to the Basic Information view to adjust team-level settings:

• Basic information: Team name, description, and whether it is enabled.

• Guardrails:

  • Max iterations (default 25) — The maximum number of times agents can go back and forth in a single conversation, preventing infinite loops.

  • Overall token limit (default 200000) — The token budget cap for the entire team processing a single user message.

  • Timeout (default 600 seconds) — The hard timeout for the entire team's processing flow.

4. Chat with the team

Once orchestration is complete and the team is "Enabled," you can chat with the entire team through the team's Web Chat channel. Users face a single entry point, and the system automatically routes questions to the appropriate agent.

When the team performs handoffs or delegates between agents, the chat interface displays transition messages such as "Handing off to," "Delegating to," or "Switching to," letting users know which agent is currently serving them.

5. Delete a team

In the danger zone at the bottom of the Basic Information view, you can Delete Team. Deleting a team also removes its entry agent, and this action cannot be undone — please confirm before proceeding.

6. Next steps

Once the team is running, you can check the Team execution traces to see which agents were involved in each execution, how many tokens each used, and how long it took — confirming the team is dividing work as expected.