Skip to main content
Getting started

Setup wizard: AI and Q-Director

Steps 4 to 9 of the setup wizard: choosing managed AI or your own keys and models, then setting Q-Director's analysis, triage, intelligence, web search and Customer Success options, with safe choices for a first setup.

Last updated 26 days ago

Steps 4 to 9 of the setup wizard decide how AI runs and how Q-Director, the part of QuantumOps that analyzes and triages tickets, behaves on your desk. Only an Administrator can use them. Every setting here can be changed after setup, so a first setup does not have to be perfect.

Before you start: finish steps 2 and 3. The wizard unlocks these steps in order.

Safe choices for a first setup

StepA sensible first choice
4Managed AI: leave the key fields empty, keep the models the wizard preselects, keep Smart Queuing on.
5Keep the starting values. Where the screen shows a recommended value, use it. Leave category creation off.
6Leave Post Sherlock research results to ticket, auto-triage, on-call alerts and escalation paths off until you have read the page that covers each.
7Keep the starting values. Leave the dispatcher workflow off.
8Keep Tavily + Bing.
9Switch the dashboard on only if you plan to use Customer Success.

Some options change things in HaloPSA: Allow Q-Director to create categories, Recategorize ticket on closure and Set resolution category on closure in step 5, Post Sherlock research results to ticket and Auto triage and assign tickets in step 6, and Enable Halo Color Sync in step 7, which sets the color of tickets. Switch each of them on deliberately, not by accident. Once it is fully set up, Auto triage and assign tickets changes tickets in HaloPSA on its own: it adds a private action that sets a team and a ticket type, and the impact and urgency if you checked that option. The other triage options only prepare recommendations, and dispatchers still triage and assign tickets in HaloPSA. See Q-Director: triage and routing.

Step 4: AI Configuration

The header contrasts two ways to run AI: Managed (pay per use) and BYOK (your API keys). Leave the API Key under Anthropic empty to use managed AI. Enter your own keys to bring your own.

Choose the models

Select a model field to open the model picker. Models from providers you have not switched on are grayed out.

FieldWhat it is used for
Primary ModelRequired. Bulk ticket analysis, categorization and sentiment.
Secondary ModelTriage, incremental refresh and quick checks. A fast model suits it.
Reasoning ModelComplex planning and deep analysis.
Large Context ModelOperations over 200K tokens, such as memory analysis and profile generation. Leave it empty and QuantumOps chooses from your primary model. Only models with extended context are eligible.
Sanity Check Provider and Sanity Check ModelThe provider (OpenAI (GPT), Anthropic (Claude) or Together.ai) and model that cross-check results. Leave the model empty for the provider's default.

Providers

  • Anthropic (Claude) has a switch. The API Key is optional. Under Rate Limiting, set the Service Tier to match your Anthropic account: the choices run from Tier 1 - Free/Starter to Monthly Invoicing (Highest), and the line under the field shows the token and request limits QuantumOps will pace to. A tier higher than your account has makes requests fail when Anthropic's limit is reached. With managed AI, keep the preselected tier. Timeout (min) takes 1 to 15 minutes. Smart Queuing queues requests when a limit is hit and is recommended.
  • OpenAI is optional. Switch it on and enter an OpenAI API Key if you want GPT models as a fallback.
  • Together.ai is optional. Switch it on to use open-source models such as Llama, DeepSeek and Qwen. It needs your own Together.ai API Key. Token Cap/Min, Request Cap/Min and Timeout (min) set its limits.
  • Vector Store offers Managed Vector Store, which needs no configuration, and Managed Embeddings runs automatically. There is nothing to set.

Next needs a Primary Model and at least one provider switched on, and a key if you switched on Together.ai.

Later, change these settings in the AI Provider Configuration section of Tenant settings. AI providers and models explains the choices in depth.

Step 5: Q-Director Core

