Setup Wizard

QuantumOps Setup Wizard

The QuantumOps setup wizard guides you through configuring your AI-powered MSP operations platform in 11 steps. Your progress is automatically saved, so you can leave and return at any time.

Estimated completion time: 15-20 minutes

[insert screenshot of Setup Wizard welcome screen here]

Before You Begin

Ensure you have the following ready before starting. See Review Prerequisites for detailed preparation instructions.

Required

Optional

Wizard Overview

The wizard consists of 11 steps organized into four phases:

Phase 1: Foundation

1. Welcome — Overview and prerequisites checklist
2. HaloPSA Connection — API credentials and webhook setup
3. Billing & Organization — Company info, spending limits, multi-user access

Phase 2: AI Configuration

4. AI Configuration — Model selection, provider settings, rate limiting

Phase 3: Q-Director Setup

5. Q-Director Core — Incremental analysis, categorization, stale detection
6. Q-Director Automation — Triage assist, auto-assignment, escalation
7. Q-Director Intelligence — Sentiment, duplicates, recurring patterns

Phase 4: Features & Launch

8. Web Search — Configure AI research capabilities
9. Customer Success — CSAT surveys and health monitoring
10. Dashboard Setup — HaloPSA iframe integration URLs
11. Import & Finalize — Data import options and launch

Step 1: Welcome

The welcome screen provides an overview of what you're about to configure and an interactive prerequisites checklist.

[insert screenshot of Welcome tab here]

What You'll See

• Setup time estimate: 15-20 minutes
• Auto-save confirmation: Your progress is saved automatically
• Prerequisites checklist: Click each item to mark it complete
• Quick tour option: Interactive walkthrough of the wizard

Prerequisites Checklist

The wizard displays six prerequisite items you can check off:

• HaloPSA Agent URL — Your HaloPSA instance URL
• HaloPSA Client ID — From your API application
• HaloPSA Client Secret — From your API application
• Webhook URL — Provided during setup for HaloPSA configuration
• Billing Information — Company details for invoicing
• AI API Keys — Optional, or use managed services

Click Let's Get Started to proceed.

Step 2: HaloPSA Connection

This step establishes the secure connection between QuantumOps and your HaloPSA instance.

[insert screenshot of HaloPSA Connection tab here]

API Credentials

Testing Your Connection

1. Enter all three credential fields
2. Click Test Connection
3. Wait 10-15 seconds for validation
4. Look for the green success indicator
   Connection Success Response:

✅ Connection Successful!
Successfully authenticated with HaloPSA.

Regional Settings

💡 Recommendation: Select Production unless you're specifically testing HaloPSA beta features.

Webhook Configuration

QuantumOps provides a custom automation runbook you'll configure in HaloPSA after completing the wizard.

Copy the Webhook URI — You'll need this for QuantumOps configuration:

https://[your-instance].halopsa.com/api/automation/[unique id]

Ticket Type Exclusions

Optionally exclude specific ticket types from AI processing. Common exclusions:

• Alerts/Informational — Automated maintenance tasks and alerts
• Internal — Internal team tickets
• Quotes — Quote and Opportunity tickets

ℹ️ Note: This selector only becomes available after a successful connection test.

Security Information

Your credentials are protected by:

• AES-256 encryption at rest
• Azure Key Vault for secret storage
• TLS 1.3 for all connections

Step 3: Billing & Organization

Configure your billing information, spending controls, and multi-user access settings.

[insert screenshot of Billing & Organization tab here]

Billing Information

Spending Controls

Set a monthly AI consumption limit to control costs (if desired):

💡 Tip: Most MSPs processing 50-200 tickets/day consume $250-500/month in AI costs depending on feature set enabled.

Display Preferences

Time Zone — All timestamps in QuantumOps will display in your selected time zone. This affects:

• Ticket activity times
• Alert timestamps
• Report generation
• Dashboard displays

Multi-User Access

Toggle Enable Multi-User Access to allow team collaboration:

When Enabled:

• Organization Name field appears (required) — This is the public-facing name shown on login screens and within the application. It can differ from your billing name (e.g., "Acme IT Solutions" vs. "Acme IT Solutions LLC").
• Invite Team Members button becomes available
• Team members can access the entire QuantumOps management console
• Role-based access controls become available in Q1 2026

Inviting Team Members

With multi-user enabled, click Invite to send email invitations:

1. Enter colleague's email address
2. Click Send Invitation
3. Invitee receives email with setup instructions
4. They'll appear in the Team Members list once registered

