Teams
A team is a group of AI agents that work together on a shared mission. Think of it like a department in a company -- each agent has a specialized role, and the team lead coordinates everyone.
Why Teams?
A single agent can only do so much. Real business processes need multiple perspectives, parallel execution, and coordinated handoffs. Teams solve this by:
- Specialization -- Combine agents with complementary expertise instead of overloading one agent
- Scale -- Execute tasks in parallel when speed matters
- Oversight -- Route critical decisions through a lead agent or to a human
- Shared context -- All agents on a team see the same workspace briefing, customer context, and shared memories
How Teams Are Structured
Every team has a lead agent and one or more specialist agents. The lead receives incoming work, delegates to specialists, and synthesizes results.
┌─────────┐
│ Lead │ Coordinator / manager
└────┬────┘
|
┌────────┼────────┐
v v v
┌─────┐ ┌─────┐ ┌─────┐
│ A │ │ B │ │ C │ Specialist agents
└─────┘ └─────┘ └─────┘
┌──────────────────────────────┐
│ Shared Context │
│ (Briefing, Artifacts, etc.) │
└──────────────────────────────┘
Team Hierarchy
Teams can be nested. The most common pattern is a C-Suite team at the top that cascades context down to child teams:
C-Suite (parent)
├── Sales Team
├── Support Team
├── Marketing Team
└── Engineering Team
The parent team (C-Suite) must be started first. Its lead reads the full Workspace Briefing, generates summaries for each child team, and a human approves before the cascade continues. This ensures every team gets contextually relevant direction -- not a raw dump.
Orchestration Modes
How agents collaborate within a team depends on the orchestration mode:
| Mode | How It Works | Best For |
|---|---|---|
| Sequential | Agents execute tasks one after another in a defined order | Linear processes, pipeline workflows |
| Parallel | Agents work simultaneously on different sub-tasks | Speed-critical work, independent sub-tasks |
| Hybrid | Combines sequential and parallel execution as needed | Complex coordination, enterprise processes |
25+ Pre-Built Team Templates
MeetLoyd ships with ready-made templates across industries:
| Category | Templates |
|---|---|
| Sales | Sales Team, Customer Success |
| Support | Support Team, Support Tiers (multi-tier escalation) |
| Executive | C-Suite Leadership |
| Engineering | DevOps, Product |
| Business | Marketing, Finance, Legal, Strategy, HR |
| Industry | Healthcare, Insurance, Accounting, Construction, Real Estate, Logistics, Manufacturing |
| Investment | VC/PE, Fundraising |
| Operations | Enterprise Deployment, Legal Services |
Browse the full list in the Team Catalog.
The Team Starting Wizard
Teams are never just flipped to "running." When you start a team for the first time, a guided wizard orchestrates a multi-phase onboarding:
| Phase | What Happens |
|---|---|
| Self-Discovery | Agents analyze their own configuration, tools, and role |
| Tool Discovery | Agents verify connections and permissions |
| Skill Discovery | Relevant skills are auto-assigned based on connected integrations |
| Charter Generation | Each agent gets a charter defining its mission, boundaries, and escalation rules |
| Human Review | You review and approve the generated charters |
| Handshake | Agents introduce themselves to each other and establish communication protocols |
| Briefing Cascade | The workspace briefing propagates from the lead down to specialists |
After all phases complete, the team transitions to running status.
Never set a team to running directly via the database or API. Always use the Team Starting Wizard -- it ensures agents have proper context, charters, and introductions.
Creating a Team
From a Template (Recommended)
- Go to Teams in the dashboard
- Click + Create Team
- Choose a template from the catalog
- Fill in the onboarding form (customer name, goals, integrations)
- Click Create
The template pre-configures agents, roles, tools, and interaction rules. You can customize anything after creation.
From Scratch
- Go to Teams > + Create Team > Blank Team
- Name the team and assign it to a workspace
- Add agents one by one, assigning roles and hierarchy levels
- Configure orchestration mode and interaction rules
- Click Create
Via Loyd
Tell Loyd what you need:
"Create a DevOps team for incident response in the Platform Ops workspace"
Loyd will ask clarifying questions, select the right template, and deploy the team.
Shared Onboarding
When creating a team from a template, you fill in a shared onboarding form. These answers become shared context that every agent on the team can see:
| Field Type | Example |
|---|---|
| Customer name | "Acme Corporation" |
| Industry | "Technology" |
| Current stack | "Okta, Slack, Jira" |
| Project goals | "SSO deployment, Security compliance" |
| Timeline | "Q1 2026" |
This context is injected into each agent's prompt so they all start with the same understanding.
Interaction Rules
Rules define automatic behaviors within the team:
| Rule Type | When It Triggers | What Happens |
|---|---|---|
| Escalation | Complexity score exceeds threshold, or negative sentiment detected | Routes to senior agent or human |
| Handoff | Specific intent detected (e.g., billing dispute) | Transfers conversation to specialist |
| Approval | High-value action (e.g., refund > $1,000) | Pauses for manager approval |
Managing Teams
You can adjust team settings at any time through the dashboard, through Loyd ("make my sales team more autonomous"), or via the API.
Changing settings while a team is running applies to new tasks only. Existing tasks continue with their original settings.