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

# Skill-match dispatch

> Send each ticket to the technician who owns that kind of work, using a routing matrix in an Agent Builder skill that a Flow runs.

Some desks route by expertise: firewall alerts go to the network specialist, backup alerts to the backup owner, billing questions to the account manager. Auto-dispatch profiles don't match tickets to technician skills. You can do it with an **Agent Builder** skill that holds a routing matrix, plus a **Flow** that runs it on the tickets the matrix covers.

## How skill-match dispatch works

This example uses a board, **Security Alerts**, and a skill, **Alert Routing Matrix**.

| Ticket matches | Primary | Backup |
| - | - | - |
| Alert source **Firewall** | Network specialist | Second network tech |
| Alert source **Backup** | Backup owner | Service desk lead |
| Anything else | No one: leave for dispatcher | — |

1. A new alert lands on **Security Alerts**.
2. The Flow matches the board and runs **Alert Routing Matrix**.
3. The skill reads the ticket, finds the row that matches, and assigns the primary. If the primary is out, it assigns the backup.
4. If nothing matches, it assigns no one and adds a note.

The matrix lives in the skill's instructions, so changing who owns a type of work means editing the skill.

## Variations

| Decision | Options |
| - | - |
| **What the matrix keys on** | Alert source or monitoring tool. Ticket category or type. Board item or sub-type. Keywords in the summary. |
| **Who it names** | One named tech per row. A primary and a backup. A small specialist pool, balanced by workload (combine with [Agent dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/agent-dispatch-on-a-shared-board.md)). |
| **Scoring instead of a table** | Score each tech on specialty fit, past tickets for this client, and current workload, then pick the top score, as in the [Smart Dispatch](https://docs.getthread.com/skill-library/scheduling-and-dispatch/smart-dispatch.md) prompt. |
| **What else it writes** | Owner only. Owner and a status such as **Assigned**. Owner and a move to a specialist board. |

## Before you start

* You can write the matrix down: every row, its primary, and its backup.
* The tickets the matrix covers can be picked out with Flow conditions, such as a board, a source, or a type.
* The skill is a **shared** skill.

## Set up skill-match dispatch

**1. Write the matrix into a shared skill**

List each row and who owns it. Tell the skill to check the ticket has no owner first, to fall back to the backup when the primary is deactivated or out, and to assign no one when nothing matches.

**2. Create the Flow**

Set the conditions to the tickets the matrix covers. Add **Agent Builder → Run a Skill**, choose the skill, and check the update ticket and add note tools. Turn the Flow on.

**3. Name an owner for the matrix**

Pick one person who updates the skill whenever someone joins, leaves, or changes role.

## Rules for skill-match dispatch

* **The skill only knows what you wrote.** Thread doesn't store technician skills for it to read. A matrix that names someone who left keeps sending them work until you edit it.
* **"Out" has to come from somewhere.** The skill can see who is available for dispatch only through an enabled Auto-assign profile. Otherwise keep absences in the skill.
* **One run per ticket per Flow**, and a declined or failed run isn't retried.
* **The agent overwrites an existing owner** unless the skill and the Flow conditions guard against it.
* **Check only the tools it needs.** With none checked, Run a Skill gets every write tool allowed in unattended runs.


## Related topics

- [Agent dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/agent-dispatch-on-a-shared-board.md)
- [After-hours and shift dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/after-hours-and-shift-dispatch.md)
- [Pod and client dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/pod-and-client-dispatch.md)