Step 5 sets the foundations. Every field starts with a working value, so you can continue without changing anything. Under most numeric fields the wizard prints a recommended value and the reason for it. Steps 5 to 7 use the same labels and the same choices as Q-Director Settings, so a setting reads the same on both screens.

  • Incremental Lifecycle Analysis. Enable incremental refreshes on ticket updates analyzes a ticket again when it changes, so insights stay current without running a full reprocessing job. When it is on you also see AI Model, which is your Secondary Model, Stale Recheck (hours), Scan Interval (mins) and Timeline Retention (days).
  • Ticket Categorization. Enable Q-Director ticket categorization lets AI assign categories. When to categorize chooses when: On Creation, On Closure or During Triage Assist. Allow Q-Director to create categories lets it create a category in HaloPSA when none of your existing ones fits, and Category Creation Mode chooses between Category Only, Resolution Category Only and Both. Recategorize ticket on closure and Set resolution category on closure update the category when a ticket is resolved.
  • Stale Ticket Detection. These settings decide when a ticket counts as stale, and they drive health scores and alerts.
    • Inactivity Threshold (business days) is the number of business days without activity, and Max Ticket Age (days) is the age after which a ticket counts as too old. Count business days only skips weekends and the public holidays of your organization's billing country. Inactivity Trigger chooses whose silence matters: No Agent Action, No User Action, No Any Action or Agent Awaiting Response.
    • Track Agent Follow-Up Requirements and Follow-up Required Within (days) flag tickets where an agent has not followed up in time.
    • Assignment Delay (hours) is how long an unassigned ticket can wait. SLA Hold Time Threshold (hours) is the threshold for tickets on SLA hold. Track SLA Breaches Separately treats a breach as more serious than staleness.
    • Enable AI Stale Analysis asks AI why a ticket is stale. Analysis Trigger chooses when: Incremental Refresh (recommended), Scheduled Only or Disabled. Min Hours Between Analysis sets the minimum gap between analyses of the same ticket.

Later, find these in Q-Director Settings: incremental refresh and stale detection on the AI Processing tab, categorization on the Classification tab. See Q-Director Settings, Q-Director: AI Processing, Q-Director: sentiment and categorization and Stale ticket detection, which also gives the default for each stale setting.

Step 6: Q-Director Automation

  • Triage Assist. Enable Q-Director Triage Assist gives dispatchers AI suggestions for routing and prioritization. Set Impact and Urgency during auto triage sits under it. It matters only when Auto triage and assign tickets is on: then QuantumOps writes the recommended impact and urgency when it triages a ticket. Otherwise dispatchers set them with Dispatch on the Ticket Triage Dashboard. On Autotask, which has no impact or urgency, the same switch is named Set Priority during auto triage and writes the recommended priority.
  • Research & Sherlock. Post Sherlock research results to ticket adds Sherlock's research findings to the ticket in HaloPSA as an action. It is a choice you make, so decide it deliberately. Use custom action filtering for AI analysis lets you list HaloPSA action outcomes to leave out of AI analysis in Excluded Outcomes (comma-separated), for example Rule Applied or SLA Hold. See Sherlock research and live context.
  • Triage Dashboard. Enable Triage Dashboard for dispatchers shows the triage dashboard's settings (duplicates, recurring incidents, feedback and display, which step 7 holds) in Q-Director Settings. It starts On. With it off, the Ticket Triage Dashboard that dispatchers open from a HaloPSA tab shows a notice that it is turned off instead of the triage view. See The Ticket Triage Dashboard and Q-Director: triage and routing.
  • Auto-Triage & Assignment. Auto triage and assign tickets starts Off. It has Auto triage after idle time (minutes), Schedule time zone and Triage outcome to use. In the wizard the outcome is the number of the HaloPSA action outcome that marks a ticket as triaged, and a ticket that carries it counts as triaged. QuantumOps's own triage action uses the outcome Q-Director Triage Assist. Q-Director Settings lets you pick the outcome by name instead of typing its number. The wizard does not ask for the business-hours schedule, the teams a ticket may be routed to or the target ticket types. Until you set the teams and the target ticket types in Q-Director Settings, switching the option on routes nothing. See what Auto triage and assign tickets does.
  • On-Call Notifications. Notify on-call staff of after hours tickets has a Notification method of PagerDuty, SMS or Email, and a target to match. SMS cannot be delivered yet because this instance has no SMS gateway, so choose PagerDuty or Email. The notice goes out for an after-hours ticket that auto triage handles, so it needs Auto triage and assign tickets to be on and set up. See what Auto triage and assign tickets does for what after hours means.
  • Escalation Paths. Define escalation schedule and path is a switch here. The detailed configuration is in Q-Director Settings after setup.

