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

# Teams and assignment

> Teams, how tickets are handed out, availability, shifts and time off, and adding a customer's new conversations to the ticket they already have.

## Teams

Every helpdesk starts with one team, **General**, as its default. Add teams under **Settings › Teams & assignment** and pick who is on each. The **Route to default team** trigger puts a new ticket without a team on the default team; your own triggers can route tickets elsewhere first. It doesn't run on a ticket you open with **Takeover**: that ticket is assigned to you and has no team until you, an **Updated** trigger, or an automation gives it one.

Each team has an **Assignment strategy**:

| Strategy | What it does |
| - | - |
| **Manual** | Nobody is assigned automatically; tickets wait in the team's pool. |
| **Round Robin** | Each new ticket goes to the next available teammate in turn. |
| **Balanced** | Each new ticket goes to the available teammate with the fewest open tickets. |

**Max tickets per agent** stops assigning to someone who already has that many, counting the statuses you choose under **Which statuses count as workload**. When someone frees up, the oldest, most urgent waiting tickets go to them. **Assign to next available shift** holds a ticket for whoever's shift starts next when nobody is on now, and **Unassign on reply** takes a ticket back from someone who has gone when the customer writes again.

## Availability, shifts and time off

Teammates are **Available**, **Away**, **Busy** or **Paused**; only available ones get new tickets. Teammates switch themselves with the switch at the bottom of the helpdesk menu if **Allow teammates to be able to change their availability status** is on (under **Settings › Members**).

Under **Settings › Scheduling**, give teammates a **shift** (days, hours and a timezone) so they are assigned only while it runs, and add **time off** to skip them on those days.

## Ticket reuse

With **Ticket reuse** on, a customer who already has an open ticket doesn't get a second one: when the agent hands a new conversation of theirs to your team, it is added to the ticket they have, becomes the one replies go to, and the agent tells them that ticket's number.

* It only applies to customers whose email address is known to be theirs: the sender of an email, or a chat visitor your website identified.
* **Window** is how recently the ticket must have had a message (1 hour to 30 days; 5 days by default).
* **Include chats** lets new chats join too, and lets emails join tickets that started in chat.
* WhatsApp is never joined: a WhatsApp conversation always gets a ticket of its own, and a later email or chat doesn't join an open WhatsApp ticket.
* **Excluded senders** lists addresses or whole domains that always get a ticket of their own.


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