How agent dispatch works
This example uses a board, Service Desk, with a status Ready to be Assigned, and a shared skill, Service Desk Dispatcher.- Intake or triage moves a new ticket to Ready to be Assigned.
- The Flow matches it and runs Service Desk Dispatcher.
- The skill checks the ticket has no owner, scores the pool, and sets the winner as owner with the update ticket tool. It can also set a status or book a schedule entry, if you checked those tools.
- If no one qualifies, the skill writes nothing except a note, and the ticket waits for a dispatcher.
Variations
Every desk builds the dispatcher a little differently. Pick one option per row and write it into the skill.Before you start
- The board has a status that means “ready to assign”, and intake or triage sets it.
- No Auto-assign profile dispatches from that status on that board. If one does, see Auto-assign plus an agent.
- The skill is a shared skill. Run a Skill only runs shared skills.
- You know how to build a Flow with an Agent Builder action. See Flows. The Smart Dispatch and Tier Dispatcher prompts are good starting points.
Set up agent dispatch
1
Write the dispatcher skill
Create a shared skill with your pool and your picking rule. Tell it to: do nothing if the ticket already has an owner; never pick a deactivated or excluded tech; set the owner with the update ticket tool; add a plain-text internal note with the reason; and when there’s no clear winner, assign no one and say so in the note.
2
Prove it by hand
Run the skill in Super Magic on a few real tickets. Check it picks the tech your dispatcher would, and leaves owned tickets alone.
3
Create the Flow
Add the conditions from the table above. Add Agent Builder → Run a Skill, choose the skill, and check only the write tools it needs: update ticket, add note, and the schedule tool if it books time. Turn the Flow on.
4
Watch the first week
Read the agent’s notes daily, and compare the Flow’s run history with the tickets that actually got an owner.
Rules for agent dispatch
- One run per ticket per Flow. A failed or declined run still counts, and nothing retries it.
- The agent overwrites. The update ticket tool assigns whoever the skill names, even if the ticket already has an owner. Guard against it in the Flow conditions and in the skill.
- Auto-assign never takes an owned ticket. If a profile also covers this status, the profile skips tickets the agent already assigned. The agent can still overwrite the profile’s pick.
- Shared skills only. A personal skill in Run a Skill does nothing, and the run still shows as succeeded.
- “Succeeded” means it ran. Run history marks a run succeeded when it starts. Check the ticket’s owner and the agent’s note to see what happened.
- Notes need the add note tool. In a Flow, the agent’s reply isn’t posted on the ticket.
- The skill acts as its creator, or as an active admin if the creator isn’t an active member.
- Schedules. The skill can read Planner entries. Thread’s built-in agent tools don’t read work schedules or time off. Keep shifts and absences in the skill, or use After-hours and shift dispatch.
- Get next thread doesn’t run in Flows. It only works for a technician in Super Magic.
- Track agent dispatch from the Flow. Use the Flow’s run history and the agent’s notes to see what it assigned and why.