Leave auto-triage, on-call notifications and escalation paths off in a first setup, and read Q-Director: triage and routing before you switch any of them on.

Later, find these on the Triage & Routing tab of Q-Director Settings. Sherlock posting is on the Research & Docs tab, and custom action filtering is on the AI Processing tab.

Step 7: Q-Director Intelligence

  • Sentiment & Tonality Analysis. Sensitivity Level is Low, Medium or High: low gives fewer alerts, high is more vigilant. Sentiment Alert Threshold (1-10) and Tonality Alert Threshold (1-10) raise an alert when the score is at or below the number. Enable Feedback Buttons in Alerts adds feedback buttons to Slack and Teams alerts. Custom Analysis Instructions is optional text that tailors the analysis to your business. See Sentiment and tonality alerts.
  • Duplicate Detection. Detection Scope is Same Client, Same User or Global. Lookback Period (days) sets how far back to search, Status Filter chooses Only Open, Open & Closed or Open & Recently Closed, and Recently Closed Period appears for the last of those. Content Similarity Threshold is a slider. Enable subject line matching, Auto-flag high-confidence duplicates and Show merge button are checkboxes. Duplicate tickets and recurring issues explains the thresholds.
  • Recurring Incident Detection. Enable recurring incident detection has a threshold for User, Client and Global, and a Window (days).
  • ML Feedback & Learning. Track dispatcher corrections is the switch for the feedback loop that works from dispatcher corrections. Under it, Enable Manager Review asks for human approval before learned changes apply, and Min Corrections Before Retraining sets how many corrections to collect first. Changing Enable Manager Review here also sets manager review in the dispatcher workflow. See Dispatch workflow and scheduling settings. See Override and feedback review.
  • Dashboard Display Settings. Evaluation Mode is Quick, Deep or Auto. Auto-refresh (seconds) and Max Similar Tickets are numbers. Show agent workload indicators, Show client health & VIP indicators, Show ML priority score and Pre-generate AI predictions choose what the triage dashboard shows.
  • Dispatcher Workflow. Enable Dispatcher Workflow turns on dispatcher-focused scheduling, routing and guided work. Enable Appointment Scheduling and Enable Halo Color Sync are checkboxes, and color sync sets ticket colors in HaloPSA. Workflow Rollout Phase runs from Disabled through RecommendOnly, DispatcherApprovalRequired, ManagerApprovalRequiredForLearning and ColourSyncEnabled to AutoSchedulingEligible. Keep the switch off and the phase on Disabled until you are ready to roll the workflow out. See Dispatch workflow and scheduling settings.

Later, find sentiment on the Classification tab of Q-Director Settings, duplicates, recurring incidents, feedback and dashboard display on the Triage & Routing tab, and the dispatcher workflow on the Dispatch & Scheduling tab. The setup page for each is Q-Director: sentiment and categorization and Q-Director: triage and routing.

Web search lets AI look things up while it analyzes a ticket: error codes, documentation, known issues and unfamiliar technologies. Choose a Search Provider:

  • Tavily + Bing is the recommended managed service. It needs no setup.
  • Anthropic Web Search is Claude's own web search. It needs your own Anthropic API key with web search enabled on the account. Choosing it switches on Enable Anthropic Web Search and shows Max Searches Per Request (1 to 20, with 3 to 5 recommended), and the optional Allowed Domains and Blocked Domains, each a comma-separated list. Leave Allowed Domains empty to allow all domains.

Later, change these in Q-Director: web search.

Step 9: Customer Success

Customer Success monitors the health of your clients and tracks satisfaction surveys.

  • Enable Customer Success Dashboard switches the feature on. The options below appear once it is on.
  • Rating Scale is fixed: surveys are rated 1 to 5 with faces. You choose 3 or 5 faces later in CSAT Administration β†’ Survey Config.
  • Link Expiration (days) is how long a survey link keeps working.
  • Post CSAT Results as Private Actions adds feedback to the ticket as private notes that customers cannot see.
  • Alert Silence Duration (hours) is how long to silence an alert after someone acknowledges it.

Later, see Customer Success settings and CSAT Administration.

What comes next

Step 10 shows the addresses for your HaloPSA tabs. See Adding QuantumOps tabs to HaloPSA. Step 11 sets how far Ticket Autopilot may go; see The setup wizard. Step 12 reviews your choices and completes setup. See The setup wizard.