Skip to main content
Dispatch

Dispatch workflow and scheduling settings

Tune how QuantumOps schedules appointments, estimates how long tickets take, ranks each technician's work, routes by skill and holds dispatcher corrections for review.

Written By Chris Scaminaci

Last updated About 1 hour ago

These settings control how QuantumOps books appointments, estimates how long a ticket will take, ranks each technician's work, suggests technicians by skill and holds dispatcher corrections until someone approves them. They apply to your whole organisation. Scheduling, estimation, guided work, colour sync and skill-based routing all start off. Manager review starts on.

Before you start: the Dispatch Workflow Settings screen needs the Administrator role. To open it from Module Management, the Call Center Operations module must be on (see Module Management). The Dispatch & Scheduling and Advanced tabs of Q-Director Settings (Q-Director Config in the sidebar) need the Administrator role or the Q-Director Configuration role.

Two screens edit the same settings

Dispatch Workflow SettingsQ-Director Settings
Open itIn Module Management, find the Call Center Operations card and select Open Module. The card shows the button only while the module is on.Open Q-Director Settings and choose the Dispatch & Scheduling tab or the Advanced tab.
Who can use itAdministratorsAdministrators and the Q-Director Configuration role
Save withSave SettingsSave Changes, top right
Only on this screenThe JSON settings as plain text boxesEnable Dispatcher Workflow, Workflow Phase, Include scheduling in triage recommendations, Colour palette, Use recommended values, and a JSON editor with Format and Validate

Both screens write the same settings. A change you save on one shows on the other the next time it loads. If you keep both open, whichever you save last replaces the other's values, so reload a screen before you edit it.

The Dispatch Workflow Settings screen groups the controls under Appointment Defaults, Estimate Defaults, Guided Work, Routing & Review, Appointment Type Behavior, Override Reasons and Advanced JSON Configuration. Four tiles at the top, Scheduling, Routing, Guided Work and Review, show whether each area is Enabled or Disabled. The Dispatch & Scheduling tab uses the same group names, with Dispatcher Workflow first.

Switch the workflow on

Dispatcher Workflow is the first section of the Dispatch & Scheduling tab.

  • Enable Dispatcher Workflow shows whether any of three features is on: Enable Guided Work to Zero, Enable Historical Estimation or Enable Skill-Based Routing. Switch those on or off in the sections below. When you save, QuantumOps sets Enable Dispatcher Workflow to match them, so it is on when any of the three is on.
  • Workflow Phase records how far along your rollout is. The choices are Disabled, Recommend Only, Dispatcher Approval Required, Manager Approval Required For Learning, Colour Sync Enabled and Auto Scheduling Eligible. Choosing a phase is saved with your settings but does not switch any feature on or off, because each feature has its own switch.

Colour Sync Enabled and Auto Scheduling Eligible are entries in the phase list, not switches. The switches are Enable Halo Colour Sync and Auto-Scheduling Eligibility.

Two buttons sit under the list. Override Review Queue opens Override and feedback review. Dispatch Control Center opens the older in-app dispatch screen (see The legacy Dispatch Control Center).

Set up appointment scheduling

With scheduling on, a dispatcher who sends a ticket to a specific technician on the Ticket Triage Dashboard sees Commitment, Appointment Type and Available Slots. The call-taking ticket form offers the same choices. See Ticket Triage Dashboard and Call scripts and creating the ticket.

SettingWhat it doesStarts as
Enable Appointment SchedulingThe master switch for appointments. Switching it off turns off every appointment feature. The Dispatch Workflow Settings screen calls it Enable appointment scheduling.Off
Lookahead DaysHow many days ahead QuantumOps looks for free slots.5
Slot Duration MinutesHow long each slot is when QuantumOps searches for availability.60
Fallback Duration RatioWhen there is no history to go on, an appointment is estimated as the resolution estimate multiplied by this number.0.50
Auto-Scheduling EligibilityMarks your organisation as eligible for automatic scheduling flows. QuantumOps does not currently book an appointment without a dispatcher choosing the slot, so this switch changes nothing you can see today.Off
Include scheduling in triage recommendationsQ-Director Settings only. When it and appointment scheduling are both on, the AI triage recommendation also suggests a technician, a time slot and a duration.Off

Set up historical estimation

With Enable Historical Estimation on, QuantumOps estimates how long a ticket will take from the tickets your team has already resolved. It shows a range, Best, Expected and Conservative, for resolution and for appointment length. The ranges appear on the Ticket Dashboard and the Ticket Triage Dashboard. The Dispatch Workflow Settings screen calls the switch Enable historical estimation.

SettingWhat it doesStarts as
Minimum Sample SizeHow many past tickets of the same kind QuantumOps needs before it trusts the history over a fallback.10
Lookback DaysHow far back it looks for past tickets.365
IQR MultiplierHow unusual a past ticket must be before QuantumOps leaves it out. A higher value keeps more of the very long and very short tickets. A lower value discards more of them.1.50
Default Resolution HoursThe resolution estimate used when there is no history and the AI has no estimate for the ticket.8
Default Appointment HoursThe appointment length used when there is neither history nor a resolution estimate to scale.2

With too little history for a ticket, QuantumOps falls back to the AI's estimate for that ticket, or to Default Resolution Hours, and marks the estimate as a fallback. QuantumOps rebuilds its estimate history about every six hours, so a change to Lookback Days or IQR Multiplier reaches estimates after the next rebuild.

In Q-Director Settings, a Recommended hint sits under Minimum Sample Size and Lookback Days. Use recommended values fills both with the recommended figures. Nothing is saved until you select Save Changes.

Rank technicians by skill

