Agent teams
An agent team lets one agent (the main agent) ask other agents of your workspace (its members, or specialists) for help while it answers its own customer. The main agent sends a brief, the specialist works with its own instructions, tools and Knowledge, and the answer comes back to the main agent, which writes one reply to the customer.
Use a team when one agent would need too many tools and too much knowledge, or when you already have specialists you want to reuse. Example: a Finance agent has Crypto, Fund and Stock agents on its team. For "BTC, THYAO or a gold fund?" it asks all three at once and answers in one message.
A specialist never writes to the customer and the conversation never moves to it. Specialists only answer the agent that asked. To bring a person into a conversation, see Human handoff.
How it works
-
For each member the main agent gets a tool named
ask_<name>, described with what the member is good at. -
When a question needs a specialist, the main agent calls that tool with a brief:
Part What it holds Limit goalWhat it needs, e.g. "Analyse THYAO over the last 3 months and today's price" 2,000 characters, required factsEverything the specialist's tools need: symbols, codes, amounts, dates, the customer's stated preferences 4,000 characters answerFormatHow to answer, e.g. "short: numbers + 2 sentences" 500 characters -
The specialist runs its published version: its own instructions, tools, Knowledge, skills, records and model. It also sees part of the conversation, per What it sees.
-
It returns an answer, or asks for a missing detail (see below). Several
ask_calls in one step run in parallel. -
The main agent writes the reply. In the Inbox, the reply shows Asked: with the members it asked; each call opens to the brief, the answer, tools used, time and cost.
Asking for details
When a specialist's tools need something the brief doesn't give (a fund code, an amount, a date), it asks instead of guessing. The main agent then asks the customer, or adds the detail and asks again. On the specialist's side this shows as Asked for details.
Set up a team
-
Build and publish each specialist as a normal agent. Each keeps its own channels and can serve several main agents.
-
Open the main agent's Instructions page and scroll to Team: "Other agents of this workspace this agent can ask for help while it answers. They answer this agent, never the customer."
-
Click Add member and set:
Setting What it does Default Agent The workspace agent to ask. Not the agent itself, and each agent once. The first available agent Tool name The name after ask_: lowercase letters, digits and_, starting with a letter, up to 60 characters, unique in the team.Made from the agent's name, e.g. cryptoWhat it sees Brief + last 10 messages, Brief only, or Brief + whole conversation. Brief + last 10 messages What it is good at Up to 500 characters. The main agent reads it to decide when to ask, e.g. "Crypto prices and analysis: BTC, ETH, altcoins". Empty, required to publish -
Test in the Test panel with questions that need the specialists. The reply shows Asked: ….
-
Publish the main agent.
The team is part of the draft, like tools: changes reach customers when you publish.
Tell the Copilot "a finance assistant that uses the crypto, fund and stock agents". It proposes the members with descriptions, sets them in the draft after your approval, and tests with questions that need them. See Working with the Copilot.
Publishing rules
The main agent can't be published while a member:
| Problem shown | Fix |
|---|---|
| "An agent can't be on its own team." | Remove it. |
| "This agent was deleted: remove it before publishing." | Remove the member. |
| "Agent name is not published yet: publish it before this agent." | Publish the specialist first. |
| "Describe what it is good at before publishing." | Fill in What it is good at. |
If a member is deleted later, the main agent keeps working: that member's tool is just no longer offered.
What it sees
| Option | The specialist receives |
|---|---|
| Brief only | Only the brief. |
| Brief + last 10 messages | The brief and the last 10 messages of the customer conversation. |
| Brief + whole conversation | The brief and the conversation, up to the last 200 messages. |
The shared conversation is capped at 30,000 characters, keeping the newest messages. Personal data stays as the main conversation's placeholders ([PHONE_1], [NAME_1]): a specialist never sees the real values and never reveals them, but its tools still receive them when needed.
What a specialist can and can't do
On a team call, a specialist works in delegate mode, enforced by the system:
- It gets no tools to send to a channel or a customer, start conversations, ask for a person, or add to Knowledge. Nothing goes out through its own channels.
- Its answer goes only to the agent that asked. The brief and conversation are treated as data, never as instructions to it.
- Records it saves and approval requests it creates belong to the main agent's conversation and customer. The follow-up after an approval goes to the main agent's conversation.
- It can ask its own team, also in delegate mode.
The same agent can answer its own customers on its channels and work as a specialist for other agents at the same time. The two are independent.
Limits
| Limit | Value |
|---|---|
| Members per team | 10 |
| Depth (main → member → member's member) | 3 levels |
| The same agent twice in one chain | Not allowed (A → B → A is refused) |
| Team calls per customer reply | 10, across the whole chain |
| Time per call | 60 seconds, and never past the main reply's own time limit (8 seconds are kept for the main agent to write its answer) |
| A call needs at least | 5 seconds left in the reply |
| Specialist's answer | 8 KB |
| Question back (Asked for details) | 500 characters |
The whole chain also shares one cost budget per customer reply. When a call isn't allowed, the main agent receives a short reason such as "Not asked: teams can be at most 3 levels deep" or "Not asked: this reply's team budget is used up", and answers without it.
Team calls for live conversations also count toward the workspace's daily reply limit. The costs of team calls add to the main conversation's cost.
Team calls history
Every call is stored on the specialist's side.
- Inbox → Team calls on the specialist lists every call another agent made to it, newest first. Filter by Caller (All callers or one agent). Click Show older for more.
- Each call opens with a title like Finance asked Crypto: the Brief (goal, Facts, Answer format), the Conversation it saw, the tool calls, the outcome (Answer, Asked for details or Error), time and cost, and a link: Open the caller's conversation.
- Calls from test conversations carry a Test tag.
On the main agent, the Asked: line under a reply links to each call.
The specialist's Analytics page has a separate Team section with its calls, average time, cost, error and "asked for details" rates, an AI check of answer quality, and how the callers' conversations ended. Team calls are never counted in its customer numbers. See Analytics.