> ## Documentation Index
> Fetch the complete documentation index at: https://chatbase.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Create support teams in the Helpdesk

> Group your agents into teams so tickets can be routed and assigned to the right people.

A Chatbase Helpdesk team is a named group of teammates inside one AI agent. A ticket first goes to a team, and the team's assignment strategy then picks the teammate who handles it. Teams let support leads split work by function, product, or language, so the right group always handles the right tickets.

Every AI agent has exactly one **default team**. When you first enable the Helpdesk, a team called **General** is created as the default and every workspace member is added to it. New tickets that no [trigger](https://chatbase.co/docs/user-guides/chatbot/help-desk/triggers.md) sends to a team go to the default team.

Teams and their assignment settings live on a single page: **Settings → Helpdesk → Teams & assignment**.

## How tickets reach a team

[Triggers](https://chatbase.co/docs/user-guides/chatbot/help-desk/triggers.md) decide which team a ticket goes to. Use a trigger with a **Ticket is Created** condition and an **Assign team** action to send, for example, every ticket received on [billing@example.com](mailto:billing@example.com) to a "Billing Support" team.

When you enable the Helpdesk, Chatbase also adds a trigger named **Route to default team**, described as "When a new ticket still has no team, assign it to your default team." Its conditions are **Ticket is Created** and **Team is no team**, it assigns whichever team is the default when it runs, and it sits last in your trigger list. That's why the default team's card reads "New and unrouted tickets are assigned to this team."

A new ticket ends up with no team only when:

* The **Route to default team** trigger is paused or deleted. It's an ordinary trigger, so you can change it like any other.
* The ticket comes from a [takeover](https://chatbase.co/docs/user-guides/chatbot/help-desk/takeover.md). It skips the create triggers and is assigned to the teammate who took over.
* An API call sets the team or assignee explicitly.

> [!NOTE]
>
> Team Routing rules no longer run. Existing rules were converted into triggers named **Team routing rule N**, which you'll find in your trigger list. See [Triggers](https://chatbase.co/docs/user-guides/chatbot/help-desk/triggers.md).

## Team properties

| Property | Description |
| :- | :- |
| **Name** | A display name for the team, 1 to 100 characters (for example, "Billing Support"). |
| **Assignment strategy** | How tickets are distributed to agents within the team: **Manual**, **Balanced**, or **Round Robin**. See [Ticket Assignment](https://chatbase.co/docs/user-guides/chatbot/help-desk/assignment-algorithm.md) for how each method works. |
| **Max tickets per agent** | An optional cap on open tickets per agent, up to 1,000,000. Only applies when the strategy is **Balanced** or **Round Robin**. Leave empty for no limit. |
| **Statuses that count toward agent workload** | Whether **On customer** and **On hold** tickets count toward an agent's workload. Both count by default. Shown for **Balanced** teams, and for **Round Robin** teams that have a max tickets per agent. See [Agent workload](https://chatbase.co/docs/user-guides/chatbot/help-desk/assignment-algorithm.md#agent-workload). |
| **Assign to next available shift** | A toggle that routes tickets to the next agent coming on shift when no one is currently available. Only shown for **Balanced** and **Round Robin**. |
| **Unassign on reply** | When a customer replies to a ticket whose assigned agent is currently unavailable, that agent is unassigned and the team's auto-assignment runs again. Off by default. |
| **Default team** | Exactly one team per AI agent is the default. It receives every new ticket that no trigger sent to another team. |

> [!NOTE]
>
> The assignment strategy controls how tickets are shared **between agents inside a team**. Triggers decide **which team** a ticket goes to. The two work together: a trigger picks the team, then the team's strategy picks the agent.

***

## The Teams & assignment page

**Settings → Helpdesk → Teams & assignment** shows every team and the selected team's configuration on one screen.

* **Team chips.** Each team appears as a chip at the top of the page with its **member count**, its number of **open tickets**, and a **Default** badge on the default team.
* **Search.** Filter the chips by team name with the search box.
* **Create team.** The **Create team** button sits next to the search box. A newly created team is selected automatically.
* **Selected team.** Clicking a chip loads that team's **Team settings** and **Members** cards below the chips, with no page change. The default team is selected when you open the page, so auto-assignment settings are visible right away.
* **Deep links.** The selected team is reflected in the URL as `?team=<team-id>`, so you can bookmark or share a specific team.

***

## Creating a team

**1. Open the Teams & assignment page**

Navigate to your AI agent's **Settings → Helpdesk → Teams & assignment**.

**2. Start a new team**

Click **Create team**. A slide-over panel opens.

**3. Name the team**

Enter a name, such as "Billing Support" or "Tier 2".

**4. Add members (optional)**

Select agents from the member picker. You can search by name or email and use **Select all**. Members can also be added later.

**5. Choose an assignment strategy**

Pick **Manual**, **Balanced**, or **Round Robin**. If you choose Balanced or Round Robin, you can optionally set **Max tickets per agent** and enable **Assign to next available shift**. You can choose which statuses count toward agent workload after the team is created.

**6. Save**

Click **Create team**. The team appears as a new chip and is selected immediately so you can keep configuring it.

***

## Editing a team

Select a team's chip to load its configuration below the chips. It has two main cards.

### Team settings

Edit **the team’s name**, **assignment strategy**, **max tickets per agent**, **statuses that count toward agent workload**, **Assign to next available shift**, and **Unassign on reply** settings. A Save button appears once you make a change.

This card also shows the team's default status:

* If the team **is** the default, an info box reads "New and unrouted tickets are assigned to this team."
* If the team **is not** the default, a **Make default** button lets you promote it.

### Members

The Members card lists the team's current agents in a searchable table showing each agent's availability status, current shift, and number of open tickets. The **Open tickets** count only includes tickets on this team, so an agent who also works tickets on another team has more open tickets than this column shows.

* **Add a member** with the **Add member** control, which lists any workspace member who can access this AI agent and isn't already on the team. Any role can be a team member, Viewers and Support Associates included.
* **Remove a member** with the per-row **Remove** action. A confirmation dialog appears before the member is removed.

Removing someone from a team doesn't touch their tickets. Their open tickets stay assigned to them and stay on the team, and nothing is reassigned. To move that work, reassign the tickets yourself. Removing someone from the **workspace** is different: their tickets become unassigned.

***

## The default team

There is always exactly one default team per AI agent.

* It is created automatically (named **General**) when the Helpdesk is first enabled, with all workspace members added.
* **General** uses **Manual** assignment, so tickets it receives join the team but aren't given to an agent until someone claims them. Switch it to **Balanced** or **Round Robin** to auto-assign them.
* People who join the workspace later, by invitation, SSO, or Shopify, are added to the current default team of every AI agent that has the Helpdesk on. If their role is limited to certain AI agents, this only happens on those agents. Their status starts as **Away**.
* Any team can become the default using **Make default** in its **Team settings** card.
* The default team **cannot be deleted**.

> [!TIP]
>
> Keep your default team staffed with agents who can handle general or uncategorized tickets, since it is the fallback for anything your triggers don't send to another team.

***

## Deleting a team

Only non-default teams can be deleted. Select the team, click **Delete team** at the bottom of its **Team settings** card, then confirm in the dialog.

> [!WARNING]
>
> If the team has open tickets, those tickets are **detached from the team** (they keep their assigned agent, if any, but are no longer tied to a team). The default team can never be deleted, so reassign the default first if you need to remove that team.

***

## Limits

* **Teams:** no limit on the number of teams or on members per team.
* **Team name:** 100 characters.
* **Max tickets per agent:** up to 1,000,000.
* **Scope:** teams belong to one AI agent. If you run the Helpdesk on two AI agents, set up teams on each.

Creating, editing, and deleting teams, and adding or removing members, uses the same permission as editing Helpdesk tickets.

***

## Frequently asked questions

> [accordion] Where do tickets go if no trigger assigns a team?
>
> To the default team. The **Route to default team** trigger, added when you enable the Helpdesk, sends every new ticket that still has no team to whichever team is the default. If you pause or delete that trigger, those tickets stay with no team.

> [accordion] Why are tickets in the default team still unassigned?
>
> The default **General** team uses **Manual** assignment, so tickets join the team without going to an agent. Change its **Assignment strategy** to **Balanced** or **Round Robin** to assign them automatically. See [Ticket Assignment](https://chatbase.co/docs/user-guides/chatbot/help-desk/assignment-algorithm.md).

> [accordion] Is there a limit on how many teams I can create?
>
> No. There is no limit on teams or on members per team. Team names can be up to 100 characters.

> [accordion] Are new workspace members added to a team automatically?
>
> Yes. Anyone who joins the workspace is added to the default team of every AI agent with the Helpdesk on (only the AI agents they can access, if their role is limited). They start with the **Away** status, so they don't get auto-assigned tickets until they're set to **Available**.

> [accordion] What happens to a teammate's tickets when I remove them from a team?
>
> Nothing. Their open tickets stay assigned to them and stay on the team. If you remove them from the workspace instead, their tickets become unassigned.

> [accordion] Can one person be on several teams?
>
> Yes. A teammate can belong to any number of teams on the same AI agent. Each team's **Open tickets** column counts only that team's tickets, and **Balanced** assignment also counts only the tickets in the team it's assigning for.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.