How client routing works
This example uses one board, Service Desk, with status New, three pods, and clients tagged in the PSA with a Company Type for their pod.- A new ticket lands in New on Service Desk.
- Thread checks each team’s filter. The ticket’s company is tagged Pod B, so it’s in Pod B’s pool.
- Thread assigns it to the least-busy available Pod B tech who’s under the workload limit.
Options
Before you start
- Every client is tagged with its pod in the PSA, using one field such as Company Type.
- For Option A, each pod has its own Inbox Team. A team can belong to only one auto-dispatch profile.
- For Options B and C, you can create Flows. For C, the skill is a shared skill.
Set up the pods
1
Create one Auto-assign profile
In Dispatch scope, select the board under Dispatch from and set its dispatch status to New.
2
Add a team for each pod
Under Dispatch to, add each pod’s team.
3
Filter each team to its clients
On each team’s row, click Add filter, choose Company Type, and pick that pod’s type. Make sure the operator is is. Team filters use is, and only Companies and Company Type also allow is not. Each field can be used once per team.
4
Set workload per pod (optional)
Turn on Set different limits per Inbox Team to give each pod its own max active threads.
Rules for client routing
- One profile per team. A tech who works in two pods must be on both pods’ teams.
- Pinned clients need a backup. The Assign action assigns the named tech even when they’re out. Option C can fall back to a backup.
- Agents overwrite; Auto-assign doesn’t. If a profile also covers the pinned client’s tickets, keep the client out of the profile’s filter.
- Flows run once per ticket. A pinned client’s ticket that gets unassigned later isn’t pinned again by the same Flow.