Org Chart Builder

The Org Chart Builder provides a visual interface for designing agent hierarchies and team structures.

What It Does

Agent hierarchies define how your team is organized:

• Parent-child relationships between agents
• Escalation paths for routing complex issues upward
• Team memberships for grouping agents by function
• Reporting structures for context cascade and accountability

A well-designed hierarchy ensures agents know who to escalate to, who their peers are, and how context flows through the team.

Keep It Shallow

3--4 hierarchy levels maximum. Deeper hierarchies create unnecessary escalation latency and context loss.

Using the Org Chart

Viewing the Hierarchy

1. Open Studio from the top bar
2. Select the Org Chart tab
3. View the visual tree of agents with their roles and relationships

Adding Agents

1. Click on an agent node in the tree
2. Select Add Child Agent
3. Choose from existing agents or create a new one
4. The new agent appears as a subordinate in the hierarchy

Setting Parent Relationships

Select an agent and use the Set Parent action to move it under a different supervisor. Removing the parent relationship makes an agent top-level.

Example Hierarchy

A typical team structure might look like this:

Level	Agent	Role
1	CEO Agent	Top-level decision maker
2	Department Head A	Manages a functional area
3	Team Lead 1	Manages a small team
4	Agent 1.1, Agent 1.2	Individual contributors

Team Overlap

Agents can belong to multiple teams independently of the hierarchy. An agent might report to one supervisor in the org chart but collaborate with agents from other teams on specific projects.

Best Practices

1. Keep hierarchies shallow -- 3--4 levels maximum
2. Clear escalation paths -- each agent should know its parent
3. Document relationships -- add notes explaining why agents are connected
4. Use meaningful roles -- "CRM Agent" is better than "Agent 3"

---

Next: Learn about Prompt Engineering for configuring agent behavior.