Skip to content

Dispatch Recommendations ​

Dispatch recommendations help your coordinator choose a technician for a new, unassigned PSA ticket. Junto ranks technicians using relevant ticket history and workload, with company and category rules that you control.

Dispatch runs in one of three modes. Shadow and Internal note only recommend: your team still makes the assignment in your PSA. Assign goes one step further and makes the recommended technician the ticket owner in your PSA, then messages them in Slack or Teams. You can choose a different mode for specific boards and companies, so you can start assigning on one board while the rest of your tickets stay in Shadow.

Before You Start ​

  • Connect your PSA and sync ticket and assignment history. Recommendations need eligible technicians with recent ticket ownership in that PSA.
  • Enable Triage Assistant in Settings → Processors. Its board or queue filters and company exclusions also determine which tickets receive a dispatch recommendation.
  • An Owner or Admin can configure Dispatch. Managers, Admins, and Owners can review dispatch activity.
  • For Assign mode notifications, connect Slack or Microsoft Teams and make sure each technician has a Junto account that is linked to their PSA member and matched under Manage Users.

Dispatch runs for new PSA tickets that are unassigned when processing begins. Tickets already assigned to a technician or resource are skipped. A ticket assigned while triage is running may also have no recorded recommendation.

Choose a Mode ​

Turning Dispatch on or off is done with the switch on the Processors page. While it is on, each ticket gets one of these modes:

ModeWhat happens
ShadowRecords the pick and compares it with who was actually assigned. Nothing is written to the ticket. Use this to measure how often Junto agrees with your team.
Internal noteAlso lists the ranked technicians in the internal triage note, recommended technician first.
AssignAlso makes the recommended technician the ticket owner in your PSA, when the ticket has none, and messages them in Slack or Teams. Requires confirmation.

Internal note and Assign follow your Triage Assistant note-posting settings. To show the ranked technicians in your PSA, enable Auto-post triage note and make sure note posting is allowed for the ticket's company.

How Assign Mode Works ​

Assign mode is the only mode that changes the ticket itself. Without it, Dispatch never assigns tickets.

  • Only unowned tickets -- Right before writing, Junto reads the ticket's current owner from your PSA. If someone has already taken the ticket, Junto leaves it alone and records why.
  • Who is assigned -- When a company or category rule picked the technician, that technician is assigned. Otherwise Junto assigns the first ranked technician who isn't off shift. A technician counts as off shift when their recent time entries show they never work at that hour of the week; technicians with no work pattern yet are treated as available.
  • No approval step -- Assign mode is a processor setting, not an agent tool, so assignments happen without a technician approving each one. That is why saving Assign asks for confirmation first.
  • Assignee message -- After assigning, Junto sends the technician a direct message in Slack or Teams titled Junto assigned you a ticket, with a link to the ticket, the client, and the triage reasoning. The reasoning is only included when the assignee is the technician it was written about. A technician without a Junto account or a Slack or Teams mapping is still assigned; the activity page shows why they weren't notified.
  • Supported PSAs -- ConnectWise PSA (ticket owner), Autotask (primary resource), HaloPSA (agent), and Syncro.

If your organization has more than one PSA connected, a company or category rule cannot assign, because the same technician identifier can point to different people in each PSA. Those tickets show Not assigned with the reason on the activity page.

Enable and Configure ​

  1. Open Settings → Processors.
  2. Under Assignment & escalation, find Dispatch recommendations and select Configure.
  3. Choose the Default mode, then review where Dispatch runs, mode overrides, routing rules, exclusions, and history settings below.
  4. Select Save dispatch settings. If the save lets Dispatch assign tickets it could not assign before, confirm the Let dispatch assign tickets? dialog by selecting Allow assignment.
  5. Turn on the Dispatch recommendations switch. It turns on in the mode you saved; until you choose otherwise, that is Shadow.
  6. Let new tickets arrive and select View activity to review the results.

You can choose and save the mode while Dispatch is off; the Configure dialog notes that the mode applies once you turn Dispatch on. Turning the switch off and back on keeps your saved mode.

Settings changes apply to new tickets. Enabling Dispatch does not generate recommendations or assignments for an existing backlog. Switching from Assign back to Shadow or Internal note never needs another confirmation.

A cautious way to start is to run Shadow for a few weeks, move to Internal note once the match rates look right, and then use a mode override to try Assign on a single board before widening it.

Where Dispatch Runs ​

OptionDefaultDescription
Where dispatch runsAll boardsChoose All boards or Selected boards. The label follows your PSA: boards in ConnectWise, queues in Autotask, teams in HaloPSA, and issue types in Syncro. Tickets on other boards get no dispatch at all unless a mode override names their board.
Excluded companiesNoneDispatch never runs for an excluded company, whatever its board or override.
Mode overridesNoneGive a company, a board, or a company on one board its own mode. Select Add mode override, then choose a company (or Any company), a board (or Any board), and a mode.

Junto resolves each ticket's mode in this order, and the first match wins:

  1. The ticket's company is in Excluded companies: no dispatch.
  2. An override for that company on that board.
  3. An override for that company on any board.
  4. An override for that board.
  5. Selected boards is chosen and the ticket's board isn't selected: no dispatch.
  6. Otherwise, the Default mode.

