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

# Tiered dispatch with agents

> Run first-line and second-tier pools with Agent Builder skills, one per tier, instead of two Auto-assign profiles.

[Tiered dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/tiered-dispatch-on-a-shared-board.md) with two Auto-assign profiles covers most tiered desks. Some desks want each tier's dispatcher to apply its own rules, such as a fixed senior pool, a classifier that decides the tier, or escalation that hands a ticket back. You can run each tier as an **Agent Builder** skill in its own **Flow**.

## How agent tiers work

This example uses one board with two statuses, **Tier 1 Queue** and **Tier 2 Queue**.

| Flow | Runs when | Pool | When no one qualifies |
| - | - | - | - |
| Tier 1 dispatcher | Status is **Tier 1 Queue** | Tier 1 techs | Move the ticket to **Tier 2 Queue** |
| Tier 2 dispatcher | Status is **Tier 2 Queue** | Tier 2 techs | Leave it unassigned with a note |

1. A new ticket lands in **Tier 1 Queue**, and the Tier 1 Flow runs its skill.
2. The skill assigns a Tier 1 tech, or moves the ticket to **Tier 2 Queue** if none qualifies.
3. The status change is written to the PSA. When the PSA sends that update back, Thread checks the ticket against your Flows again, and the Tier 2 Flow matches and assigns a Tier 2 tech.

Each tier is a separate Flow, so each runs once on a ticket. A ticket that comes back to **Tier 1 Queue** later won't trigger the Tier 1 Flow again.

## Variations

| Decision | Options |
| - | - |
| **How the tier is chosen** | By the status or board the ticket is in (above). By a classifier in one skill that decides Tier 1, Tier 2, or senior and assigns from that pool, as in the [Tier Dispatcher](https://docs.getthread.com/skill-library/scheduling-and-dispatch/tier-dispatcher.md) prompt. By a field such as priority or board item in each Flow's conditions. |
| **How the pool is defined** | Named techs per tier in each skill. One shared skill whose instructions list both tiers' pools. |
| **How escalation works** | The skill moves the ticket to the next tier's status. Or, to escalate an assigned ticket, a Flow removes the owner and sets the next tier's status, so the next tier's dispatcher or an Auto-assign profile picks it up. |
| **Mixing with profiles** | Agents for some tiers and an Auto-assign profile for another, each on its own status. See [Auto-assign plus an agent](https://docs.getthread.com/inbox/dispatch-scenarios/auto-assign-plus-an-agent.md). |

## Before you start

* Each tier has its own status (or board), and the statuses are mapped in Thread.
* You've listed each tier's techs.
* The skills are **shared** skills.

## Set up agent tiers

**1. Write one skill per tier**

Give each skill its pool and rule. In the Tier 1 skill, say exactly when to move a ticket to the Tier 2 status instead of assigning.

**2. Create one Flow per tier**

Each Flow's conditions name that tier's status. Add **Agent Builder → Run a Skill** with the update ticket and add note tools checked.

**3. Test both paths**

Send one ticket a Tier 1 tech should take and one that should move up, and check both end with the right owner.

## Rules for agent tiers

* **One run per ticket per Flow.** Re-entering a tier's status doesn't re-run that tier.
* **Remove the owner to hand a ticket back.** Auto-assign only takes unowned tickets, and an agent overwrites an owner unless told not to.
* **Statuses still matter for profiles.** If any tier uses an Auto-assign profile, the profile rules apply: no shared dispatch statuses on a board, one profile per team, and no fallback loops between profiles.


## Related topics

- [Agent dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/agent-dispatch-on-a-shared-board.md)
- [Tiered dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/tiered-dispatch-on-a-shared-board.md)
- [Dispatch recommendations](https://docs.getthread.com/inbox/dispatch-scenarios/dispatch-recommendations.md)
