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 for how each method works. |
| Max tickets per agent | An optional cap on open tickets per agent. Only applies when the strategy is Balanced or Round Robin. Leave empty for no limit. |
| 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. |
| Default team | Exactly one team per chatbot is the default. It receives every ticket that no routing rule matched. |
The assignment strategy controls how tickets are shared between agents inside a team. Routing decides which team a ticket goes to. The two settings work together: routing picks the team, then the team’s strategy picks the agent.
Creating a team
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.
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.
Editing a team
Click any team in the Teams table to open its detail page. It has two main cards.Team settings
Edit the team’s name, assignment strategy, max tickets per agent, and the next available shift toggle. 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 explains that it receives all unmatched tickets.
- If the team is not the default, a Make default button lets you promote it. You can also use Set as default from the team’s row in the Teams table.
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.- Add a member with the Add member control, which lists any account agent not already on the team.
- Remove a member with the per-row Remove action. A confirmation dialog appears before the member is removed.
The default team
There is always exactly one default team per chatbot.- It is created automatically (named General) when the Helpdesk is first enabled, with all account members added.
- Any team can become the default using Make default on its detail page or Set as default from the Teams table.
- The default team cannot be deleted.