Enable Skill-Based Routing is off at the start. With it on, the technician suggestions for a ticket compare each technician's skills with the skills the ticket needs, and weigh that match against capacity, familiarity with the client, burnout risk and quality. With it off, the suggestions use those other factors and do not match skills. The ranking appears on the Ticket Triage Dashboard.

SettingWhat it doesStarts as
Skill Match ThresholdThe lowest skill match score, from 0 to 100, that counts a technician as a match. A lower value widens the pool.70
Development Gap ToleranceHow many skill-gap points below the threshold a technician can be and still be offered tickets for development.3

Decide whether corrections need approval

Enable Manager Review (Enable manager review on the Dispatch Workflow Settings screen) is on at the start, in the Routing & Review section.

  • With it on, every dispatcher correction and technician override, and every piece of copilot feedback, waits as pending. Only items someone approves are used to tune future recommendations.
  • With it off, new items are approved straight away and are used for learning immediately, so nothing waits for review. Items that are already pending stay in the review list until someone decides them.

The Manager Approval Required For Learning entry in the Workflow Phase list is not this switch. See Override and feedback review.

Guided work and colour sync

Enable Guided Work to Zero, Enable Halo Colour Sync, the colour palette, Yellow Queue Size, Refresh Interval Minutes and the three weights (Priority Weight, SLA Weight and Age Weight) are in the Guided Work section. Guided work and HaloPSA colour sync explains what they do and what technicians see.

Settings held as JSON

Eight cards hold advanced behaviour as JSON text. On the Dispatch Workflow Settings screen, Appointment Type Behavior and Override Reasons have their own boxes. The other six sit under Advanced JSON Configuration, in boxes named for the card, for example Appointment Scheduling JSON. In Q-Director Settings, all eight are on the Advanced tab.

CardWhat it controls
Appointment Type BehaviorWhich HaloPSA appointment type is chosen for a tentative booking and for a firm one, and whether a dispatcher may change it.
Override ReasonsThe reasons a technician can give for working a ticket other than their red one.
Appointment SchedulingWhether scheduling forms offer the Commitment choice.
Estimate StrategyHow much of a client's own history is needed before an estimate is adjusted for that client.
Routing WeightsHow much each factor counts when QuantumOps ranks technicians for a ticket.
Actionability RulesWhich ticket statuses count as waiting, so that a ticket in them is not ranked as work to do now.
Guided Order RulesSaved with your settings and checked as valid JSON. QuantumOps does not currently use them to change what technicians see.
Manager Review GatesSaved with your settings and checked as valid JSON. QuantumOps does not currently use them to change what is held for review.

An empty card means QuantumOps uses its built-in values. On the Advanced tab the preview of such a card reads Not configured.

Fields that take effect

CardFieldsNotes
Appointment Type BehaviorTentativeDefaultTypeId, FirmDefaultTypeId, AllowDispatcherOverrideThe two ids are HaloPSA appointment type ids. They preselect the Appointment Type for a tentative and a firm booking. With AllowDispatcherOverride set to false, Appointment Type is greyed out for dispatchers. It starts as true.
Appointment SchedulingShowTentativeAndFirmToggleSet it to false to hide Commitment. It starts as true.
Estimate StrategyClientAdjustmentMinSampleSizeIt starts as 20.
Routing WeightsLiveCapacityWeight, CategorySkillWeight, ClientFamiliarityWeight, BurnoutSafetyWeight, QualityFitWeight, DevelopmentFitWeightWhole numbers. They start as 35, 25, 15, 10, 10 and 5.
Actionability RulesNonActionableStatusIdsA list of HaloPSA status ids.
Override ReasonsCode, Label, RequiresNote, ExcludeFromLearningA list with one entry per reason. Label is what technicians see. RequiresNote asks them for a short note. ExcludeFromLearning keeps an override with that reason out of learning even after it is approved.

Other field names in these cards are accepted but have no effect today.

A short example for Appointment Type Behavior, with made-up ids:

{
  "TentativeDefaultTypeId": 5,
  "FirmDefaultTypeId": 6,
  "AllowDispatcherOverride": false
}

An example for Override Reasons:

[
  { "Code": "CustomerCalledIn", "Label": "Customer called in" },
  { "Code": "Other", "Label": "Other", "RequiresNote": true },
  { "Code": "TrainingTicket", "Label": "Training ticket", "ExcludeFromLearning": true }
]

Until you save your own list, Override Reasons holds five reasons: Customer called in, Manager directed, Dependency on another ticket, Quick follow-up and Other, which asks for a note. Clear the box and save to return to those five.

Edit a JSON card

On the Dispatch Workflow Settings screen:

  1. Edit the text in the box.
  2. Select Save Settings. QuantumOps checks every box first. If one is not valid, a message names it, for example Appointment Type Behavior JSON is invalid., and nothing is saved.

In Q-Director Settings, open the Advanced tab and select Edit on the card. Q-Director Settings walks through the editor and the two Save Changes buttons.

Two checks apply. Validate and the editor's Save Changes check only that the text is JSON, and the editor will not keep text that is not. Whether it is the shape the card expects, a list for Override Reasons and an object for the others, is checked when you select Save Changes at the top of the page, or Save Settings on the Dispatch Workflow Settings screen. In both places a card that fails is named in a message, and nothing is saved. Neither check confirms that a field name is one QuantumOps uses, so check your spelling against the table above.

Save your changes

On the Dispatch Workflow Settings screen, select Save Settings. The message Dispatcher workflow settings saved. confirms it. In Q-Director Settings, select Save Changes at the top right. It saves every tab of the page together. The count in the confirmation covers only the general Q-Director fields that changed. A change to these dispatch settings alone is confirmed as Settings saved (no tenant fields had changed) and is still saved.