Skip to main content
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.
  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

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 and Flows.
  • 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.