Skip to main content
Q-Director and AI settings

Q-Director: triage and routing

The Triage & Routing tab turns on Triage Assist, chooses the teams and ticket types its recommendation draws on, and sets how QuantumOps detects duplicate and recurring tickets for the Triage Dashboard.

Written By Chris Scaminaci

Last updated About 3 hours ago

The Triage & Routing tab of Q-Director Settings controls how QuantumOps helps dispatchers triage new tickets: Triage Assist, the teams and ticket types its recommendation can choose from, and the detection of duplicate and recurring tickets. Administrators use it, and dispatchers see the results on the Ticket Triage Dashboard.

Before you start: you need the Administrator or the Q-Director Configuration role. The team and ticket type lists come from HaloPSA, so your HaloPSA connection has to be working. Changes on this tab are kept when you select Save Changes at the top of the page.

Ticket types for triage dashboard and the Duplicate Detection, Recurring Incident Detection, Machine Learning Feedback and Dashboard Display & Performance cards appear only while Enable Triage Dashboard for dispatchers is on. It starts Off, so turn it on first when you set up a new organisation. The switch only shows or hides these settings; the Ticket Triage Dashboard itself opens whether it is on or off.

Turn on Triage Assist

  1. Open Triage & Routing.
  2. Under Triage Assist, turn on Enable Q-Director Triage Assist.
  3. Optionally pick Ticket types to run triage assist on. The next section says what the list does.
  4. Select Save Changes.

With Triage Assist on, QuantumOps triages each new ticket as it arrives. It prepares a recommendation for the dispatcher, together with the duplicate and recurring-ticket checks described below, and the full analysis of the ticket runs after triage.

Choose the teams and ticket types it recommends from

The AI recommendation picks a team and a ticket type for the ticket. These settings limit what it can pick. Ticket types with Portal, Triage or Dispatch in their name are always left out. When none of the ticket type lists on this tab is set, it can pick any other type.

What you setWhereWhat it does
Ticket types to run triage assist onTriage AssistThe AI recommendation chooses a ticket type from this list. When it is empty, the recommendation chooses from Target ticket types, and then from Ticket types for triage dashboard. The Triage Dashboard leaves the types you pick here out of its route-to list and does not suggest them. Dispatch treats tickets of these types as triage tickets, with the same fallback when the list is empty.
Target ticket typesUnder Auto triage and assign ticketsUsed when Ticket types to run triage assist on is empty.
Teams eligible for assignmentUnder Auto triage and assign ticketsThe teams it can recommend. When this is empty it uses Teams for Workload Sidebar, and when that is empty too, every team.

Teams eligible for assignment, Target ticket types and Triage outcome to use appear only while Enable Q-Director Triage Assist and Auto triage and assign tickets are both on. They keep applying after you turn Auto triage and assign tickets off, but you can change them only while both switches are on.

What Auto triage and assign tickets does

Turning on Auto triage and assign tickets does not make QuantumOps triage or assign tickets by itself. Dispatchers still triage and assign in HaloPSA, using the recommendation. Three of the options under the switch are used:

  • Teams eligible for assignment and Target ticket types, as described above.
  • Triage outcome to use is the HaloPSA action outcome your dispatchers apply when they have triaged a ticket. When QuantumOps sees an action with that outcome on a ticket, it marks triage as completed and the ticket moves on in Dispatch.

Set up the Triage Dashboard

The Triage Dashboard opens inside HaloPSA from a tab you add, as described in Adding QuantumOps tabs to HaloPSA. These settings shape what it shows.

  • Enable Triage Dashboard for dispatchers starts Off. While it is on, the tab shows Ticket types for triage dashboard and the Duplicate Detection, Recurring Incident Detection, Machine Learning Feedback and Dashboard Display & Performance cards. The switch only shows or hides these settings. The dashboard lists the ticket types you pick in Ticket types for triage dashboard first and prefers them when it suggests one. Leave it empty for no preference.
  • Pre-generate AI predictions under Dashboard Display & Performance starts On. QuantumOps analyses a ticket as soon as it arrives, instead of waiting for a dispatcher to open it, so the recommendation is ready. This suits a busy desk.
  • Teams for Workload Sidebar. Only the teams you pick appear in the agent workload sidebar. Leave it empty to show every team.