Each company, board, or company-and-board combination can have one override. Overrides choose between Shadow, Internal note, and Assign; to turn Dispatch off for a company, add it to Excluded companies instead.

Selected boards belong to the PSA you chose them from. If you connect a different PSA later, the dialog asks you to clear the saved boards before choosing boards from the new one. Company exclusions and company overrides apply to every PSA.

Recommendation Options ​

OptionDefaultDescription
Company overridesNoneChoose a preferred technician for a company. A company override takes precedence over a category override.
Category overridesNoneChoose a preferred technician for a ticket category. Categories use Junto's Category & Tag Extractor results.
Excluded techniciansNonePrevent selected technicians from being recommended or assigned, including through an override. Use this for dispatchers, administrators, or anyone who should not receive tickets.
History lookback90 daysChoose the history window used for recommendations. Standard choices are 30, 60, and 90 days.
Maximum candidatesTop 5Choose how many candidates to consider: Top 1, Top 3, or Top 5. Fewer may be available for a ticket.

Select Add company rule or Add category rule, then choose the company or category and a technician. Each company or category can have one rule. Complete or remove empty rows before saving.

An override applies only when its technician is eligible for that ticket's PSA and has owned a ticket within the selected history window. The form displays a warning when a saved rule lacks that history. An override cannot make an excluded technician eligible.

Use Excluded technicians to keep inactive or otherwise ineligible staff out of recommendations, even if they still appear in recent ticket history.

Review Dispatch Activity ​

Select View activity beside Dispatch recommendations. The activity page shows each ticket, its ranked recommendation, the first actual assignment, and the outcome. Open Recommendation details to see the recorded explanation and confidence, or select a ticket to inspect it. Use Refresh to load recent activity.

Managers can open the Dispatch activity page directly. Access to the Processors configuration page requires an Admin or Owner role.

OutcomeMeaning
Assigned by JuntoAssign mode made the recommended technician the owner.
Matched · Top 1The first assignment went to the recommended technician.
Top 3 match or Top 5 matchThe first assignment went to another technician within that ranked group.
DifferentThe first assignment did not match the displayed ranked candidates.
PendingA first assignment has not yet been recorded for comparison.
UnknownThe first assignment or comparison result was not recorded.

The summary shows all-time recommendation and comparison counts, plus Top 1, Top 3, and Top 5 assignment match rates. These measure agreement with your team's first assignments; they do not measure whether a technician was the best person to resolve the ticket.

Pending and unknown assignments are excluded from match rates. Tickets Junto assigned itself are also excluded, because their owner is the recommendation by definition. Top 3 and Top 5 rates only include tickets processed with a maximum-candidate setting of at least 3 or 5, respectively. Later reassignments do not change the first-assignment comparison.

Assign Mode Results ​

Once Assign mode has run, three more cards appear:

  • Assigned by Junto -- tickets Junto assigned, and how many technicians were notified.
  • Still owned by the assignee at resolution -- of the assigned tickets that have resolved, how many were still owned by the technician Junto picked. This is the best signal that Assign is choosing well.
  • Assign mode ran, nobody assigned -- tickets that were already owned, had no technician on shift, or were refused.

Each assigned ticket in the table also notes whether the technician was notified. When Assign mode ran without assigning, the table shows the reason:

NoteMeaning
Not assigned: the ticket already had an owner.Someone took the ticket before Junto wrote the owner.
Not assigned: no ranked technician was on shift.Every ranked technician was off shift for that hour of the week.
Not assigned: a routing rule matched, and rules cannot assign while more than one PSA is connected.See the note on multiple PSAs above.
Not assigned: Assign mode no longer applied to this ticket.The mode or scope changed before the assignment ran.
Not assigned: the PSA rejected the assignment.Your PSA refused the write. Check the integration's permissions and the technician's PSA account.

Troubleshooting ​

IssueWhat to check
No recommendations appearConfirm Dispatch is on, Triage Assistant is enabled, and new unassigned tickets are arriving. Check Where dispatch runs, Excluded companies, Triage's board or queue filters and company exclusions, and whether eligible technicians have synced ownership history.
Recommendations appear in activity but not in PSA notesShadow mode deliberately keeps them out of notes. In Internal note or Assign mode, check Auto-post triage note and the company's note-posting settings.
Assign mode isn't assigning a board or companyWalk the order under Where Dispatch Runs: an exclusion, a more specific override, or an unselected board may give that ticket a different mode.
Not assigned: the PSA rejected the assignmentConfirm the Junto API account can update tickets. In Autotask, the technician must belong to a Service Desk Queue before Autotask lets them be assigned. In HaloPSA, the Unassigned agent can never be assigned.
The assignee wasn't notifiedLink the technician's Junto account to their PSA member, and match their Slack or Teams account under Settings > Notifications > Slack (or Teams) > Manage Users.
An override does not applyCheck the technician's history in the ticket's PSA, the selected lookback window, exclusions, and any company override that takes precedence over a category rule.
The boards list is disabledThe saved boards were chosen from a different PSA. Select Clear boards (or queues, teams, or issue types) to choose from the PSA now connected.
Technicians or categories do not loadClose and reopen Configure to retry. Check that your PSA data has synced.
Activity or metrics do not loadSelect Retry or Refresh, and confirm you have Manager access or higher.

See Triage Note for the surrounding triage workflow and Catchall Ticket Router for routing tickets to the correct company or service board.