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

# Dispatch recommendations

> Have an Agent Builder skill suggest who should take a ticket in a note, and leave the assignment to a dispatcher.

> [!NOTE]
>
> This pattern is less common, and guidance for it is based on limited use so far. Test it on a small set of tickets before you rely on it.

Not every desk is ready to let an agent assign. A recommendation skill does the dispatcher's legwork: who's free, who knows the client, what's related. It posts that as an internal note, and the dispatcher makes the call. It's also a safe way to trial a dispatcher skill before letting it write the owner.

## How recommendations work

This example uses a board, **Service Desk**, and a shared skill, **Dispatch Recommendation**.

| Piece | Set to |
| - | - |
| Flow conditions | Board is **Service Desk**, Status is **New** |
| Flow action | **Agent Builder → Run a Skill**: Dispatch Recommendation, with **only** the add note tool checked |
| Skill | Scores candidates and writes the top two with reasons, or "no clear pick" |

1. A new ticket lands in **New**, and the Flow runs the skill.
2. The skill posts a note: recommended tech, runner-up, and why.
3. The dispatcher reads the note and assigns the ticket.

## Variations

| Decision | Options |
| - | - |
| **What the note contains** | A recommended tech and runner-up with scores. Context only, with no name: related tickets, client history, and who's booked today. |
| **Trial mode** | Run your real dispatcher skill with only the add note tool checked, so it explains what it would do without doing it. Switch on the update ticket tool when you trust it. |

## Before you start

* The skill is a **shared** skill.
* Dispatchers know where to look for the note.

## Set up recommendations

**1. Write the skill**

Tell it to recommend, never assign, and to write plain text, since notes can sync to the PSA.

**2. Create the Flow**

Add the conditions, then **Agent Builder → Run a Skill**. Check the **add note** tool and nothing else.

Check the add note tool on purpose. With no tools checked, Run a Skill gets every write tool allowed in unattended runs, including the one that assigns.

## Rules for recommendations

* **The note only appears if the add note tool is checked.** In a Flow, the agent's reply isn't posted on its own.
* **Prompt the Agent in read-only mode can't post a note.** Read-only means no write tools at all.
* **One run per ticket per Flow.** The recommendation reflects the moment the Flow ran.


## Related topics

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