Agent Teams let you group agents together so they can collaborate, delegate work, and communicate with each other. Instead of building one agent that tries to do everything, you create specialists and organise them into teams with clear communication rules.
A team is a named group of agents that can interact with each other according to rules you define. Teams model the way departments work in a real business — a customer support team might have a triage agent, a technical specialist, and an escalation manager, all working together to resolve issues.
When agents are on a team:
They can message each other in a team room they have both been added to. @-mentioning an agent there wakes it to respond. An Agent Team does not create a room or add its members to one; add them to a room separately
They can delegate tasks to teammates
They can be discovered by other agents (using the find_teammates tool) when their membership is public
Direct messages between members follow the communication rules you set (see the note under Communication rules for what they do not cover)
Teams can also include people. The User Members tab lets you add human team members alongside agents — useful when a workflow needs a person to approve or review the team’s work.
Only company owners and admins can create teams or change their members, rules and settings. An agent can do this for you only when you are an owner or admin.
Navigate to Agent Teams
Go to the Agent Teams section in your Sprigr Team portal at team.sprigr.com.
Click “New Team”
Click the New Team button to open the Create Agent Team form.
Enter a name and description
Give the team a clear name like “Customer Support”, “Operations”, or “Sales”. Add a description that explains the team’s purpose — this helps other agents (and your team members) understand what the group does. Click Create Team.
Add member agents
The new team opens on its detail page. From the Members tab, add the agents you want to include. When adding each member you choose its visibility — Public or Private (see below). You can always add or remove members later.
Set communication rules (optional)
From the Communication Rules tab, add any allow, deny, or route-through rules the team needs. Without rules, team members can communicate freely.
Explicitly permit messages between two agents. Note that adding any allow rule switches the team into allowlist mode: from then on, only explicitly allowed communications are permitted. Use this when you want tight control over who talks to whom.
Block one agent from messaging another. A deny rule works in one direction, so add a second rule to block both ways. Leave From Agent or To Agent on “Any team member” to apply the rule more widely. Use this to enforce boundaries. For example, you might deny direct communication between a sales agent and a finance agent to ensure all financial requests go through proper channels.
Direct messages between two agents must pass through a designated intermediary agent. Route-through does not reroute delegate_task requests. This is useful for:
Approval workflows — All requests to the procurement agent must go through the operations manager agent first.
Quality control — Customer-facing messages are reviewed by a supervisor agent before being sent.
Logging and compliance — An intermediary agent can log all communications between two departments.
Each team member has a visibility setting that controls whether agents outside the team can discover it through the team:
Public — Agents across your organisation can discover this member and send it messages (subject to communication rules). Use this for members that serve the whole organisation, like customer support or IT help desk.
Private — Other agents can find and delegate to this agent only if they share a team with it. If the agent is Public in any other team, or belongs to no team, it stays visible to everyone. Use this for sensitive roles like HR, finance, or executive operations.
You can toggle a member between public and private at any time from the Members tab. The team’s default visibility for new members applies to members an agent adds. When you add a member from the Members tab, pick its visibility each time.
Every team can optionally designate an orchestrator — a coordinator agent that oversees the team’s work. The orchestrator has special capabilities:
CC on direct messages — With the orchestrator CC setting enabled, the orchestrator gets a copy of direct messages between team members. It is not copied on delegate_task requests or team-room conversations.
Task routing — Other agents can delegate to the orchestrator directly, and it can pass the work on to the right member.
Coordination — The orchestrator can assign tasks, check progress, and ensure nothing falls through the cracks.
A triage agent handles initial enquiries. If the issue is technical, it delegates to a technical specialist on the same team. If the customer is unhappy, it escalates to a supervisor agent. An orchestrator tracks all open issues.
Department routing
A front-desk agent receives all incoming requests and routes them to the correct department team — maintenance, accounts, or scheduling. Each department team has its own specialists and communication rules.
Multi-step workflows
A quote request comes in. The sales agent gathers requirements, the estimating agent calculates costs, and the approvals agent checks margins. The team orchestrator ensures each step completes before the next begins.
Knowledge specialists
A research team has agents specialising in different areas — compliance, market data, and competitor analysis. When a question comes in, the orchestrator routes it to the right specialist.