Step 4: AI Configuration

Configure your AI providers, model preferences, and rate limiting settings.

[insert screenshot of AI Configuration tab here]

Primary AI Model

The primary model handles the bulk of platform usage—ticket analysis, summarization, and reasoning tasks.

⭐ Recommended: Claude 4.5 Sonnet offers the best cost-performance ratio for MSP ticket analysis, plus the highest performance and a 1M token context window that some functions in the application depend on (especially for large MSPs). Not using Claude 4.5 Sonnet or a 1M token context window model as your primary AI model will prevent large batch operations from being as efficient. This primarily applies to large semantic memory or profile generation tasks for large MSPs that sometimes exceed the standard 200k token context window due to the number of semantic memories and interactions that need to be consolidated or analyzed. Since queries in excess of 200k tokens cost double per token after 200k, QuantumOps only uses 1M token context for those explicitly large tasks, and only after determining a token context window will be exceeded or has been exceeded while attempting a cheaper approach.

Secondary AI Model (Fast)

The secondary model handles lightweight, incremental tasks that don't require complex reasoning—such as updating analysis or trajectories when a user or agent emails on a ticket, and performing sentiment/tonality analysis.

⭐ Recommended: Claude 4.5 Haiku provides the speed, efficiency, and accuracy needed for high-frequency incremental refreshes at minimal cost.

Orchestration AI Model

The orchestration model handles complex chat queries and guides responses from Qubit. This model sees minimal usage but requires advanced reasoning and tool-use capabilities when invoked.

⭐ Recommended: Claude 4.5 Opus provides the highest reasoning capability for orchestrating complex tasks and guiding nuanced responses at a competitive cost and speed.

Anthropic (Claude) Configuration

Toggle Enable Anthropic to configure Claude models.

API Key Options:

• Leave empty → Use QuantumOps managed service (recommended)
• Enter your key → Bring Your Own Key for direct billing

Rate Limiting Configuration:

Service Tier Defaults:

OpenAI Configuration

Toggle Enable OpenAI to configure GPT models.

API Key:

• Required for BYOK
• Leave empty to use managed service

Managed vs. BYOK Comparison

Step 5: Q-Director Core

Configure foundational AI features including real-time analysis, categorization, and stale detection.

[insert screenshot of Q-Director Core tab here]

Incremental Lifecycle Analysis

When enabled, QuantumOps analyzes tickets automatically as they're created and updated via webhooks—no manual refresh required.

Ticket Categorization

Q-Director can automatically assign categories based on ticket content:

💡 Recommendation: Start with OnCreation timing and Allow Category Creation enabled. This lets Q-Director learn your patterns while providing immediate value.

Stale Ticket Detection

Configure when tickets are flagged as "stale" and require attention:

Inactivity Thresholds:

Assignment & SLA Settings:

Health Score Penalties:

Stale conditions apply penalties to ticket health scores:

Step 6: Q-Director Automation

Configure automated ticket handling, routing, and escalation workflows.

[insert screenshot of Q-Director Automation tab here]

Triage Assist

When enabled, Q-Director provides AI-powered triage suggestions:

Toggle Set Impact & Urgency During Triage to have Q-Director automatically set these values based on ticket content analysis.

Auto-Triage & Assignment

Automatically triage and assign tickets that remain idle:

💡 Recommendation: Start with 30-minute idle time and monitor before reducing. Set to 15 minutes for urgent ticket types.

Research & Sherlock

Configure how AI research results are handled:

On-Call Notifications

Alert staff for tickets arriving outside business hours:

Exclude Clients from Notifications — Comma-separated list of clients that shouldn't trigger on-call alerts.

Escalation Paths

Configure automatic escalation workflows for specific conditions. Escalation rules can trigger based on:

• Ticket age
• Priority level
• Client importance
• SLA proximity

Step 7: Q-Director Intelligence

Configure advanced AI analysis features including sentiment detection, duplicate identification, and pattern recognition.

[insert screenshot of Q-Director Intelligence tab here]

Sentiment & Tonality Analysis

Detect customer emotional state and communication tone:

Custom Instructions — Add business-specific guidance for sentiment analysis:

Ignore standard support frustration. Focus on:
- Threats to cancel service
- Mentions of competitor evaluation
- Executive involvement signals

Duplicate Detection

Automatically identify similar tickets to reduce redundant work:

Recurring Incident Detection

Identify patterns of repeated issues across users, clients, and globally:

ML Feedback Loop

Train Q-Director from corrections:

Step 8: Web Search Configuration

Configure AI-powered web research for ticket analysis.

[insert screenshot of Web Search tab here]

Provider Options

Tavily + Bing (Recommended)

Automatically configured with:

• Pre-configured domain prioritization for tech documentation
• Automatic result filtering for relevance
• Integration with ticket context for better results
• No additional configuration required

Anthropic Web Search

When selected, configure:

Example Domain Configuration:

Allowed: microsoft.com, docs.microsoft.com, stackoverflow.com
Blocked: facebook.com, twitter.com, pinterest.com

When Web Search is Used

The AI automatically triggers web search when:

• Looking up error codes
• Finding vendor documentation
• Researching known issues
• Encountering unfamiliar technologies

Step 9: Customer Success Configuration

Configure proactive customer success monitoring and CSAT surveys.

[insert screenshot of Customer Success tab here]

Customer Success Dashboard

Toggle Enable Customer Success Dashboard to activate:

• Client health score tracking
• Sentiment trend monitoring
• At-risk client alerts
• CSAT tracking
• Response time monitoring
• Success reports

CSAT Survey Configuration

Alert Settings

Step 10: Dashboard Setup

Configure QuantumOps dashboards as iframe tabs within HaloPSA.

[insert screenshot of Dashboard Setup tab here]

Available Dashboards

How to Add Dashboards to HaloPSA

1. Log into HaloPSA as administrator
2. Navigate to Configuration → Custom Objects → Custom Tabs
3. Select the entity type (Ticket or Client)
4. Click New → Set Type to iFrame
5. Paste the URL from the wizard and save

Dashboard URLs

Each dashboard provides a URL with HaloPSA placeholders:

https://[your-instance].qops.app/TicketDashboard/[your-tenant-id]/$FAULTID?agentid=$agentid&agentname=$agentname
https://[your-instance].qops.app/TicketTriageDashboard/[your-tenant-id]/$FAULTID?agentid=$agentid&agentname=$agentname
https://[your-instance].qops.app/ClientDashboard/[your-tenant-id]/$CLIENT_ID
https://[your-instance].qops.app/InteractiveGuide/[your-tenant-id]/$FAULTID?agentid=$agentid&agentname=$agentname

The ${id} placeholder is automatically replaced by HaloPSA with the ticket or client ID.

Recommended Tab Order

For Incident/Service Request Tickets:

1. Ticket Dashboard
2. Agent Assist
3. Progress (HaloPSA native)

For Intake/Triage Ticket Types:

1. Triage Dashboard
2. Agent Assist
3. Progress (HaloPSA native)

ℹ️ Note: Dashboard configuration can be completed after the wizard. URLs are also available in Q-Director Settings.

Step 11: Import & Finalize

Import historical data and launch your QuantumOps instance.

[insert screenshot of Import & Finalize tab here]

Data Import Options

Import Agents (Required)

Syncs your HaloPSA agents into QuantumOps for:

• Intelligent routing suggestions
• Workload balancing
• Performance tracking
• Skill matrix population

Import Historical Tickets (Optional)

Imports past tickets to:

• Train AI on your resolution patterns
• Enable similar ticket matching
• Populate semantic memory
• Build client/user profiles

💡 Recommendation: Start with 90 days of import only. The import screen allows you to estimate what this training will cost and set a maximum spend for training.

Setup Summary

Before completing, review your configuration:

Completing Setup

Click Complete Setup & Launch to:

1. Save all configuration
2. Start selected data imports
3. Redirect to main dashboard

Troubleshooting

Connection Test Fails

"Invalid Client ID or Secret"

• Verify exact values from HaloPSA
• Check for extra spaces
• Ensure API application is enabled

"URL not found"

• Remove https:// prefix
• Verify HaloPSA instance is accessible
• Check for typos

"Permission denied"

• Ensure API application has required permissions
• Verify admin:all permission is granted
• Check if API application is disabled

Webhook Not Receiving Events

1. Verify webhook URL is exactly as provided
2. Check HaloPSA webhook is enabled
3. Confirm events are selected (Created, Updated, Action Added)
4. Test with a manual ticket update

AI Processing Not Starting

1. Verify AI provider is configured (managed or BYOK)
2. Check API key validity if using BYOK
3. Review rate limiting settings
4. Check consumption limit hasn't been reached

Next Steps

• Initial Training / Data Import — Initial training and data import

Related Documentation

• Setup Wizard — Initial QuantumOps configuration
• Review Prerequisites — Prerequisites and preparation