> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/getting-started/pylonboarding/teams.md).

# Teams

Organize ownership, automate assignments, and track work by function or region.

***

## Overview

**Teams** in Pylon help you mirror your organizational structure so you can manage support and success workflows more effectively. They make it easier to:

* Divide responsibilities across functions, products, or regions
* Route and assign work using triggers and automation rules
* Track performance by team, subteam, or member
* Filter dashboards and views to focus on specific groups
* Report on volume, resolution time, and SLA adherence per team<br>

Whether you’re managing enterprise customers, segmenting by region, or coordinating cross-functional work, Teams let you do it in a scalable, organized way.

***

## Setup

{% embed url="<https://demo.arcade.software/glzQILbJT0lXEfacSfG9?embed=&embed_desktop=inline&embed_mobile=tab&show_copy_link=true>" fullWidth="true" %}

***

## Use cases

* Assigning tickets by region
  * Route all EU tickets to the EMEA Support Team, with APAC getting their own queue and assignment logic.
* Organizing by function
  * Create separate teams for Support, Success, and Finance to triage different types of issues.
* Nested teams
  * Set up sub teams under broader teams (like Tier 1 and Tier 2 support under a Support team) for more detailed routing and reporting.
* Running global coverage
  * Use recurring daily/weekly schedules or round robin to distribute issues within a team automatically.

***

## Best practices

* Use Teams, even if you only have a small number of users, so you can be ready to scale
* Use Teams in [Triggers](/pylon-docs/platform/triggers.md) for automated routing (e.g. “Assign all emails to the support@ email address to the support team”)
* Create [Views](/pylon-docs/support-workflows/issues/views.md) filtered by Team to create targeted boards
* Report by Team to measure resolution times, volume, and performance
* Use [Assignment Rules](/pylon-docs/support-workflows/assignment-rules.md) to automatically route issues that have been assigned to a team to a specific individual on that team


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/getting-started/pylonboarding/teams.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.