> ## 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.

# Pod and client dispatch

> Send each client's tickets to the pod or technician that owns them, with team filters on one Auto-assign profile or with an Agent Builder skill.

Some service desks split technicians into pods, and each pod owns a set of clients. Others pin a key client to one or two named techs. You can run either on a shared board with an **Auto-assign** profile that filters each team to its clients, or with an **Agent Builder** skill in a **Flow**.

## How client routing works

This example uses one board, **Service Desk**, with status **New**, three pods, and clients tagged in the PSA with a Company Type for their pod.

| Team on the profile | Filter | Receives |
| - | - | - |
| Pod A | Company Type **is** Pod A | New tickets from Pod A clients |
| Pod B | Company Type **is** Pod B | New tickets from Pod B clients |
| Pod C | Company Type **is** Pod C | New tickets from Pod C clients |

1. A new ticket lands in **New** on **Service Desk**.
2. Thread checks each team's filter. The ticket's company is tagged Pod B, so it's in Pod B's pool.
3. Thread assigns it to the least-busy available Pod B tech who's under the workload limit.

Because the pods are teams on one profile, they share the board's dispatch status without a conflict. Team filters can overlap, and a team with no filter draws from all of the profile's boards, so give every pod a filter and keep the pods' filters apart.

## Options

| Option | Use it when | How |
| - | - | - |
| **A. Team filters on one profile** | Pods own many clients and you want Auto-assign's balancing | The setup below |
| **B. Pin a client to a tech** | One client always goes to one named tech | A Flow with a Company condition and the **Assign** action naming the tech. No skill needed |
| **C. Agent pod dispatch** | You want rules a filter can't hold: read the client's pod from the company record, balance inside the pod, fall back to a named backup | A Flow runs a shared skill based on the [Pod-Based Dispatch](https://docs.getthread.com/skill-library/scheduling-and-dispatch/pod-based-dispatch.md) prompt that assigns with the update ticket tool |

## Before you start

* Every client is tagged with its pod in the PSA, using one field such as Company Type.

> [!WARNING]
>
> Every client must be tagged with the pod field you filter on in the PSA. A client with no value there will not match any pod team's **is** filter, so its tickets are not routed to a pod.

* For Option A, each pod has its own Inbox Team. A team can belong to only one auto-dispatch profile.
* For Options B and C, you can create Flows. For C, the skill is a **shared** skill.

## Set up the pods

**1. Create one Auto-assign profile**

In **Dispatch scope**, select the board under **Dispatch from** and set its dispatch status to **New**.

**2. Add a team for each pod**

Under **Dispatch to**, add each pod's team.

**3. Filter each team to its clients**

On each team's row, click **Add filter**, choose **Company Type**, and pick that pod's type. Make sure the operator is **is**. Team filters use **is**, and only **Companies** and **Company Type** also allow **is not**. Each field can be used once per team.

**4. Set workload per pod (optional)**

Turn on **Set different limits per Inbox Team** to give each pod its own max active threads.

A pod set to **is not** gets every client except the ones you picked, so check the operator on each row.

## Rules for client routing

* **One profile per team.** A tech who works in two pods must be on both pods' teams.
* **Pinned clients need a backup.** The Assign action assigns the named tech even when they're out. Option C can fall back to a backup.
* **Agents overwrite; Auto-assign doesn't.** If a profile also covers the pinned client's tickets, keep the client out of the profile's filter.
* **Flows run once per ticket.** A pinned client's ticket that gets unassigned later isn't pinned again by the same Flow.


## Related topics

- [Triage, route, then dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/triage-route-then-dispatch.md)
- [Auto-assign plus an agent](https://docs.getthread.com/inbox/dispatch-scenarios/auto-assign-plus-an-agent.md)
- [Set Up Thread Inbox by Service Team Structure](https://docs.getthread.com/inbox/service-team-structure.md)
