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

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.