Use recommended values in Dashboard Display & Performance fills the section with the suggested values. Nothing is kept until you select Save Changes.

Tune duplicate detection

The Duplicate Detection card, which shows only while Enable Triage Dashboard for dispatchers is on, decides which earlier tickets QuantumOps lists as possible duplicates of a new one. Duplicate tickets and recurring issues shows what technicians and dispatchers see. QuantumOps compares a new ticket with tickets it has already analysed. It lists an earlier ticket when its content is at least as similar as the Content Similarity Threshold, or when its subject line matches closely enough and subject line matching is on.

SettingChoicesStarts atWhat it does
Detection ScopeSame Client, Same User, GlobalSame ClientCompares only with the same client's tickets, only with the same user's, or with every ticket.
Lookback Period (days)7 to 36590How far back to look. A longer period finds more and takes longer.
Status FilterOnly Open, Open & Closed, Open & Recently ClosedOnly OpenWhich earlier tickets to compare with.
Recently Closed Period7 to 90 days30How recently a ticket must have closed. Shown only for Open & Recently Closed.
Content Similarity Threshold70% to 100%, in steps of 590%How alike two tickets must be. A higher value gives fewer false matches and may miss some duplicates.
Enable subject line matchingOn or offOnLists tickets with nearly identical subject lines even when their content differs.
Subject Match Threshold95% to 100%, in steps of 198%How close the subject lines must be. Shown only while subject line matching is on.

Use recommended values sets the lookback, the recently closed period and the two thresholds to the starting values above. Nothing is kept until you select Save Changes.

If dispatchers see too many wrong matches, raise Content Similarity Threshold in steps of 5%, narrow Detection Scope to Same Client or Same User, shorten Lookback Period (days), or choose Only Open. You can also raise Subject Match Threshold, or turn subject line matching off. If duplicates never appear, do the reverse: lower the threshold toward 70%, widen the scope, lengthen the lookback and include closed tickets.

Tune recurring ticket detection

The Recurring Incident Detection card decides when QuantumOps tells a dispatcher that a ticket looks like part of a repeating problem. A ticket is similar when it has the same category or the same resolution category as the new one and was created within the time window. QuantumOps counts the other similar tickets at three levels and flags the ticket when a count reaches its threshold. The four fields below show while Enable recurring incident detection is on, and it starts On.

SettingAllowedStarts atCounts
User Threshold2 to 102Similar tickets from the same user
Client Threshold3 to 203Similar tickets from the same client
Global Threshold5 to 505Similar tickets across all clients, a possible major incident
Time Window (days)7 to 9030How far back to count

Because similar means the same category, recurring detection works best when tickets are categorised. See Q-Director: sentiment and categorisation. If too many tickets are flagged, raise the thresholds or shorten the window. The three thresholds cannot go below their starting values, so to catch more, lengthen Time Window (days) and check that your tickets carry categories. Use recommended values sets the four numbers back to their starting values.

Other options on this tab

These options complete the cards above.

OptionWhereChoicesStarts at
Auto-flag high-confidence duplicates and Show merge buttonDuplicate DetectionOn or offOn
Enable recurring incident detectionRecurring Incident DetectionOn or offOn
Track dispatcher correctionsMachine Learning FeedbackOn or offOn
Min Corrections Before RetrainingMachine Learning Feedback, shown while corrections are tracked10 to 50050
Evaluation ModeDashboard Display & PerformanceQuick, Deep, AutoAuto
Auto-refresh (seconds)Dashboard Display & Performance10 to 30030
Max Similar TicketsDashboard Display & Performance3 to 2010
Show agent workload indicators, Show client health & VIP indicators and Show ML priority scoreDashboard Display & PerformanceOn or offOn

The Manager Review note under Track dispatcher corrections says the Require manual review setting for corrections is on the Dispatch & Scheduling tab under Routing & Review. The switch there is labelled Enable Manager Review. See Override and feedback review.