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

# Auto-assign plus an agent

> Keep an Auto-assign profile for most tickets and let an Agent Builder skill handle the slice a profile can't, such as a client, a specialist queue, or a status that triage sets.

Auto-assign is the simplest way to dispatch, but one profile per dispatch status can't express everything. You can keep a profile for most of the work and carve out the rest for an **Agent Builder** skill in a **Flow**. Both set the ticket's owner, so the setup is about keeping their tickets apart.

## How the split works

This example splits one board, **Help Desk**, by status. Both sides use the same team.

| Handled by | Scope | Assigns | Extras |
| - | - | - | - |
| Auto-assign profile | Dispatch status **New** | Least-busy available tech | None |
| Flow + skill | Board is **Help Desk**, Status is **Needs specialist**, Owner is blank | The skill's pick from a specialist pool, by workload | Note with the reason |

1. A ticket lands in **New**. It's in the profile's dispatch status, so Auto-assign assigns it.
2. Triage moves an unassigned ticket to **Needs specialist**. The profile doesn't dispatch from that status. The Flow matches and its skill assigns it.
3. Auto-assign never takes a ticket that already has an owner, so it won't undo the skill's pick.

The skill, though, *will* overwrite an owner if you let it. Keep the two scopes from overlapping, and tell the skill to skip owned tickets.

## Variations

| Carve-out | Profile handles | Agent handles |
| - | - | - |
| **Client** | Everyone else | One client's tickets, pinned to named techs (see [Pod and client dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/pod-and-client-dispatch.md)) |
| **Specialist queue** | General service desk | Tickets matching a board item, alert source, or category, sent to a specialist pool |
| **By status** | Tickets in its dispatch status | Tickets in a different status that triage sets, assigned and booked on the Planner |
| **Escalation back to the profile** | Re-dispatches tickets that come back unowned | A Flow on an escalation status removes the owner so the profile picks the ticket up |
| **Review the profile's pick** | Assigns first | Checks the profile's choice and keeps or replaces it. Replacing undoes Auto-assign's balancing. See the note below |

> [!NOTE]
>
> Guidance for **Review the profile's pick** is based on limited use so far. Test it on a small set of tickets before you rely on it.

## Before you start

* You can describe the carve-out with Flow conditions.
* You know how to create a profile and a Flow. See [Auto-dispatch profiles](https://docs.getthread.com/inbox/auto-dispatch-profiles.md) and [Flows](https://docs.getthread.com/inbox/flows.md).
* The skill is a **shared** skill.

## Set up the split

**1. Configure the profile**

Create or edit the Auto-assign profile, and use a team filter (for example Companies) or a separate dispatch status so it leaves the carve-out alone.

**2. Build the skill**

Give it the carve-out's pool and rule. Tell it to do nothing if the ticket already has an owner.

**3. Create the Flow**

Conditions: exactly the carve-out, plus Owner is blank. Action: **Agent Builder → Run a Skill**, with only the update ticket and add note tools checked.

**4. To hand a ticket back to the profile**

Remove the owner and set a status the profile dispatches from. Auto-assign then treats it as unassigned.

On brand-new tickets, Auto-assign can wait up to 90 seconds for auto-categorize and auto-prioritize to finish. Don't rely on which one acts first. Keep the scopes from overlapping instead.

## Rules for a split

* **Auto-assign skips owned tickets. Agents don't.** The profile never overwrites an owner. The agent's update ticket tool does, unless the skill is told not to.
* **No second profile on the same status.** Two Auto-assign profiles can't share a dispatch status on a board, so use the Flow for an overlapping slice.
* **The Flow runs once per ticket**, and Auto-assign re-checks unowned tickets as they change.
* **The Assign action is not a dispatcher.** The Flow's **Assign** action assigns the member you name or the board's on-call member, or removes the owner. It doesn't weigh workload or availability.
* **Track the agent's share from the Flow.** Use the Flow's run history and the agent's notes.


## Related topics

- [Agent dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/agent-dispatch-on-a-shared-board.md)
- [Tiered dispatch with agents](https://docs.getthread.com/inbox/dispatch-scenarios/tiered-dispatch-with-agents.md)
- [Triage, route, then dispatch](https://docs.getthread.com/inbox/dispatch-scenarios/triage-route-then-dispatch.md)
