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

# Assignment

> Configure teams, skills, capacity, and routing strategies for Woes issues.

# Assignment

Assignment settings help route issues to the right teammate or team without
turning every workflow into a manual triage step.

## What Assignment Controls

| Area             | Use it for                                                                     |
| ---------------- | ------------------------------------------------------------------------------ |
| Assignment rules | Enable or disable automatic issue routing.                                     |
| User status      | Skip away or inactive teammates when routing is configured to respect status.  |
| Capacity         | Avoid assigning beyond each member's open issue load.                          |
| Skills           | Match issues to people by product area, language, or another custom dimension. |
| Teams            | Group members and define ordered routing strategies.                           |
| Test routing     | Preview who an issue would route to before relying on the rule.                |

Capacity counts issues in **New** and **On You** status. This keeps routing
focused on current support load rather than historical closed work.

## Routing Strategies

Teams can use one or more ordered strategies. Woes tries the first strategy, then
falls through when it cannot find an eligible member.

| Strategy         | Behavior                                                 |
| ---------------- | -------------------------------------------------------- |
| Skills-based     | Routes to members who match required skill dimensions.   |
| Round robin      | Rotates work across eligible team members.               |
| Recurring daily  | Uses daily time windows for member assignment.           |
| Recurring weekly | Uses day-of-week and time windows for member assignment. |

## AI Channel Routing

Assignment controls issue and team routing. AI channel routing is a separate
control that decides which support agent answers inbound live chat, email, and
Discord conversations before or alongside human triage.

Use channel settings for the simple per-channel selector. Use the broader
assignment/routing panel when you need the configured channel-agent list:

| Channel   | Agent routing behavior                                                                         |
| --------- | ---------------------------------------------------------------------------------------------- |
| Live chat | Selects one agent for the installed widget key or channel fallback.                            |
| Email     | Can route across multiple selected agents, with a stable agent selected for each conversation. |
| Discord   | Selects one agent for Discord intake.                                                          |

Use Automations when a workflow should hand a conversation to the AI agent,
hand it back to a human operator, or route it to a team.

## Preview Routing

Use **Test routing** after saving assignment changes. Pick a team, priority, and
optional required skills, then run a preview against the current open-issue
workload.

The preview shows:

* Assigned member or queued state.
* Strategy used.
* Reason.
* Eligible member count.
* Current load versus capacity for team members.

<Tip>
  Keep skill dimensions broad enough to route work. Very narrow skills can make
  otherwise healthy teams look unavailable.
</Tip>