# ResultsIQ > ResultsIQ Control Center is a platform built for managed service providers (MSPs). It lets an MSP scope, price, build and bill AI managed services across the clients it already has, and gives the MSP’s team Control Center MCP, one connection to every client and every tool it runs. ResultsIQ sells only to MSPs, never to their clients. ## Key facts - Price: $1,750 a month for the platform, plus $75 a month for each billable workflow (a workflow the MSP bills a client for). No cost for the first 90 days. No fees per seat, per user, per client or per device. - The 90 days: they cost nothing, so an MSP starts ROI positive before it spends anything on AI. The suggested path is days 1–45 inside the MSP’s own business and days 46–90 with its first client, but the MSP can use the 90 days however it wants. The first ResultsIQ invoice comes on day 91. - After day 90: an annual contract with a 30-day notice period. An MSP that decides it isn’t a fit walks away by day 90 and owes nothing. - Control Center MCP, included in the platform price: the MSP’s team connects Claude or ChatGPT once and reaches every client tenant and connected tool, with the same roles and client scopes as the login. The team uses it for service delivery, automations and reports; it drafts automations that a person approves before they run. MCP as a service for the MSP’s clients is planned for Q2 2027. - The MSP brings its own AI provider account and keys. ResultsIQ adds no markup on AI usage. - Hosted by ResultsIQ in Microsoft Azure, isolated per tenant. SOC 2 Type I is in progress, with a target of Q1 2027. - Availability: ResultsIQ is running pilots with select MSPs and starts reaching out to the waitlist in Q1 2027. Book a call at https://www.resultsiq.ai/demo/ or join the waitlist at https://www.resultsiq.ai/waitlist/. - Built by Connor Reece, President and CEO of Reboot, the MSP his father started in 2005. ## Every page, in full --- Page: https://www.resultsiq.ai/ For managed service providers # Turn every client into AI MRR. ResultsIQ Control Center lets MSPs scope, price, build and bill AI managed services for the clients they already have. [Book a call](https://www.resultsiq.ai/demo/?src=home) [Build your AI plan 5 min](https://www.resultsiq.ai/integrations/) Example, one client (Northbridge Insurance). They ask: "Do we need an AI policy?" "Is our data safe in ChatGPT?" "Where would AI actually save us money?" "What should we do first?" "Can you just run it for us?" You answer with one managed service on their monthly invoice: AI managed services, $2,500 a month. It includes AI policy and governance, approved AI tools and data protection, an AI opportunity assessment, an AI roadmap reviewed every QBR, and managed AI automations built for their tools and processes. Delivered and billed in Control Center. Works with 156 tools your MSP already runs. Click yours to start your AI plan, or [see them all](https://www.resultsiq.ai/integrations/). Control Center connects to 156 MSP tools through their public APIs, including NinjaOne, ConnectWise PSA, Microsoft 365, Datto RMM, Autotask PSA, SentinelOne, IT Glue, HaloPSA, Huntress and Veeam, plus anything with a documented REST API. What it’s worth ## What’s AI MRR worth to your MSP? Update the calculator below to see how much profit this puts in your pocket. The calculator multiplies four inputs. At its defaults (40 clients, 40% of them buy, 3 billable workflows each, $2,500 a month per client): AI revenue is 16 clients × $2,500 a month × 12 = $480,000 a year. Gross profit is $480,000 × 70% margin, less $64,200 of ResultsIQ fees ($1,750 a month, plus $75 a month for each of 48 billable workflows) = $271,800 a year. At 8 times yearly profit, the multiple a buyer pays for recurring profit, that adds $2.17M to what the MSP sells for. This is the AI line on its own. Year one bills about half of it, because adoption starts at zero. The full three-year picture is in [The No Brainer](https://www.resultsiq.ai/no-brainer/) Capabilities ## Everything your MSP runs on, in one platform. AI managed services are where it starts. Pick any capability to see it in detail. [### Client business context Every client’s business documented and kept current. Every answer starts from it.](https://www.resultsiq.ai/capabilities/#c-doc) [### AI managed services Find, value, price, build and bill AI services for every client.](https://www.resultsiq.ai/capabilities/#c-rev) [### Automation Build a workflow once and run it for every client, with approvals and a run log.](https://www.resultsiq.ai/capabilities/#c-auto) [### Technology standards Your standard on every client, checked every morning, with drift flagged.](https://www.resultsiq.ai/capabilities/#c-std) [### Reports and QBRs Reports and QBRs from live data, in each client’s terms, on demand.](https://www.resultsiq.ai/capabilities/#c-rep) [### Roadmaps and budgets A priced roadmap and budget for every client, refreshed every QBR.](https://www.resultsiq.ai/capabilities/#c-road) [### Billing and AI margin Every AI run metered and priced, billed through your PSA at your margin.](https://www.resultsiq.ai/capabilities/#c-cost) [### Control Center MCP Your team’s AI on every client, every tool and every API.](https://www.resultsiq.ai/mcp/) [### Security and governance Role-based access, approvals and an audit trail for every AI run.](https://www.resultsiq.ai/capabilities/#c-sec) [See every capability](https://www.resultsiq.ai/capabilities/) Control Center MCP ## Every tech covers more. Every endpoint costs less. Labor is an MSP’s biggest cost. Connect your team’s AI to Control Center once, and every person reaches every client, every tool and each client’s business. Your cost to deliver drops, so you keep more margin or price to win. Modeled example: 12 technicians supporting 2,000 endpoints, each getting 5 hours back a week. Endpoints each tech supports go from 167 to 190 (+14%). Labor cost per endpoint goes from $40 to $35 a month. Keep your price and that is $120,000 a year in margin, or price to win at $5 less per endpoint with the same margin. Assumes $80,000 loaded cost per technician, 48 working weeks and 1,920 hours per full-time person. ### An EDR that understands the business. An RMM that does too. Control Center builds a context graph of each client: every device, account, site and alert, joined to their people and how their business runs. Every alert, answer and report your team gets carries it. For example, the EDR says "Suspicious PowerShell on NB-LT-0142." With business context, your team sees: it's the underwriting manager's laptop, in renewal season, so isolate it, then call her. The RMM says "Disk 94% full on NB-FS01." Your team sees: it's where the claims team scans, and full by Friday means late claims, so fix it today. Microsoft 365 says "MFA is off for 2 accounts." Your team sees: both people approve wire transfers, Northbridge's top risk, and a ticket is opened. Network monitoring says "Packet loss on the Tampa office link." Your team sees: Tampa's agents quote by phone all day, so fail over to the backup line before 9 a.m. Microsoft Entra says "Impossible-travel sign-in for m.chen." Your team sees: it's the controller, two days before payroll, so lock the account and verify by phone. If there's a path to the data, your team can use it. ### The same context, at every desk. Everything is mapped together into one on-demand record of each client: their technology, their people and how their business runs. No gaps, nothing out of reach, and every answer in terms the client understands. Service desk engineer Responding to a ticket or an alert Laptop NB-LT-0142 Underwriting manager Renewal season Her laptop, in renewal season. It’s priority one: call her before you isolate it. Technology standards engineer Keeping every tool deployed to standard 2 accounts without MFA Finance Approves wires Those two accounts approve wire transfers. They go to the top of the list. vCIO Selling the next project to the decision maker Tampa office link Sales agents Quotes by phone Tampa’s agents quote by phone all day. A second line keeps them selling when this one drops. ### Ask it. Automate it. Report on it. - Ask about any client, across every tool. Every answer names its source. - Automate what you just did, as a skill in your AI or a workflow that runs for every client. - Report in each client’s terms: QBRs, alignment, patch status. Same roles and client scopes as the login, and a person approves before anything runs. Claude and ChatGPT at launch, included in the platform price. Service desk Which clients have laptops missing the DNS roaming agent? 7 laptops at 3 clients: Northbridge Insurance (4), Golden Gate Insurance (2), Northwind Manufacturing (1). Want a ticket opened for each? Source: RMM and DNS filter, live Service desk Check for that every morning, for every client. Done. It’s saved as a skill in your AI and as a workflow that runs at 6 a.m. for every client and opens the ticket. It’s waiting for your approval. Source: Workflow Studio vCIO Draft the QBR summary for Northbridge Insurance. Drafted in Northbridge’s terms: both people who approve wires now use MFA, and the claims server was fixed before it filled. It’s in QBR Studio for your review. Source: QBR Studio You’re not just an MSP anymore. You’re the data and information company for every client you manage. [See Control Center MCP](https://www.resultsiq.ai/mcp/) Who uses it ## The automation layer for every team in your MSP. Each team does its job in less time and takes on more, with their AI on every client and reports on demand. Service desk. Today: Triage and route every ticket by hand. With Control Center: Triaged, enriched and routed before a tech opens it (automated). Today: Search five tools for context. With Control Center: Ask about the user, the device and the client in one place (mcp). Today: Fix the same issue, client by client. With Control Center: Fix it once, run it for every client (automated). Ask it: "Who at Northbridge is affected by this outage, and what are they working on today?" Technology standards. Today: Audit each client by hand, once a quarter. With Control Center: Every client checked against your standard every morning (automated). Today: Dig through tools to find why a setting drifted. With Control Center: Ask which clients drifted, and why (mcp). Today: Write the alignment report. With Control Center: A client-ready standards report, on demand (on-demand report). Ask it: "Which clients drifted from our Microsoft 365 standard this week, and why?" vCIO & account management. Today: Gather data from every tool for each QBR. With Control Center: The QBR drafted from live data in minutes (on-demand report). Today: Build roadmaps and budgets in spreadsheets. With Control Center: A priced roadmap and budget for every client (on-demand report). Today: Explain risk in technical terms. With Control Center: Explain it in the client’s business terms (mcp). Ask it: "What should Northbridge budget for next year, and what does each item protect?" Centralized services. Today: Rebuild the same automation for each client. With Control Center: Build it once, publish it to every client (automated). Today: Write and test scripts tenant by tenant. With Control Center: Scripts drafted by your AI, tested on live data (mcp). Today: Piece together what ran where. With Control Center: Every run logged, with its cost (on-demand report). Ask it: "Draft a script that clears stuck print queues on every client’s file servers." Professional services. Today: Discover scope on the clock. With Control Center: Scope from the documented business, before the SOW (mcp). Today: Specify the build twice. With Control Center: Build from the approved blueprint (automated). Today: Find the project margin after the fact. With Control Center: Cost and margin known before you quote (on-demand report). Ask it: "Which systems does Northbridge’s claims team use, and who owns each one?" Sales & marketing. Today: Pitch projects one at a time. With Control Center: A queue of priced AI opportunities across every client (on-demand report). Today: Pitch AI in general terms. With Control Center: Pitch from each client’s own documented business (mcp). Today: Write every proposal from scratch. With Control Center: Proposals built from the client’s roadmap (automated). Ask it: "Which clients are ready for an AI automation proposal this quarter?" Compliance & risk. Today: Can’t say what the AI touched. With Control Center: Every run logged: what ran, what it cost, who approved it (on-demand report). Today: An AI policy written once and never checked. With Control Center: The AI policy applied and monitored for every client (automated). Today: Weeks of audit prep. With Control Center: Audit evidence on demand (on-demand report). Ask it: "Show every AI action on Northbridge’s data this month, and who approved it." Finance & accounting. Today: AI usage costs show up as a surprise. With Control Center: Every run metered and priced (automated). Today: Margin found at year end. With Control Center: Margin per client and per workflow, every month (on-demand report). Today: Invoices built by hand. With Control Center: Invoice lines sync to your PSA (automated). Ask it: "What was our AI margin by client last month?" Why us ## Why not just use…? Everything else does part of the job. We haven’t found anything that does all of it, or anything built only for MSPs. Compared by category. AI assistants give faster answers but nothing to sell. Automation platforms run workflows but don't find, value, price or bill them. AI features in a PSA or RMM help inside that one tool. Building it yourself means five products to build and keep running. Control Center finds the AI work at each client, values and prices it at your margin, builds and runs it in every client's tenant, meters every run and bills it through your PSA, connects your team's AI to every client and tool, and is built only for MSPs. ### Why not just give our team an AI assistant? Keep it, and connect it to Control Center. On its own, an assistant makes your team faster. It doesn’t give you anything to sell, price or bill. ### Why not an automation platform? It runs workflows. It doesn’t find the work at each client, put a value on it, price it or bill it. That’s most of the job. ### Why not the AI features in our PSA or RMM? They work inside that one tool. Control Center works across all of your tools, adds each client’s business context and turns the result into a service you bill. ### Why not hire an AI consultant? A consultant bills hours and leaves with the knowledge. Control Center keeps the work inside your MSP, priced and recurring, for every client. ### Why not build it ourselves? You’d be building five products and a spreadsheet to hold them together. We know, because we did it first. Ours is $1,750 a month, and the first 90 days cost nothing. Built for MSPs ## One industry. One customer. One purpose. Control Center is built only for MSPs, by MSP operators, to help you succeed and scale. Nothing in it was built for anyone else. The numbers you run your MSP on MRR AI managed services on every client Gross margin Every service priced at the margin you set Endpoints per tech Your team’s AI on every client and tool Cost per endpoint Less labor in every ticket, alert and report Revenue per employee More revenue from the same team What a buyer pays More recurring profit, which is what buyers pay for [Score my MSP on these numbers](https://www.resultsiq.ai/score/) Only for MSPs - We sell only to MSPs. Never to your clients. The client relationship is yours. - Your own AI account and keys. We take no spread on your AI spend. - Your data stays yours. Yours and your clients’, whether you stay or not. - Every AI run is metered and logged. What ran, what it cost, who approved it. - SOC 2 Type I in progress. Target Q1 2027. [Where we stand](https://www.resultsiq.ai/security/) 90 days ## Start ROI positive. First 90 days, no cost. Run it in your own MSP first. You’re ROI positive before you pay us anything. [Book a call](https://www.resultsiq.ai/demo/?src=home) [Join the waitlist](https://www.resultsiq.ai/waitlist/) You won’t need a card, a contract or a procurement cycle. --- Page: https://www.resultsiq.ai/capabilities/ Capabilities # Everything Control Center does for your MSP. What each capability does for your business, and a picture of how it does it. Comparing tools? [See our guide to AI tools for MSPs.](https://www.resultsiq.ai/ai-tools-for-msps/) Client business context ## Your whole team knows every client’s business. - Techs work every ticket with the client’s business in view. - No interviews to run and no wiki to keep current. - New AI opportunities show up on their own. How it works: Control Center reads each client's apps and maps how their business runs, then every desk in your MSP works from that one record. AI managed services ## AI does 90% of the work. You approve it and bill it. - AI finds, values, prices, builds and bills each service. - Your team makes one decision: approve it. - New recurring revenue on every client, at your margin. How it works: AI finds the opportunity, values it, prices it, builds it and bills it. The MSP approves it once. Automation ## Automate the work once, for every client. - Build it once and sell it to every client. - No automation engineer to hire. - Tested on live data before any client sees it. How it works: Describe the job in plain English, AI drafts the workflow, it is tested on live data, and every client gets it. Technology standards ## Catch drift before it turns into a ticket. - Problems get fixed before the client calls. - Junior engineers deliver like your senior ones. - Every gap becomes a project you can sell. How it works: Your standard is checked against every client each morning. Drift becomes a ticket you fix today or a project you sell. Reports and QBRs ## Your vCIO walks into every QBR ready to sell the next project. - QBRs ready in minutes, not days. - Every client gets one, every quarter. - Risks explained in business terms, with the fix priced. How it works: Live data from every tool and the client's business context become a QBR in their terms. Your vCIO approves it and sells the next project. Roadmaps and budgets ## Sell a plan, not one project at a time. - A 12-month plan and budget for every client. - Clients see every cost coming. - AI spend alerts at 80%, and runs never stop. How it works: Approved work goes on a dated roadmap and a 12-month budget, and AI spend is tracked against the budget you sold. Billing and AI margin ## Get paid for every AI run, at the margin you set. - AI services bill themselves, with zero labor hours. - See the margin on every client and every workflow. - Waste is found and fixed, so your margin grows. How it works: Every AI run is metered. Your cost plus your margin sets the price, and the line lands on the invoice in your PSA. Control Center MCP ## Every tech gets an assistant that knows every client. - Answers about any client, across every tool, in seconds. - Any answer can become an automation. - Same permissions as the login, and a person approves every action. [See Control Center MCP](https://www.resultsiq.ai/mcp/) How it works: Your tech asks in Claude or ChatGPT. Control Center MCP checks their role and clients, reaches every tool and answers with the source. Security and governance ## Say yes to the clients who ask hard questions about AI. - Your AI account and keys, and nothing trains on client data. - You decide exactly what AI can touch. - An audit trail for every action, ready for any auditor. [See how we handle security](https://www.resultsiq.ai/security/) How it works: An AI agent asks to act, your policy decides, a person approves anything risky, and every action is logged with its cost. ### See it on an MSP like yours. Thirty minutes, the live product, whichever of these you want opened first. [Book a call](https://www.resultsiq.ai/demo/?src=capabilities) [Join the waitlist](https://www.resultsiq.ai/waitlist/) --- Page: https://www.resultsiq.ai/mcp/ Control Center MCP # Give everyone at your MSP an AI that knows your clients. Your team asks Claude or ChatGPT. It answers from your PSA, RMM and Microsoft 365 in seconds, then does the work. [Book a call](https://www.resultsiq.ai/demo/?src=mcp) [Join the waitlist](https://www.resultsiq.ai/waitlist/) Included In the $1,750 platform price, with nothing per seat 156 MSP tools it connects to, plus any REST API Q2 2027 MCP as a service, so you can provide it to your clients Why it matters ## Every tech does more. Every client notices. For you +$120,000 a year in margin ### More margin from the same team. Modeled: 12 techs, 5 hours back each a week. For your team Why is Kelly locked out? ### One question, not five tools. For your clients Ticket #48127 New Fixed Kelly keeps getting locked out J Jordan, Service Desk ### Fixed on the first call. Try it ## Pick a role. Watch it work. Example conversations in Claude or ChatGPT with Control Center connected, one for each role in Control Center, shown with an example stack: ConnectWise PSA, NinjaOne, SentinelOne, Microsoft 365, IT Glue, Datto BCDR, Avanan, Cisco Meraki, QuickBooks Online and KnowBe4. ### Owner/Admin You, Owner/Admin: everything, every client. You ask: "Which clients are eating our margin?" It uses ConnectWise PSA: Time entries this quarter, all 42 clients; ConnectWise PSA: Agreements and what each client pays. The answer: Two clients are well under your $125-an-hour target this quarter: Northwind Manufacturing, 210 hours on $4,200 a month, $60 an hour. Ridgeline Builders, 96 hours on $2,100 a month, $66 an hour. At Northwind, 61% of those hours went to one old ERP server. You ask: "What would fix Northwind?" It uses NinjaOne: NW-ERP-01: age, warranty and alerts; Control Center: Northwind’s roadmap. The answer: Moving that server to Azure. It’s 7 years old, out of warranty, and behind most of their tickets. I added the move to Northwind’s roadmap at $14,800, so Morgan can take it to their QBR on November 18. ### vCIO Morgan, vCIO: their 9 accounts, including what each pays. Morgan asks: "Get me ready for Thursday’s QBR with Meridian Health." It uses ConnectWise PSA: Meridian’s tickets this quarter; NinjaOne: Their 58 devices; Microsoft 365: Users, MFA and licenses; Control Center: Their business and AI workflows. The answer: Here’s Meridian Health’s quarter: Tickets, 94, down 18%, Most were printers at the Eastside clinic. Security, MFA on for all 64 users, 1 laptop without SentinelOne. Lifecycle, 9 laptops out of warranty by March, About $11,700 to replace. AI, 2 workflows live, 41 hours of front-desk time saved. Two things to bring them: a plan for the 9 laptops, and a fix for the Eastside printers. Morgan asks: "Put that in the QBR deck." It uses Control Center: QBR Studio: Meridian Health, Q4. The answer: Done. Meridian Health’s QBR is drafted in QBR Studio with these numbers and both recommendations, ready for you to review before Thursday. ### Centralized Services Sam, Centralized Services engineer: all 42 clients, no prices or margins. Sam asks: "Which servers missed last night’s backup, and why?" It uses Datto BCDR: Last night’s jobs, all 42 clients; NinjaOne: Disk space and agent status. The answer: 5 servers at 3 clients: Harbor Dental, 2 servers, Backup drive 98% full. Northbridge Insurance, 2 servers, Job timed out at 2:14 a.m. Ridgeline Builders, 1 server, Agent offline since Tuesday. Harbor Dental’s drive fills up every week: it keeps 90 days of backups on a 2 TB drive. Sam asks: "Open a ticket for each, and check this every morning from now on." It uses ConnectWise PSA: 3 new tickets; Control Center: A new automation: morning backup check. The answer: Opened 3 tickets in ConnectWise PSA, one per client, with the job logs attached. I also built a morning backup check for all 42 clients. It ran clean on last night’s data, so you can release it when you’re ready. ### Service Desk Jordan, Service Desk: their 14 clients, no billing. Jordan asks: "Kelly Brooks at Northbridge keeps getting locked out. What’s going on?" It uses Microsoft 365: Kelly’s sign-ins this week; ConnectWise PSA: Kelly’s tickets; NinjaOne: Her laptop, NB-LT-114. The answer: Her password was changed on Monday (ticket #48120), but the mail app on her iPhone still has the old one. It has tried 46 times since, and that’s what keeps locking her out. Her laptop is fine. The fix: update the password in her iPhone’s mail settings. It takes about two minutes. Jordan asks: "Put that in her ticket." It uses ConnectWise PSA: Ticket #48127. The answer: Done. The cause and the fix are in ticket #48127 in ConnectWise PSA, and it’s set to Waiting on Client. ### Billing Riley, Billing: invoices, agreements and margins, builds nothing. Riley asks: "Which clients have more Microsoft 365 licenses than we bill for?" It uses Microsoft 365: Licenses at all 42 clients; ConnectWise PSA: Agreements at all 42 clients. The answer: 4 clients use 23 more licenses than their agreements bill, about $650 a month: Golden Gate Insurance, 9 unbilled, Business Premium. Northwind Manufacturing, 7 unbilled, Business Standard. Summit Legal Group, 4 unbilled, Business Premium. Ridgeline Builders, 3 unbilled, E3. Riley asks: "Add them to the agreements so they bill on the next invoice." It uses ConnectWise PSA: 4 agreements. The answer: Done. The 23 licenses are on the 4 agreements in ConnectWise PSA, so they bill on the November 1 invoices: about $650 a month more. One connection ## One connection to every tool you run, for every client. Connect Claude or ChatGPT to Control Center once. It reaches the tools you already use, and checks every question against the person’s role and clients. Your team's Claude or ChatGPT connects to Control Center's MCP server once. Every question is checked against the person's role and assigned clients, and logged. From there it reaches the tools the MSP already uses, for every client: the PSA (tickets, agreements and time), the RMM (devices, patches and alerts), Microsoft 365 (users, licenses and sign-ins), endpoint security, backup, documentation and the rest, 156 tools in all, plus any REST API. Other MCP connectors give your AI one company’s apps. This gives it every client you manage. MCP as a service, from Q2 2027 ## Then sell it to your clients. Their AI and their apps, with your name on it. Billed monthly, like any managed service. From Q2 2027, MCP as a service: each client's people use the Claude or ChatGPT they already pay for, connected through the MSP to their own apps (for an insurance agency: Applied Epic, Microsoft 365, QuickBooks Online and the rest), with the MSP's name on it and the access the MSP sets. The MSP bills it every month, like any managed service. FAQ ## Questions MSP owners ask about it. ### What is MCP? The Model Context Protocol, the open standard Claude and ChatGPT use to work with other software. Control Center runs an MCP server, so your team’s AI can use your clients’ tools the way your team does. ### Which AI does it work with? Claude and ChatGPT at launch, on your own AI account at your own rate. We don’t mark it up. ### What does it cost? It’s included in Control Center’s $1,750 a month, with nothing per seat or per technician. ### Can every technician see every client? No. Each person signs in with their role from Control Center and sees only their clients and what that role allows. Service Desk and Engineers never see prices or margins. ### Can it change things in our tools? Only the actions an Owner or Admin turns on for each tool, with MFA, and only for roles allowed to use them. Every action is logged with who asked for it. ### Where do the passwords and API keys live? In Control Center’s vault. The AI never sees a password or API key, and nothing is pasted into the chat. ### Does it train on our data? No. Your clients’ data is never used to train a model or improve anything outside your tenant. ### Can our clients use it? Yes, from Q2 2027, as MCP as a service. You connect each client’s Claude or ChatGPT to their own apps, with your name on it and the access you set, and bill it monthly. Until then, it’s for your own team. ### Put your team’s AI to work on every client. Included in the platform price. We start reaching out to the waitlist in Q1 2027. [Book a call](https://www.resultsiq.ai/demo/?src=mcp) [Join the waitlist](https://www.resultsiq.ai/waitlist/) --- Page: https://www.resultsiq.ai/integrations/ Your AI plan # Your MSP’s AI plan in five minutes. Pick the tools your MSP runs. See what to automate in your own shop, what to sell every client, and what it’s worth each month. Then copy it, save it as a PDF or share it with your team. Pick your tools If it has an open API, it connects: 156 MSP tools today. [API docs and requirements for every tool](https://www.resultsiq.ai/docs/tools/) ## Pick your tools. Pick the tools your MSP runs. Control Center connects to each one through its API and shows what they can do together. If a tool has a documented API and is not listed, it can still be connected. PSA: ConnectWise PSA, Autotask PSA, HaloPSA, Kaseya BMS, Syncro, SuperOps, Atera, Accelo, ServiceNow, Freshservice, Zendesk, Jira Service Management. RMM: Syncro, SuperOps, Atera, NinjaOne, Datto RMM, ConnectWise Automate, ConnectWise RMM, Kaseya VSA, N-able N-central, N-able N-sight, Level, Action1, Pulseway, ImmyBot, Automox, Microsoft Intune. Endpoint security: SentinelOne, CrowdStrike Falcon, Huntress, Microsoft Defender for Endpoint, Sophos Central, Bitdefender GravityZone, ESET PROTECT, ThreatDown, Webroot, Blackpoint Cyber, Arctic Wolf, Cynet, Datto EDR, Todyl. SIEM and managed SOC: Microsoft Sentinel, Blumira, Stellar Cyber, RocketCyber, N-able Adlumin, Rapid7 InsightIDR, Splunk, Elastic Security, Sumo Logic, Exabeam, LogRhythm, Fortinet FortiSIEM, Coro, Wazuh, SaaS Alerts, Field Effect MDR, ConnectWise SIEM, Barracuda XDR. Email security: Avanan, Mimecast, IRONSCALES, Abnormal, Proofpoint, Proofpoint Essentials, Material Security, Barracuda, SpamTitan, EasyDMARC. Backup: Datto BCDR, Datto SaaS Protection, Veeam, Acronis, Axcient x360Recover, Cove Data Protection, Rubrik, Dropsuite, Keepit, AvePoint, Redstor. Documentation: IT Glue, Hudu, IT Portal (SI Portal), Confluence, SharePoint, Notion, ITBoost. Microsoft 365 and identity: Microsoft 365, Google Workspace, Microsoft Entra ID, Okta, JumpCloud, Duo, CIPP, Microsoft Purview. Network: Cisco Meraki, Ubiquiti UniFi, Fortinet FortiGate, SonicWall, Auvik, Domotz, Liongard, PRTG, Cisco Catalyst Center, Aruba Central, Ruckus, WatchGuard Cloud. Billing and accounting: QuickBooks Online, Xero, Stripe, Sherweb, QuoteWerks, Sage Intacct, Pax8, ConnectWise CPQ, Gradient MSP, Microsoft Partner Center, Ingram Micro Xvantage, Quoter. Security training and compliance: KnowBe4, Huntress Security Awareness Training, Vanta, Drata, Breach Secure Now, Hook Security, Apptega, Compliance Scorecard, Cynomi. Vulnerability scanning: Tenable, Qualys, Rapid7 InsightVM, ConnectSecure, runZero, RapidFire VulScan, RapidFire Network Detective, RapidFire Cyber Hawk, Nodeware. DNS filtering: DNSFilter, Cisco Umbrella, Cloudflare Zero Trust, Zscaler, SafeDNS, WebTitan. Passwords: 1Password, Bitwarden, Passportal, Devolutions, Keeper Security. Admin rights and allowlisting: ThreatLocker, Admin By Request, AutoElevate. Remote access: ConnectWise ScreenConnect, TeamViewer, Splashtop, BeyondTrust Remote Support. Teams, chat and phones: Microsoft Teams, Slack, Zoom, RingCentral, 3CX. Cloud and files: Microsoft Azure, AWS, Dropbox, Box, Wasabi. Reporting and lifecycle: ScalePad, Power BI, Grafana, Datadog, CloudRadial, Crewhu, BrightGauge, SmileBack. Automation platforms: Rewst, Power Automate, n8n, Zapier, Make. No public API found (Control Center cannot connect yet): Todyl, ConnectWise SIEM, Barracuda XDR, IT Portal (SI Portal), ITBoost, Breach Secure Now, Hook Security, Apptega, Compliance Scorecard, Cynomi, RapidFire VulScan, RapidFire Network Detective, RapidFire Cyber Hawk, Nodeware, AutoElevate, BrightGauge, SmileBack. API only for apps the vendor approves (the connection depends on the vendor): Sage Intacct, ConnectWise CPQ, Gradient MSP. ### Examples of tools working together A threat, handled. The endpoint security tool: Flags a threat on a laptop at Northbridge Insurance. Control Center: Adds who uses it: the claims manager, who can open every policy file. The PSA: Opens a priority ticket with all of it, so nobody starts from zero. The endpoint security tool: Isolates the laptop the moment a tech approves. The documentation platform: Records what happened for Northbridge’s next QBR. A new hire, one request. The PSA: Northbridge asks for a new hire’s setup. The directory: Creates the account with the right groups and licenses. The RMM: Runs your new-laptop setup on their device. The documentation platform: Documents the user and what they can access. The PSA: Closes the ticket with the time logged. An alert, fixed. The RMM: Raises a low-disk alert on a server at Meridian Health. Control Center: Drops the duplicates and checks whether it has happened before. The documentation platform: Finds the fix your team wrote down last time. The RMM: Runs the cleanup when a tech approves. The PSA: Logs one ticket, not one per alert, with the time recorded. A QBR, written. The PSA: Brings the quarter’s tickets and response times. The RMM: Brings patch status for every device. The endpoint security tool: Brings the threats it stopped. The backup: Brings backup results for every server. Control Center: Writes Northbridge’s QBR in business terms, for your vCIO to approve. A phish, contained. The email security tool: Catches a phishing email two people at Golden Gate already clicked. The email security tool: Pulls it from every inbox that got it. The directory: Shows their sign-ins since the click. Control Center: Resets their passwords and signs them out everywhere when a tech approves. The PSA: Logs it all on one ticket. Licenses, squared. Microsoft 365: Counts Microsoft 365 licenses at every client. The PSA: Compares them with what each agreement bills. Control Center: Finds licenses you’re not billing for, and ones nobody uses. The PSA: Updates the agreement after you approve. A failed backup, sorted. The backup: A server backup fails at Harbor Logistics. The RMM: Shows the server’s disk space and last restart. Control Center: Adds what that server runs for Harbor’s business. The PSA: Opens one ticket with the error and the last good backup. Control Center: Puts the result in Harbor’s next QBR. ### Automations Work that runs on its own, across your tools. A person approves the steps that matter. - Alerts become one ticket, not a pile. RMM alerts are grouped and duplicates dropped. One PSA ticket opens with the device, the user and what it means for the client. - Threats triaged before a tech looks. When the endpoint security tool flags a threat, a priority PSA ticket opens with who uses the device and what it can reach. - Isolation, approved from the ticket. A tech approves from the PSA ticket and the endpoint security tool isolates the device. Releasing it works the same way. - Known fixes run when a tech approves. For a repeat issue, your fix script runs through the RMM, and the time lands on the PSA ticket. - New hires set up from one request. A request in the PSA creates the user in the directory with the right groups and licenses, then closes the ticket. - Offboarding that misses nothing. One PSA ticket blocks sign-in in the directory, removes licenses and closes with a record of every step. - Failed backups handled overnight. When a backup job fails, a PSA ticket opens with the error and the last good backup. - Phishing clicks checked fast. When the email security tool catches a phish, directory sign-ins are checked for anyone who clicked, and it’s all on one PSA ticket. - Site down, ticket ready. When the network tool reports a site offline, a PSA ticket opens with the site and every device affected. - Approvals where your team already works. Anything waiting on a person is posted to Teams or Slack with the context and a link to approve. - Missed time entries caught daily. Tickets with work but no time in the PSA are flagged to the tech each afternoon. - Every ticket triaged and routed. New PSA tickets are categorized, prioritized and routed, with the client’s business context attached. - Documentation that updates itself. Devices from the RMM sync into the documentation platform every night, with changes flagged. - Blocked threats explained. When the DNS filter blocks something dangerous, the PSA ticket says which device, which user and why. - Admin requests approved in one place. Requests from the admin-rights tool become PSA tickets, and a tech approves or denies them there. - Cloud bills watched every day. Azure or AWS spend is checked per client daily, and a jump opens a PSA ticket before the invoice lands. - Old hardware turned into a plan. Devices the lifecycle tool shows out of warranty go on each client’s roadmap with a refresh budget. - Agreements and invoices reconciled. PSA agreements are checked against accounting system invoices every month, and anything unbilled is flagged. - New clients onboarded on rails. A new client in the PSA gets a checklist that tracks RMM agents, the endpoint security tool coverage and backup jobs until every device is done. - Your existing automations, plugged in. Control Center can start your automation platform workflows and use what they return, so nothing you built is wasted. - Full disks cleaned up before anyone calls. When the RMM flags a disk filling up, the cleanup script your team approved runs. A PSA ticket opens only if that doesn’t fix it. - Failed patches retried, then explained. Devices that fail patching in the RMM get another try in the next window. If one fails again, a PSA ticket opens with the error and the device’s history. - Software requests installed on approval. A software request in the PSA installs through the RMM once a tech approves it, and the ticket closes with what was installed. - New devices set up to your standard. When a new device checks in to the RMM, your baseline scripts run on it automatically. - Password resets handled from the ticket. A reset request in the PSA is done in the directory once a tech approves it, and the ticket closes itself. - Risky sign-ins investigated. A sign-in from an unusual country, or a burst of failed sign-ins in the identity provider, opens a PSA ticket with the user’s recent activity. - MFA gaps turned into tickets. Users in the identity provider without MFA open one PSA ticket per client, with the list attached. - Unused licenses reclaimed on approval. Microsoft 365 licenses nobody has used in 30 days are listed per client. A tech approves, and they’re removed. - SOC incidents land with context. When the siem opens an incident, a PSA ticket opens with the affected users and devices and what they can reach. - Critical vulnerabilities become tickets. New critical findings from the vuln open a PSA ticket per client, grouped by fix rather than by device. - Failed restore tests caught early. When a backup restore check fails, a PSA ticket opens before anyone needs that backup. - Firewall configs documented every night. The network tool configurations are saved to the documentation platform every night, with changes highlighted. - Website unblock requests handled on approval. A request in the PSA to unblock a site updates the DNS filter policy once a tech approves it. - Remote sessions turned into time entries. Sessions in the remote are matched to PSA tickets, and missing time is drafted for the tech to confirm. - QBR action items become tickets. Every action item agreed in a QBR becomes a PSA ticket or project, with an owner and a date. - Renewals quoted before they lapse. Agreements in the PSA ending in the next 60 days get a renewal quote drafted in the accounting system for your account manager. - Threats remediated on approval. A tech approves remediation from the PSA ticket, and the endpoint security tool cleans up the device. - Broken agents reinstalled. When an endpoint security tool agent stops reporting, the RMM reinstalls it with your script once a tech approves. ### Technology standards Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - MFA on every account. Checked in the identity provider for every user at every client. - The endpoint security tool on every device. Devices in the RMM without a healthy endpoint security tool agent become a ticket. - Patches inside your window. Every device in the RMM, against the patch window you set. - Supported operating systems only. Devices in the RMM on Windows or macOS versions past end of support. - Every backup finished. Backup jobs that failed or didn’t run in the last 24 hours. - Backups that actually restore. The backup verification results, checked every day. - Microsoft 365 locked down. Legacy sign-in blocked, admin roles kept small and conditional access on. - Email protection on every mailbox. Mailboxes in the directory that the email security tool isn’t protecting. - DNS filtering on every device. Devices in the RMM without a DNS filter agent. - Network gear on current firmware. The network tool firmware checked against the version you approve. - Network changes caught. The network tool configuration changes since the last approved version are flagged. - Security training completed. The security training platform completion for every client, against your target. - Phishing tests passed. The security training platform results per client, with repeat clickers flagged. - Shared passwords rotated. Credentials in the password manager older than your rotation window. - Every client on a current agreement. Clients in the PSA with an expired or missing agreement. - Endpoint security tool agents healthy. Agents offline, out of date or not reporting, at every client. - No stale devices or accounts. Devices in the RMM that haven’t checked in for 30 days, and directory accounts unused for 90. - Devices compliant in Intune. Compliance and encryption for every managed device. - Documentation complete. Every client in the documentation platform has current contacts, sites and assets. - Every mailbox backed up. Mailboxes in the directory that the Microsoft 365 backup isn’t backing up. - No file-sharing accounts left behind. Dropbox or Box accounts for people who are no longer in the directory. - Compliance controls passing. The security training platform control and test results for every client. - Only approved software. Software in the RMM’s inventory, checked against each client’s approved list. - No unapproved remote access tools. Remote access software in the RMM’s inventory that isn’t on your approved list, at every client. - Critical vulnerabilities fixed on time. The vuln findings rated critical, against the fix window you set. - Every device scanned. Assets in the vuln that haven’t been scanned in the last 30 days. - Logs collected from every server. Servers in the RMM that the siem isn’t collecting logs from. - Everyone in the password manager. People in the directory who don’t have a password manager account. - Guest accounts reviewed. Guest accounts in the directory older than 90 days, at every client. - Web filtering set to your standard. The DNS filter policies checked against the categories you block for every client. - No wide-open firewall rules. The network tool rules that allow any traffic from anywhere, flagged at every site. - Business devices under warranty. Devices the lifecycle tool shows out of warranty, against your refresh policy. - Licenses only on active users. Microsoft 365 licenses on disabled or unused accounts. - Every device has an owner. Devices in the RMM that aren’t matched to a person in the directory. - Every device documented. Devices in the RMM that are missing from the documentation platform. - Threats closed within 24 hours. The endpoint security tool threats still open after 24 hours, at every client. - Sign-ins only from expected countries. The identity provider sign-ins from outside each client’s list of countries. - Leavers fully removed. Accounts in the directory still enabled for people offboarded through the PSA. - Tickets closed properly. PSA tickets closed without notes or time, by tech. For you, not the client. - Agents on a supported version. Endpoint security tool agents running a version older than the one you approve. - Backups recent enough to recover from. Servers whose last good the backup backup is older than your recovery point target. ### Reports and QBRs Numbers from your tools, in the client’s language. Build a report from any data you connect. - The whole QBR, drafted. The PSA and the RMM in one QBR, written in the client’s business terms for your vCIO to approve. - Service desk, in business terms. Ticket volume, response times and repeat issues from the PSA, explained by what they cost the client. - Patch compliance. From the RMM, per device and per site. - Threats stopped. From the endpoint security tool, with what was at risk. - Backup success and recovery readiness. From the backup, per server and per site. - MFA coverage and risky sign-ins. From the identity provider. - Phishing blocked and who’s targeted. From the email security tool. - Network uptime by site. From the network tool. - Phish-prone rate and training. From the security training platform. - Hardware due for refresh, with a budget. From the lifecycle tool. - Cloud spend by service. From Azure or AWS, with month-over-month changes. - Microsoft 365 licenses used vs. paid for. Unused and unassigned licenses at every client. - Your margin on every client. Hours in the PSA against revenue in the accounting system. For you, not the client. - Web threats blocked. From the DNS filter. - Your numbers in the BI tool. Control Center can send every metric to the BI tool for the dashboards you already use. - Devices by age and operating system. From the RMM, per client and per site, with the devices due for replacement. - Software inventory. From the RMM, with unapproved software called out. - Alerts and what they cost. Alert volume from the RMM per client, with the PSA time spent on them. For you, not the client. - Vulnerabilities and how fast they’re fixed. From the vuln, per client by severity, with the trend over 90 days. - Security incidents, explained. From the siem: what happened, what was done, and what it means for the business. - Response and resolution against your SLA. From the PSA, per client and per priority. - Where the tickets come from. Tickets from the PSA by person and by issue, so you fix the cause, not the symptom. - What AI did this month. Every AI service’s runs, hours returned and value, ready for the client’s QBR. - Standards scorecard. Every standard you check, passed or failed at each client, with each gap priced as a PSA project. - A one-page monthly summary. Tickets, devices, security and AI work from the PSA and the RMM, on one page for the client’s owner. - Any report you can describe. Describe it in a sentence. Control Center builds it from the PSA and your other connected tools, then sends it on a schedule. - Restore tests, passed and failed. From the backup, per server, ready for the client’s QBR. - Documentation coverage by client. From the documentation platform: what’s documented, what’s missing and what’s out of date. ### Ask Control Center MCP Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - “Which devices at Northbridge don’t have the endpoint security tool?”. Answered from the RMM and the endpoint security tool. - “Which clients missed a backup last night?”. Answered from the backup. - “Who at Golden Gate still doesn’t have MFA?”. Answered from the identity provider. - “What did we do for Meridian this month?”. Answered from the PSA. - “Which clients have more licenses than we bill for?”. Answered from Microsoft 365 and the PSA. - “Which firewalls need a firmware update?”. Answered from the network tool. - “Why does Harbor’s file server keep alerting?”. Answered from RMM alerts and the PSA history. - “Who’s the ISP contact for Northwind’s warehouse?”. Answered from the documentation platform. - “Who at Northbridge gets phished the most?”. Answered from the email security tool. - “What changed at Northbridge this week?”. Answered from the PSA, the RMM and the endpoint security tool. - “Who hasn’t finished security training?”. Answered from the security training platform. - “Why did Golden Gate’s Azure or AWS bill go up?”. Answered from Azure or AWS. - “Turn that into an automation.”. Any answer can become a workflow, and a person approves it before it runs. - “Which servers at Northwind are low on disk space?”. Answered from the RMM. - “Which patches failed at Meridian last night?”. Answered from the RMM. - “Which computers still have the old VPN client?”. Answered from the RMM’s software inventory. - “Which devices haven’t checked in this week?”. Answered from the RMM. - “Has this happened at Harbor before? What fixed it?”. Answered from the PSA ticket history. - “What can Sam at Northwind access, and which laptop is theirs?”. Answered from the directory and the RMM. - “Did anyone at Golden Gate sign in from a new country this week?”. Answered from the identity provider. - “What did the endpoint security tool catch at Northbridge this month, and was any of it real?”. Answered from the endpoint security tool. - “Which clients have critical vulnerabilities older than 30 days?”. Answered from the vuln. - “When did we last test a restore of Golden Gate’s file server?”. Answered from the backup. - “What’s left on Meridian’s onboarding?”. Answered from the PSA and the documentation platform. - “What work did we do this month that we didn’t bill?”. Answered from the PSA time entries and agreements. - “Which clients made us the least per hour this quarter?”. Answered from the PSA and the accounting system. - “Whose agreement renews next quarter, and what should we add to it?”. Answered from PSA agreements and each client’s AI roadmap. - “Draft Northbridge’s QBR.”. Built from the PSA, the RMM and every other connected tool, for your vCIO to edit. - “Clean up the disk on Harbor’s file server.”. Drafted as a RMM script that a tech approves before it runs. - “Which devices are isolated right now, and why?”. Answered from the endpoint security tool. - “Which devices at Meridian have an endpoint security tool agent that stopped reporting?”. Answered from the endpoint security tool. - “If Golden Gate’s file server died now, how much work would they lose?”. Answered from the backup: the last good backup and when it finished. - “Who approves changes at Northbridge?”. Answered from the contacts in the documentation platform. ### Billing Get paid for the AI work, through the tools you bill with. - AI services on the PSA agreement. Every AI service you sell is added to the client’s agreement and billed each month, at your margin. - Licenses matched to what you bill. Microsoft 365 licenses at every client against the PSA agreement, with missed billing flagged. - Distributor costs against what you bill. What the distributor charges you for each client, against the PSA agreement. - Every AI run metered. Usage per client and per workflow, behind every line you bill. Not on the list? If it has a documented API, Control Center can connect to it. [Here’s how](https://www.resultsiq.ai/docs/tools/#not-listed). Your stack With your stack 0 things Control Center can do - 0 automations - 0 standards checks - 0 report numbers - 0 questions to ask - 0 billing lines Just unlocked Start with your PSA and RMM. Your plan builds as you pick. See your plan AI plan Your plan ## What your stack can do with Control Center. Prepared for We’ll send a link to this plan, so you can open it again or pass it to your team. First name Work email MSP name Website What it’s worth across your clients $0 a month in AI managed services clients like at $0 a month each. You keep $0 a month at a 70% margin. See their AI roadmap In your own shop 0 things Control Center can do across your 0 tools Pick a few tools above and your plan builds here: what Control Center automates across them, the standards it checks, the numbers it reports and the questions your team can ask. ### Your tools, working together. Start to finish, on the tools you picked. Shown with example clients. Next step: a 30-minute call to see this plan running on your tools. Book it at www.resultsiq.ai/demo/ or call (904) 895-7558. ## One tool, up close. Everything Control Center automates, checks, reports and answers with a single tool. [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for Autotask PSA](https://www.resultsiq.ai/integrations/autotask/) [AI for HaloPSA](https://www.resultsiq.ai/integrations/halopsa/) [AI for Datto RMM](https://www.resultsiq.ai/integrations/datto-rmm/) [AI for N-able N-central](https://www.resultsiq.ai/integrations/n-able-n-central/) [AI for ConnectWise Automate](https://www.resultsiq.ai/integrations/connectwise-automate/) [AI for IT Glue](https://www.resultsiq.ai/integrations/it-glue/) [AI for Hudu](https://www.resultsiq.ai/integrations/hudu/) [AI for Microsoft 365](https://www.resultsiq.ai/integrations/microsoft-365/) [AI for SentinelOne](https://www.resultsiq.ai/integrations/sentinelone/) [AI for Huntress](https://www.resultsiq.ai/integrations/huntress/) [AI for CrowdStrike Falcon](https://www.resultsiq.ai/integrations/crowdstrike/) [AI for Kaseya VSA](https://www.resultsiq.ai/integrations/kaseya-vsa/) [AI for Syncro](https://www.resultsiq.ai/integrations/syncro/) [AI for SuperOps](https://www.resultsiq.ai/integrations/superops/) [AI for Atera](https://www.resultsiq.ai/integrations/atera/) [AI for Microsoft Intune](https://www.resultsiq.ai/integrations/microsoft-intune/) [AI for Veeam](https://www.resultsiq.ai/integrations/veeam/) [AI for Datto BCDR](https://www.resultsiq.ai/integrations/datto-bcdr/) Automation as a service ## Now build it for every client. Your clients have their own apps. Pick a client, and Control Center builds their AI roadmap the same way it built your plan: what to automate, in what order, and what to charge. Pick a client and their apps, and Control Center builds their AI roadmap: what to automate, in what order and what to charge. Prices are examples at a 70% margin, billed through the MSP’s PSA. Golden Gate Insurance (insurance agency). Their apps: Microsoft 365, Applied Epic, QuickBooks Online, DocuSign. Now: Claims intake assistant, $650 a month. Reads claim emails, matches them to the client in Applied Epic and drafts the claim for a person to approve. Now: Renewal outreach, $500 a month. Drafts renewal emails for clients coming up for renewal in Applied Epic, for a person to send. Next: Invoice coding, $400 a month. Reads vendor invoices from the inbox and codes them in QuickBooks for approval. Next: Collections follow-up, $300 a month. Sends polite reminders on overdue QuickBooks invoices and logs the replies. Then: Contracts out the door, $350 a month. Drafts contracts from approved deals and sends them for signature in DocuSign. Then: Company knowledge assistant, $400 a month. Answers staff questions from the company’s own files in Microsoft 365, with the source. Total: $2,600 a month. Summit Legal Group (law firm). Their apps: Microsoft 365, Clio, QuickBooks Online, DocuSign. Now: Matter intake, $550 a month. Turns new-client emails into matters in Clio, with a conflict check a person approves. Now: Engagement letters, $350 a month. Drafts the engagement letter for each new matter in Clio and sends it for signature in DocuSign. Next: Invoice coding, $400 a month. Reads vendor invoices from the inbox and codes them in QuickBooks for approval. Next: Collections follow-up, $300 a month. Sends polite reminders on overdue QuickBooks invoices and logs the replies. Then: Company knowledge assistant, $400 a month. Answers staff questions from the company’s own files in Microsoft 365, with the source. Total: $2,000 a month. Northwind Manufacturing (manufacturer). Their apps: Microsoft 365, Dynamics 365 Business Central, Salesforce, BambooHR. Now: Order entry, $550 a month. Turns emailed purchase orders into sales orders in Business Central for a person to approve. Now: Order status answers, $350 a month. Answers “where’s my order?” emails from Business Central in minutes. Next: Invoice coding, $400 a month. Reads vendor invoices from the inbox and codes them in Business Central for approval. Next: Lead follow-up, $450 a month. Replies to new Salesforce leads in minutes and books the first call. Then: Collections follow-up, $300 a month. Sends polite reminders on overdue Business Central invoices and logs the replies. Then: New-hire onboarding, $350 a month. A new hire in BambooHR gets accounts, documents and a first-week plan, with a person approving. Total: $2,400 a month. Ridgeline Builders (construction). Their apps: Microsoft 365, Procore, QuickBooks Online, DocuSign. Now: Daily project brief, $250 a month. Sums up open RFIs, submittals and schedule changes in Procore for each project manager every morning. Now: Invoice coding, $400 a month. Reads vendor invoices from the inbox and codes them in QuickBooks for approval. Next: Collections follow-up, $300 a month. Sends polite reminders on overdue QuickBooks invoices and logs the replies. Next: Contracts out the door, $350 a month. Drafts contracts from approved deals and sends them for signature in DocuSign. Then: Company knowledge assistant, $400 a month. Answers staff questions from the company’s own files in Microsoft 365, with the source. Total: $1,700 a month. Bright Harbor Logistics (distributor). Their apps: Google Workspace, NetSuite, HubSpot, Zendesk. Now: Order entry, $550 a month. Turns emailed purchase orders into sales orders in NetSuite for a person to approve. Now: Order status answers, $350 a month. Answers “where’s my order?” emails from NetSuite in minutes. Next: Invoice coding, $400 a month. Reads vendor invoices from the inbox and codes them in NetSuite for approval. Next: Lead follow-up, $450 a month. Replies to new HubSpot leads in minutes and books the first call. Then: Support triage, $450 a month. Sorts Zendesk tickets and drafts answers for a person to send. Then: Collections follow-up, $300 a month. Sends polite reminders on overdue NetSuite invoices and logs the replies. Total: $2,500 a month. Then do it for every client like this one: 10 clients like Golden Gate Insurance at $2,600 a month each is $26,000 a month in AI managed services, and $18,200 a month kept at a 70% margin. Easy to implement. Build an automation once. Every client with the same apps gets it, running on their own accounts. Easy to manage. Every client’s automations, approvals and runs in one place. Easy to price. Each service is priced from what it costs to run, at the margin you set. Easy to keep your margin. Every AI run is metered and billed in your PSA, with your margin on every client, every month. Client apps Control Center connects to: Microsoft 365, Google Workspace, Dropbox, Box, QuickBooks Online, Xero, NetSuite, Dynamics 365 Business Central, HubSpot, Salesforce, Pipedrive, Applied Epic, AMS360, Clio, Procore, Shopify, BambooHR, Gusto, Zendesk, Freshdesk, DocuSign, Adobe Acrobat Sign, monday.com, Asana. Applied Epic: Applied Epic’s API needs an Applied SDK-API license on the agency’s account. AMS360: AMS360’s Web Service API needs a signed SDK agreement with Vertafore, at no extra charge. Gusto: Gusto approves each app that connects to its API, so this connection depends on Gusto’s approval. ### See your plan running on your tools. Thirty minutes, the live product, your stack and one of your clients. [Book a call](https://www.resultsiq.ai/demo/?src=integrations) [Join the waitlist](https://www.resultsiq.ai/waitlist/) Product names and logos belong to their owners. Listing a tool shows that Control Center can work with it, not a partnership or endorsement. Prices are examples at a 70% margin. --- Page: https://www.resultsiq.ai/security/ Security # We host it. Your AI, keys and clients stay yours. Control Center runs in a ResultsIQ-managed Azure environment, isolated per tenant. Here’s what that covers, and what it doesn’t. Where it runs ## Four parts, and three of them stay yours. Your AI account, your keys, your rate You bring the provider account and negotiate the rate. Every token bills to you directly, and we take no spread on it. Yours Your connections, scoped by you Every integration is enabled per tenant with the exact API operations you allow, and nothing else. Yours Your client relationships We never contact your clients. The brand, tenants and invoices are yours. Yours The application, hosted by us Control Center runs in a ResultsIQ-managed Microsoft Azure environment, isolated per tenant. You stand nothing up. Ours We host the application, and we don’t resell your AI. Many platforms bundle compute and take a margin on every token. Yours bills to your own account at your rate, with nothing added. Bring-your-own-cloud is on the roadmap and isn’t in the product yet. The backend is built for it, and we’ll update this page when it ships. For now, Control Center is hosted by us. What we can see ## Control stays with you, and it’s logged. Role-based permissions Enforced per tenant. Your team sees what you decide they see. A run-level audit trail on every artifact Every document, price, workflow and approval is logged with who, when and on what input. A human approval gate before any client sees anything We left this step manual on purpose. No training on your data Your client documentation is never used to train a model or improve anything outside your tenant. Where we stand ## What’s certified, and what isn’t yet. Here’s where each one stands today. Microsoft Azure Where it runs A ResultsIQ-managed Azure environment, isolated per tenant. Microsoft publishes Azure’s own SOC and ISO reports. SOC 2 Type I In progress Target Q1 2027. We’ll publish the report once we have it. Bring your own cloud Roadmap The architecture supports it, but it isn’t available at launch. ### Send it to your security lead. They’ll want the hosting model, the permission matrix and the audit trail. All three are open to them during the ninety days, at no cost, before you commit to anything. [Book a call](https://www.resultsiq.ai/demo/?src=security) [Join the waitlist](https://www.resultsiq.ai/waitlist/) --- Page: https://www.resultsiq.ai/no-brainer/ The No Brainer # Do the math yourself. Enter two numbers. Every other assumption is published below, and you can change any of it. Your monthly recurring revenue $100,000 Managed services only. Leave out hardware, licenses and project work. How many clients 40 — Added profit in year 3 — How much more you make in year 3 than if nothing changes. Return on investment — Year-one profit back for every $1 you pay us. Added to what your MSP is worth — When you sell, at 8× profit. These are the assumptions behind the numbers above. Change any of them and the page recalculates. Your gross margin today 45% Clients buying an AI service by the end of year 1 — By year 3 — What you charge a client a month by month 12 (three to five workflows) $2,500 Billable workflows per client buying ($75 a month each to us) 3 Hours returned per client, per week 0.6 Your loaded hourly cost $55 Your profit margin today 18% Share of overlapping tools you retire 70% Monthly spend on the tools this overlaps. Total: — Automation / orchestration platform /mo Client reporting & BI /mo vCIO / QBR tooling /mo Technical alignment & standards /mo Per-seat AI licenses for the team /mo Dashboards & scorecards /mo If nothing changes, what happens to this business over the next three years? — — Your MSP in three years ## Which company would you rather own? The same business three years out, run two ways, with the same clients, team and market. If nothing changes — revenue — gross margin — profit Worth at exit · 8× — With Control Center — — revenue — — gross margin — — profit Worth at exit · 8× — — The only difference is a decision you make this quarter. Click any line in the table. The panel shows the arithmetic behind that number. — Why it’s a no-brainer ## ROI positive before our first invoice. This isn’t a cost decision. It’s a revenue decision, and the first 90 days cost nothing. Every number here comes from your numbers above. - Days 1–90 $0 Your own MSP first, then your first client, billed for an AI service. - Day 91 Invoice one Your client is already paying you, so you start ROI positive. - Year 1 — of new revenue, and — back in profit for every $1 you pay us. - Year 3 — added to what your MSP is worth, even at the same 8× multiple. What we charge: $1,750 a month for the platform, plus $75 a month for each workflow you bill a client for, starting on day 91. Every number on this page already takes it out, and counts a full 12 months of it in year one ( — on your numbers) even though the first 90 days cost nothing. ### Start with 90 days at no cost. Book a call and we’ll set up your first 45 days with you. You set every number on this page; we only supplied the arithmetic. [Book a call](https://www.resultsiq.ai/demo/?src=no-brainer) [Join the waitlist](https://www.resultsiq.ai/waitlist/) The full price and how billing works are on [Pricing](https://www.resultsiq.ai/pricing/). How the first 90 days run is on [90 Days, No Cost](https://www.resultsiq.ai/90-days/). Comparing AI tools? [See our guide to AI tools for MSPs.](https://www.resultsiq.ai/ai-tools-for-msps/) --- Page: https://www.resultsiq.ai/pricing/ Pricing # Our price is published, and it’s set to protect your margin. We built this so the margin on AI managed services stays with you. One flat platform price, plus $75 for each workflow you bill a client for. The platform $1,750 / month, after day 90 The same for fifteen clients or two hundred. + Per billable workflow $75 / month, after day 90 Charged only for workflows you bill a client for. - First 90 days: $0. [How the 90 days work](https://www.resultsiq.ai/90-days/) - Hosting is included. Control Center runs in our Azure environment, so there’s nothing for you to set up. - AI usage is yours. You bring your own AI account and keys and pay your own rate. We add no markup. Why we publish it ## We publish all of it. So now we can talk revenue. Price, the model and every assumption behind it. We’re not hiding anything. Vendors hide the true cost You find out what it did to your margin when the invoice arrives. We publish all of it Price, model and assumptions, with no call, form or NDA. Then we talk revenue It’s the number that changes your business. Everything we charge is on this page. #### You will never find the following on your invoice Per seat or per user Per client or per tenant A markup on your AI spend Hosting or infrastructure fees Setup or onboarding fees A tier that hides what you needed What it costs you ## What it costs you, and what you keep. Set three numbers. Everything else uses the published figures. The calculator on this page: 16 clients on the service at $2,500 a month each, with 3 billable workflows per client, is $480,000 a year of new revenue. Delivering it costs 30%, $144,000: your AI usage and your team's time, the same 70% gross margin used across this site. Our fee is $64,200 ($1,750 a month plus $75 a month for each of 48 billable workflows). You keep $271,800 a year, a 56.6% margin. The platform price is flat, so your margin grows with every client you add. Want the three-year picture, with every assumption you can change? Open [The No Brainer](https://www.resultsiq.ai/no-brainer/). ### Ninety days, then decide. Days 1–45 run inside your own MSP, days 46–90 with your first client, and on day 91 you’re billing before we are. [How the 90 days work](https://www.resultsiq.ai/90-days/) [Book a call](https://www.resultsiq.ai/demo/?src=pricing) [Join the waitlist](https://www.resultsiq.ai/waitlist/) --- Page: https://www.resultsiq.ai/90-days/ 90 Days, No Cost # Start ROI positive. First 90 days, no cost. Run Control Center in your own MSP, then with one client. The first 90 days cost nothing, with no card and no contract, and you bill your client before we bill you. [Book a call](https://www.resultsiq.ai/demo/?src=90-days) [Join the waitlist](https://www.resultsiq.ai/waitlist/) How the 90 days work ## Your MSP first. Then one client. Then the rest. We set it up with you, on a call every week or two. Days 1–45 Your own MSP - Set up with us - Your internal AI roadmap - First automations running Days 46–90 Your first client - Their business documented - Their AI roadmap built - Billed for an AI service Day 91 We send our first invoice - You’ve already been billing your client - Or you walk away, and owe nothing Then repeat it across the rest of your clients. After day 90: $1,750 a month for the platform, plus $75 a month for each workflow you bill a client for, on an annual contract with a 30-day notice period. If it isn’t working, walk away by day 90 and owe nothing. [See pricing](https://www.resultsiq.ai/pricing/) FAQ ## Frequently asked questions. ### What does it cost? $1,750 a month for the platform, plus $75 a month for each workflow you bill a client for. Nothing for the first 90 days. ### When can we start? We’re running pilots with select MSPs now. In Q1 2027 we start reaching out to the waitlist. [Join the waitlist](https://www.resultsiq.ai/waitlist/) to be first in line. ### Do I need a card or a contract to start? No. No card, no contract and no procurement cycle. ### Do I need to hire anyone? No. We set it up with you, on a call every week or two at your pace. ### When does revenue start? By day 90 your first client is paying you for an AI service. You bill them before we bill you. ### What happens on day 91? If it’s working, you move to an annual contract with a 30-day notice period, and we send our first invoice. If it isn’t, you walk away. There’s nothing to cancel. ### Do I have to follow the 90-day plan? No. The 90 days are there so you start ROI positive before you spend anything on AI. The plan is our suggestion, so use the time however works best for your MSP. ### What if my team won’t use it? You’ll know by day 45, because the first 45 days run inside your own MSP, not a client’s. If it doesn’t stick there, you walk. ### Who pays for the AI? You do, on your own AI account, at your own negotiated rate. We never mark it up. ### Who owns the data? You do. Your data, your clients’ data and everything the platform produces stay yours, whether you stay with us or not. ### Where does it run? We host it in the ResultsIQ Azure environment. There’s nothing for you to stand up. ### What does it connect to? 156 MSP tools, plus anything with a documented REST API. [See the list](https://www.resultsiq.ai/integrations/). ### Is it SOC 2 certified? SOC 2 Type I is in progress, with a target of Q1 2027. [See where we stand](https://www.resultsiq.ai/security/). ### What’s the biggest risk? Adoption. If you don’t have strategic conversations with your clients today, software won’t start them. Control Center makes those conversations faster and better evidenced. ### Ninety days is the whole ask. If it isn’t working by day 90, you walk away and owe nothing. [Book a call](https://www.resultsiq.ai/demo/?src=90-days) [Join the waitlist](https://www.resultsiq.ai/waitlist/) --- Page: https://www.resultsiq.ai/about/ About # I run an MSP. Control Center is what I needed and couldn’t buy. My father started Reboot in 2005 and handed the business off to me. When I set out to deliver AI to our clients, every option meant more tools and more cost. So we built one that doesn’t. Connor Reece President and CEO, Reboot How I got here ## From my father’s MSP to this. - 2005 My father, Mike, starts Reboot. - 2023 I get involved and start learning the business. I join my first peer group, TruMethods. - 2023–24 I take over the day-to-day. I join Robin Robins’ Producers Club, and later MSP Fuel, learning from owners who’ve done it. - Late 2025 I dig into how to deliver AI as a managed service: talking to vendors, asking clients what they want, fitting it into how we run. - 2026 Sales calls, our clients and feedback from other owners shape the framework. Then I build Control Center with an outside developer. To jerry-rig it, I’d need three to four vendor contracts, a developer and twelve months in the hole before any ROI. Every other option means more tools, more stuff, more junk. We need fewer. Connor Why I built it Gross margins in our industry will keep going down unless every team gets more efficient, without adding tool costs. Commoditized IT revenue, and the margin on it, is getting squeezed. We need to be leaner. Control Center is built to deliver better service at a higher gross margin, without more tools. Reboot runs at a high gross margin. I know what it takes, and I built this to help other owners get there. My word ## How I’ll treat you. - We never sell to your clients. - No markup on your AI. - The price is on the website. - 90 days before you pay. Email me, owner to owner. [connor.reece@resultsiq.ai](mailto:connor.reece@resultsiq.ai) [Book a call with me](https://www.resultsiq.ai/demo/?src=about) [Join the waitlist](https://www.resultsiq.ai/waitlist/) Connor ## Questions ### Is ResultsIQ.ai related to ResultsIQ in Tampa? No. ResultsIQ.ai makes Control Center for MSPs and is not affiliated with the Tampa HubSpot agency at resultsiq.io. --- Page: https://www.resultsiq.ai/ai-tools-for-msps/ Guide # AI tools for MSPs: what to use for each job Most lists of AI tools for MSPs mix two different things: tools that make your MSP faster, and tools that let you sell AI to your clients. They’re bought for different reasons and judged on different numbers, so this guide sorts them by the job they do. By [Connor Reece](https://www.resultsiq.ai/about/), updated November 2026 A note on where we stand: we make one of these tools, ResultsIQ Control Center, and it’s in the last group. Everything we say about other products comes from their own websites, as of November 2026. ## 1. AI for the service desk The job: triage tickets, answer the routine ones, and close tickets without a technician touching them. What to check: Which PSA it works with, how it counts a ticket “resolved by AI”, and whether it’s priced per technician, per ticket or per endpoint. Ask for the share of tickets closed with no technician time in MSPs your size. - [Thread](https://www.getthread.com/) An AI service desk for MSPs. Its AI agents take requests in Microsoft Teams, Slack and by phone, and work the tickets in your PSA (ConnectWise, Autotask or HaloPSA). - [MSPbots](https://mspbots.ai/) AI agents that work the service desk alongside your team, built on MSPbots’ business intelligence platform and automation bots for MSP data. - [Pia](https://pia.ai/) Service desk automation that takes routine requests, like password resets and onboarding, from request to resolved ticket inside your PSA. It works with Thread for no-touch resolution. - [Neo Agent](https://www.neoagent.io/) An AI automation platform for MSPs that works in Microsoft Teams and your PSA to help resolve tickets faster. - [zofiQ](https://www.connectwise.com/zofiq) AI agents that learn from your PSA, knowledge base and RMM, then triage and solve tickets inside your PSA. Part of ConnectWise since January 2026. ## 2. Automation and orchestration The job: run the repetitive work (onboarding, offboarding, license changes, alerts to tickets) across your tools. What to check: Prebuilt MSP workflows, PSA and RMM integrations, and who maintains a workflow when an API changes. - [Rewst](https://rewst.io/) An automation platform built for MSPs: build a workflow once and reuse it across the clients you choose. - [n8n](https://n8n.io/) General workflow automation you can host yourself; more building, more control. - [Microsoft Power Automate](https://www.microsoft.com/en/power-platform/products/power-automate/) Microsoft’s workflow automation; a fit if most of your clients live in Microsoft 365. ## 3. Security with AI built in The job: cut alert noise and catch real threats faster across clients. - [Guardz](https://guardz.com/) A security platform built for MSPs that covers email, identity, endpoints and awareness training in one place, with 24/7 managed detection and response. - The security tools you already run Most EDR, MDR and SIEM vendors you already use now add AI triage. Judge them on false positives in your own clients, not on the demo. ## 4. AI assistants for your team The job: make your technicians, account managers and owners faster with a general AI assistant. What to check: The data protection terms, admin and audit controls, and whether the assistant can reach your PSA, RMM and documentation, usually through MCP connectors. - [Microsoft 365 Copilot](https://www.microsoft.com/en-us/microsoft-365-copilot/business) Microsoft’s assistant inside the 365 apps, which MSPs can resell to clients through the Cloud Solution Provider (CSP) program. - [ChatGPT](https://openai.com/chatgpt/pricing/) Business and Enterprise plans and [Claude](https://claude.com/pricing) Team and Enterprise plans General assistants with admin controls and business data terms. ## 5. Tools for selling AI to your clients as a managed service The job: turn AI into a recurring service line, with a scope, a price, delivery and a monthly invoice. What to check: Who bills the client, what your margin is after the vendor’s fee, who owns the client relationship, and whether the tool produces something you can show in a QBR. Comparing platforms? [See how Control Center compares with Hatz AI and Lemhi.](https://www.resultsiq.ai/compare/) - [Hatz AI](https://hatz.ai/) A secure AI platform that MSPs use to build, sell and manage AI for their clients as a service. - [Microsoft 365 Copilot through CSP](https://www.microsoft.com/en-us/microsoft-365-copilot/business) Resell licenses and wrap adoption and governance services around them. - [ResultsIQ Control Center](https://www.resultsiq.ai/) Ours Finds the AI opportunities in each client’s business, prices them in the client’s own numbers, builds the automations and bills them every month. Control Center MCP is included, so your team’s Claude or ChatGPT can reach every client and tool with the same roles and client scopes. The first 90 days cost nothing, and you bill your client before we bill you. We sell only to MSPs, never to their clients. Works with [ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/), [Autotask](https://www.resultsiq.ai/integrations/autotask/), [HaloPSA](https://www.resultsiq.ai/integrations/halopsa/), [NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/), [Datto RMM](https://www.resultsiq.ai/integrations/datto-rmm/), [N-able N-central](https://www.resultsiq.ai/integrations/n-able-n-central/), [IT Glue](https://www.resultsiq.ai/integrations/it-glue/), [Hudu](https://www.resultsiq.ai/integrations/hudu/), [Microsoft 365](https://www.resultsiq.ai/integrations/microsoft-365/), [SentinelOne](https://www.resultsiq.ai/integrations/sentinelone/), [CrowdStrike](https://www.resultsiq.ai/integrations/crowdstrike/), [Huntress](https://www.resultsiq.ai/integrations/huntress/) and [144 more tools](https://www.resultsiq.ai/docs/tools/). ## How to choose - Start with the job that costs you the most hours or the most revenue. - Check that it works with your PSA and RMM before you look at features. - Know where client data goes and who can see it. - Compare price units (per seat, per ticket, per workflow) against your own margin. - Prefer tools that report results you can put in front of a client. ## Frequently asked questions ### What are the best AI tools for MSPs? It depends on the job. For the service desk, MSPs look at Thread, MSPbots and Pia. For automation, Rewst. For security, Guardz and the AI features in their existing EDR. For their own team, Microsoft 365 Copilot, ChatGPT or Claude. For selling AI to clients, Hatz AI, Copilot through CSP, and ResultsIQ Control Center. ### Can MSPs resell Microsoft 365 Copilot? Yes. Microsoft sells Copilot through the Cloud Solution Provider (CSP) program, so MSPs can resell licenses and add adoption and governance services. ### How do MSPs make money from AI? By selling it as a managed service: a defined scope per client, a monthly price, delivery they control, and reporting that shows the result. [Score my MSP](https://www.resultsiq.ai/score/) estimates what that’s worth to your MSP. ### Is Control Center a service desk tool? No. Control Center is for selling and delivering AI managed services to your clients. It works alongside your PSA and service desk tools. ResultsIQ Control Center is a platform built for managed service providers (MSPs). It lets an MSP scope, price, build and bill AI managed services across the clients it already has. [Score my MSP](https://www.resultsiq.ai/score/) [Do the math](https://www.resultsiq.ai/no-brainer/) [Book a call](https://www.resultsiq.ai/demo/?src=guide) --- Page: https://www.resultsiq.ai/guides/ Guides # Guides for MSPs selling AI Short, plain answers to what MSP owners ask about AI managed services, AI MRR, MCP and the tools to deliver them. By [Connor Reece](https://www.resultsiq.ai/about/), updated November 2026 ## Guides Start with what AI managed services are, then how they turn into monthly revenue. - [What are AI managed services?](https://www.resultsiq.ai/guides/what-are-ai-managed-services/) What’s usually included, how it differs from reselling AI licenses, and how MSPs price it. - [What is AI MRR?](https://www.resultsiq.ai/guides/what-is-ai-mrr/) The monthly recurring revenue an MSP earns from AI managed services, where it comes from and how to grow it. - [MCP for MSPs: what it is and how to use it](https://www.resultsiq.ai/guides/mcp-for-msps/) How the Model Context Protocol lets Claude or ChatGPT work with your PSA, RMM and documentation, and the risks to manage. - [AI tools for MSPs: what to use for each job](https://www.resultsiq.ai/ai-tools-for-msps/) The AI tools MSPs use in 2026, sorted by job: service desk, automation, security, AI for your team, and selling AI to clients. ## Comparisons How Control Center compares with other AI platforms built for MSPs, described from their own public materials. - [ResultsIQ Control Center vs Hatz AI](https://www.resultsiq.ai/compare/hatz-ai/) A governed AI workspace for client teams, next to a service line you scope, deliver and bill. - [ResultsIQ Control Center vs Lemhi](https://www.resultsiq.ai/compare/lemhi/) A consulting playbook for AI readiness and rollout, next to automations delivered and billed every month. - [All comparisons](https://www.resultsiq.ai/compare/) Every comparison in one place. --- Page: https://www.resultsiq.ai/guides/what-are-ai-managed-services/ [Guides](https://www.resultsiq.ai/guides/) # What are AI managed services? AI managed services are AI work that a managed service provider delivers to its clients on an ongoing basis and bills every month, the same way it bills for managed IT or managed security. By [Connor Reece](https://www.resultsiq.ai/about/), updated November 2026 ## What’s usually included - AI policy and governance: an acceptable-use policy, which tools are approved, and who can use what. - Approved AI tools and data protection: rolling out Copilot, ChatGPT or Claude with the right settings, and keeping client data out of tools that aren’t approved. - AI opportunity assessment: finding where AI saves the client time or money, in the client’s own numbers. - Automations: building and running the workflows that do the work, across the tools the client already uses. - Reporting: showing what AI did each month, usually in the QBR. ## How it differs from reselling AI licenses Reselling a license is a one-time margin on someone else’s product. A managed service is the work around it: scoping, setup, governance, automations and reporting. That’s where the recurring revenue is. It’s also why MSPs, who already hold the client relationship and the admin access, are well placed to sell it. ## How MSPs price it Three models are common: a flat monthly fee per client tier, a fee per automation or workflow in production, or a share of the measured return. Most MSPs start with a small fixed scope (policy, approved tools, one or two automations) and grow it at each QBR. ## What you need to deliver it You need a way to assess each client, a catalog of services with prices, the ability to build and run automations across your PSA, RMM and Microsoft 365, and a monthly invoice line. ResultsIQ Control Center is a platform built for MSPs to scope, price, build and bill AI managed services across the clients they already have. [AI tools for MSPs](https://www.resultsiq.ai/ai-tools-for-msps/) [Score my MSP](https://www.resultsiq.ai/score/) [Book a call](https://www.resultsiq.ai/demo/?src=guide) --- Page: https://www.resultsiq.ai/guides/what-is-ai-mrr/ [Guides](https://www.resultsiq.ai/guides/) # What is AI MRR? AI MRR is the monthly recurring revenue a managed service provider earns from AI managed services: AI governance, approved tools, automations and reporting that it delivers and bills every month. By [Connor Reece](https://www.resultsiq.ai/about/), updated November 2026 ## Why it matters for MSPs Clients are already asking about Copilot, ChatGPT and AI policies. Answering those questions one project at a time earns a one-time fee. Turning them into a monthly service earns MRR, which is what an MSP’s valuation and cash flow are built on. ## Where AI MRR comes from - A base AI service on every managed client: policy, approved tools, data protection. - Automations billed per workflow in production. - Higher tiers for clients with more to gain: assessments, roadmaps, reporting in the QBR. ## How to grow it Start with clients who already ask about AI. Price the first automations in the client’s own numbers (hours saved, errors avoided), show the result at the next QBR, and add the next workflow from there. [Score my MSP](https://www.resultsiq.ai/score/) estimates what AI MRR could be worth across your client base. [AI tools for MSPs](https://www.resultsiq.ai/ai-tools-for-msps/) [Score my MSP](https://www.resultsiq.ai/score/) [Book a call](https://www.resultsiq.ai/demo/?src=guide) --- Page: https://www.resultsiq.ai/guides/mcp-for-msps/ [Guides](https://www.resultsiq.ai/guides/) # MCP for MSPs: what it is and how to use it MCP, the Model Context Protocol, is an open standard for connecting AI assistants such as Claude and ChatGPT to other software. An MCP server gives the assistant a set of tools it can use, such as “find this client’s open tickets” or “check backup status”, so it can work with live data instead of pasted text. By [Connor Reece](https://www.resultsiq.ai/about/), updated November 2026 ## What MSPs use it for - Asking about a client in plain language: open tickets, devices, alerts, backups and licenses in one answer. - Drafting QBR summaries from real data. - Running routine checks across every client at once. ## The risks to manage An AI assistant connected to your tools can see what that connection can see. Three controls matter. The assistant acts with each person’s own permissions. Client data stays scoped to the clients that person is allowed to see. And credentials stay in a vault the AI never reads. ## One connection instead of dozens Most MSP tools now offer, or are building, their own MCP servers, so a team can end up wiring dozens of separate connections. Control Center MCP is one connection from your team’s Claude or ChatGPT to every client and every tool you run, with the same roles and client scopes as your login. [See Control Center MCP](https://www.resultsiq.ai/mcp/). [AI tools for MSPs](https://www.resultsiq.ai/ai-tools-for-msps/) [Score my MSP](https://www.resultsiq.ai/score/) [Book a call](https://www.resultsiq.ai/demo/?src=guide) --- Page: https://www.resultsiq.ai/compare/ [Guides](https://www.resultsiq.ai/guides/) # How Control Center compares Other AI platforms are built for MSPs too, and they do different jobs. Each comparison describes the other product from its own public materials, says who each one is for, and makes no claims we can’t back. ## Comparisons Last checked November 2026. - [ResultsIQ Control Center vs Hatz AI](https://www.resultsiq.ai/compare/hatz-ai/) Hatz AI gives MSP clients a secure, multi-model AI workspace. Control Center helps MSPs scope, price, build and bill AI managed services. - [ResultsIQ Control Center vs Lemhi](https://www.resultsiq.ai/compare/lemhi/) Lemhi runs structured AI engagements for MSPs, from readiness to roadmaps. Control Center adds automations and monthly billing across 156 tools. --- Page: https://www.resultsiq.ai/compare/hatz-ai/ [Compare](https://www.resultsiq.ai/compare/) # ResultsIQ Control Center vs Hatz AI Both are built for MSPs, and they do different jobs. ## What Hatz AI is Hatz AI is a secure AI platform that MSPs deliver to their clients. It gives client teams one place to use several AI models (ChatGPT, Claude, Gemini and others), with governance across the MSP’s client base, spending limits, audit logs and credit-based usage. (Source: [hatz.ai](https://www.hatz.ai/).) ## What Control Center is ResultsIQ Control Center is a platform built for MSPs to scope, price, build and bill AI managed services across the clients they already have. It finds the AI opportunities in each client’s business, prices them in the client’s numbers, builds the automations across 156 MSP tools and bills them every month. Control Center MCP connects the MSP team’s own Claude or ChatGPT to every client and tool. MSPs bring their own AI accounts and keys, with no markup on AI usage. ## The main differences Compared Hatz AI ResultsIQ Control Center Main job A governed AI workspace for client teams A service line: assess, price, automate and bill AI work Who uses it day to day The MSP’s clients The MSP’s team AI models Several models in one workspace, credit-based Your own AI accounts and keys, no markup Automations across MSP tools Agents, workflow templates and connections to MCP servers Automations and MCP across 156 PSA, RMM, security, backup and documentation tools Billing the client Usage tracking and limits Monthly invoice lines per client and workflow ## Which fits Choose Hatz AI if your goal is to give clients a safe, managed place to use AI chat. Choose Control Center if your goal is a recurring AI service line you scope, deliver and bill across your clients. Some MSPs will use both: a workspace for client users, and Control Center to run and bill the service. Last checked November 2026. Corrections: [connor.reece@resultsiq.ai](mailto:connor.reece@resultsiq.ai) [AI tools for MSPs](https://www.resultsiq.ai/ai-tools-for-msps/) [Score my MSP](https://www.resultsiq.ai/score/) [Book a call](https://www.resultsiq.ai/demo/?src=guide) --- Page: https://www.resultsiq.ai/compare/lemhi/ [Compare](https://www.resultsiq.ai/compare/) # ResultsIQ Control Center vs Lemhi Both help MSPs turn AI into recurring work. They start from different places. ## What Lemhi is Lemhi launched in June 2026 as an “AI Transformation-as-a-Service” platform built for MSPs. Its first product, Lemhi Engage, produces outputs such as workforce readiness scores, ROI plans, Microsoft 365 tenant assessments and phased rollout roadmaps with governance and success metrics. It has a listing on the ConnectWise Marketplace, where its PSA integration is ConnectWise Certified. (Sources: [Channel Insider, June 2, 2026](https://www.channelinsider.com/news-and-trends/lemhi-msp-ai-service-platform-launch/); [marketplace.connectwise.com](https://marketplace.connectwise.com/lemhi).) ## What Control Center is ResultsIQ Control Center is a platform built for MSPs to scope, price, build and bill AI managed services across the clients they already have. It covers opportunity assessments in each client’s numbers, automations across 156 MSP tools, QBR reporting and monthly invoice lines. Control Center MCP connects the MSP team’s own Claude or ChatGPT to every client and tool. ## The main differences Compared Lemhi ResultsIQ Control Center Starting point Structured AI engagements: readiness, ROI plan, roadmap Each client’s business and tools: what to automate, price and bill Microsoft 365 Microsoft 365 and Copilot signals feed its readiness score One of 156 connected tools Delivery Engagement playbooks and rollout plans Builds and runs the automations, then reports on them Billing Designed to be bundled into the MSP’s existing monthly contracts Monthly invoice lines per client and workflow ## Which fits Choose Lemhi if you want a repeatable consulting playbook for AI readiness and rollout, especially in Microsoft 365. Choose Control Center if you want the work itself (automations across your stack) delivered and billed every month. Last checked November 2026. Corrections: [connor.reece@resultsiq.ai](mailto:connor.reece@resultsiq.ai) [AI tools for MSPs](https://www.resultsiq.ai/ai-tools-for-msps/) [Score my MSP](https://www.resultsiq.ai/score/) [Book a call](https://www.resultsiq.ai/demo/?src=guide) --- Page: https://www.resultsiq.ai/score/ Score my MSP # What will your MSP be worth after AI? AI is likely to separate the MSPs that grow from the ones that shrink. Score your business on the three numbers a buyer pays for: revenue, gross margin and EBITDA. Start the score 4 min To complete it 3 Numbers scored: revenue, margin, EBITDA 0 Calls needed to see your score Take it ## Fourteen questions, about four minutes. Answer for where the business is today. Your score shows on screen as soon as you finish. Revenue 1 of 14 ### No email needed to see your score. 0 /100 #### Your two biggest gaps See what these numbers mean in dollars in [The No Brainer](https://www.resultsiq.ai/no-brainer/). [Book a call](https://www.resultsiq.ai/demo/?src=score) #### Email me the full breakdown Every answer, what each of the three scores means, and where to start. First name Last name Work email MSP name You can unsubscribe from anything we send. See our [Privacy Policy](https://www.resultsiq.ai/privacy). Why these three numbers ## AI changes the math on an MSP. Most MSP revenue is priced on seats, devices and hours. As AI automates routine support, that revenue is likely to come under price pressure, and buyers are starting to factor it in. Revenue Buyers pay for recurring growth. A new service line sold into existing clients is the quickest way to show it. Gross margin Margin slips when every new client needs another hire. Revenue that doesn’t grow with headcount lifts it. EBITDA and value Enterprise value is EBITDA times a multiple. Growth, margin and a business that runs without you are what move the multiple. Where AI fits MSPs that sell AI services can add revenue and margin to the same client base. Those that don’t may see clients buy it elsewhere. If a sale is on your horizon, the time to move these numbers is before a buyer measures them. What you get back ## Four things, with no sales call required. A score One number, with separate scores for revenue, gross margin, and EBITDA and value. The gaps, named The two things most likely holding back what your MSP is worth. Your first use case One opportunity for an MSP like yours, priced, in the 30-minute demo. A clear recommendation Including “not yet,” if that’s the right answer. ### One promise before you book. The call exists to work out whether this fits. If it does, we’ll keep talking. If it doesn’t, we’ll say so and leave it there. [Book a call](https://www.resultsiq.ai/demo/?src=site) [See the numbers in dollars](https://www.resultsiq.ai/no-brainer/) --- Page: https://www.resultsiq.ai/demo/ Book a call # Pick a time to talk. Thirty minutes with Connor Reece. Bring your questions, see Control Center live, and leave with a price for your first AI service. - On Microsoft Teams, at a time that suits you - Nothing to prepare and no slides - Not ready to talk yet? [Join the waitlist](https://www.resultsiq.ai/waitlist/) To book: give your name, work email, MSP name, number of technicians and a mobile number for the reminder, then pick a time on the calendar. Texts about the call are optional. The thirty minutes ## Here’s how it goes. 0–5 min What you sell now Your book, your stack, where your margin is. 5–20 min Control Center, live We open the product and go through one client end to end. 20–28 min Your first service line We price one opportunity for an MSP like yours, live. 28–30 min Questions Price, scope and what the ninety days asks of your team. Then you decide. #### What you won’t get A discovery form before you can see anything A slide deck about the AI revolution Three follow-up calls before a number A junior rep reading from a battlecard Who you’re talking to ## Built by MSP operators. We went looking for a way to sell AI managed services to our own clients. What we found was four products that each did a quarter of the job, and a lot of slides. So we built the one we wanted. Built by people who have run the service desk, the QBRs and the margin reviews, now applying that experience to AI. 84% of SMBs would trust an outside advisor to implement AI 13% of MSPs make meaningful revenue from it Pax8 Pulse, 400 SMB decision-makers, March 2026 · Kaseya 2026 State of the MSP Report, 1,000+ MSPs Your clients are going to buy AI services from somebody. MSPs have adapted to every technology shift for thirty years: virtualization, cloud, security. AI is the next one, and you’re already the partner who runs their infrastructure. ### Nothing to prepare. Bring your questions. It’s thirty minutes on one screen, with no deck. Pick a time [Join the waitlist](https://www.resultsiq.ai/waitlist/) --- Page: https://www.resultsiq.ai/waitlist/ Waitlist # Get Control Center first. We start reaching out to the waitlist in Q1 2027. Join now and you’re first in line. Join the waitlist at https://www.resultsiq.ai/waitlist/ with your first name, work email and MSP name. You get a note from Connor Reece the day you join, the AI MRR Playbook every two weeks, invitations to live webinars, and first access when ResultsIQ starts reaching out to the waitlist in Q1 2027. Your first 90 days of Control Center cost nothing. Straight answers ### What does it cost? $1,750 a month for the platform, plus $75 a month for each workflow you bill a client for. Your first 90 days cost nothing. [See pricing](https://www.resultsiq.ai/pricing/) ### When can I use it? We start reaching out to the waitlist in Q1 2027. Want to see it sooner? [Book a call with Connor](https://www.resultsiq.ai/demo/?src=waitlist). ### What will you send me? The AI MRR Playbook every two weeks, webinar invites, and a note when it’s your turn. Unsubscribe in one click. ### Will you sell my information? No. And we never sell to your clients. Questions first? Email me, owner to owner: [connor.reece@resultsiq.ai](mailto:connor.reece@resultsiq.ai) Connor --- Page: https://www.resultsiq.ai/integrations/ninjaone/ Integrations # AI for NinjaOne NinjaOne already knows every device, alert, patch, script and installed app at every client. Connected to Control Center, that data runs automations, morning standards checks, client reports, and answers your team gets in Claude or ChatGPT. - 10 automations - 9 standards - 6 reports - 11 MCP questions ## Automations with NinjaOne Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached NinjaOne alerts are grouped and duplicates dropped. One ConnectWise PSA ticket opens with the device, the user and the fix from IT Glue. With ConnectWise PSA and IT Glue - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through NinjaOne, and the time lands on the ConnectWise PSA ticket. With ConnectWise PSA and IT Glue - ### Failed backups handled overnight When a Datto BCDR job fails, a ConnectWise PSA ticket opens with the error, the last good backup and the device’s health from NinjaOne. With Datto BCDR and ConnectWise PSA - ### Documentation that updates itself Devices from NinjaOne and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and Microsoft 365 - ### New clients onboarded on rails A new client in ConnectWise PSA gets a checklist that tracks NinjaOne agents, SentinelOne coverage and Datto BCDR jobs until every device is done. With ConnectWise PSA, SentinelOne and Datto BCDR - ### Full disks cleaned up before anyone calls When NinjaOne flags a disk filling up, the cleanup script your team approved runs. A ConnectWise PSA ticket opens only if that doesn’t fix it. With ConnectWise PSA - ### Failed patches retried, then explained Devices that fail patching in NinjaOne get another try in the next window. If one fails again, a ConnectWise PSA ticket opens with the error and the device’s history. With ConnectWise PSA - ### Software requests installed on approval A software request in ConnectWise PSA installs through NinjaOne once a tech approves it, and the ticket closes with what was installed. With ConnectWise PSA - ### New devices set up to your standard When a new device checks in to NinjaOne, your baseline scripts run and the device is documented in IT Glue. With IT Glue - ### Broken agents reinstalled When an SentinelOne agent stops reporting, NinjaOne reinstalls it with your script once a tech approves. With SentinelOne ## Standards checked in NinjaOne Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### SentinelOne on every device Devices in NinjaOne without a healthy SentinelOne agent become a ticket. With SentinelOne - ### Patches inside your window Every device in NinjaOne, against the patch window you set. - ### Supported operating systems only Devices in NinjaOne on Windows or macOS versions past end of support. - ### Every server backed up Servers in NinjaOne with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### No stale devices or accounts Devices in NinjaOne that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Only approved software Software in NinjaOne’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in NinjaOne’s inventory that isn’t on your approved list, at every client. - ### Every device has an owner Devices in NinjaOne that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in NinjaOne that are missing from IT Glue. With IT Glue ## Reports from NinjaOne Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, NinjaOne, SentinelOne and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise PSA, SentinelOne and Datto BCDR - ### Patch compliance From NinjaOne, per device and per site. - ### Devices by age and operating system From NinjaOne, per client and per site, with the devices due for replacement. - ### Software inventory From NinjaOne, with unapproved software called out. - ### Alerts and what they cost Alert volume from NinjaOne per client, with the ConnectWise PSA time spent on them. For you, not the client. With ConnectWise PSA - ### A one-page monthly summary Tickets, devices, security and AI work from ConnectWise PSA and NinjaOne, on one page for the client’s owner. With ConnectWise PSA ## Ask about NinjaOne in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have SentinelOne?” Answered from NinjaOne and SentinelOne. - ### “What did we do for Meridian this month?” Answered from ConnectWise PSA and NinjaOne. - ### “Why does Harbor’s file server keep alerting?” Answered from NinjaOne alerts and ConnectWise PSA history. - ### “What changed at Northbridge this week?” Answered from ConnectWise PSA, NinjaOne and SentinelOne. - ### “Which servers at Northwind are low on disk space?” Answered from NinjaOne. - ### “Which patches failed at Meridian last night?” Answered from NinjaOne. - ### “Which computers still have the old VPN client?” Answered from NinjaOne’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from NinjaOne. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and NinjaOne. - ### “Draft Northbridge’s QBR.” Built from ConnectWise PSA, NinjaOne and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a NinjaOne script that a tech approves before it runs. ## What Control Center reads from NinjaOne Devices, alerts, patching, scripts and software inventory. Control Center connects to NinjaOne through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An API client app (OAuth 2.0) created in NinjaOne. The examples on this page use a stack MSPs often run with NinjaOne: ConnectWise PSA, IT Glue, Datto BCDR, Microsoft 365 and SentinelOne. Build your AI plan to see them with your own tools. [Connection details and what you need from NinjaOne](https://www.resultsiq.ai/docs/tools/ninja/) ## Questions about NinjaOne and Control Center ### Does Control Center work with NinjaOne? Yes. Control Center connects to NinjaOne through its public API and uses devices, alerts, patching, scripts and software inventory. You add it once, then choose which clients it covers. ### What can an MSP automate with NinjaOne and AI? With Control Center, 10 automations, including: alerts become one ticket, with the fix attached; known fixes run when a tech approves; failed backups handled overnight; documentation that updates itself; new clients onboarded on rails; full disks cleaned up before anyone calls. A person approves the steps that matter. ### Can I use NinjaOne with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about NinjaOne at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have SentinelOne?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for Datto RMM](https://www.resultsiq.ai/integrations/datto-rmm/) [AI for N-able N-central](https://www.resultsiq.ai/integrations/n-able-n-central/) [AI for ConnectWise Automate](https://www.resultsiq.ai/integrations/connectwise-automate/) --- Page: https://www.resultsiq.ai/integrations/connectwise-psa/ Integrations # AI for ConnectWise PSA ConnectWise PSA already holds your tickets, agreements, time entries and invoices for every client. Connected to Control Center, it is where AI work is triaged, approved, timed and billed, and where every standards gap becomes a project you can sell. - 18 automations - 3 standards - 9 reports - 10 MCP questions - 3 billing items ## Automations with ConnectWise PSA Work that runs on its own, across your tools. A person approves the steps that matter. - ### Threats triaged before a tech looks When SentinelOne flags a threat, a priority ConnectWise PSA ticket opens with who uses the device and what it can reach. With SentinelOne - ### Isolation, approved from the ticket A tech approves from the ConnectWise PSA ticket and SentinelOne isolates the device. Releasing it works the same way. With SentinelOne - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through ConnectWise Automate, and the time lands on the ConnectWise PSA ticket. With ConnectWise Automate and IT Glue - ### New hires set up from one request A request in ConnectWise PSA creates the user in Microsoft 365 with the right groups and licenses, documents them in IT Glue and closes the ticket. With Microsoft 365 and IT Glue - ### Offboarding that misses nothing One ConnectWise PSA ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step. With Microsoft 365 - ### Failed backups handled overnight When a Datto BCDR job fails, a ConnectWise PSA ticket opens with the error, the last good backup and the device’s health from ConnectWise Automate. With Datto BCDR and ConnectWise Automate - ### Missed time entries caught daily Tickets with work but no time in ConnectWise PSA are flagged to the tech each afternoon. - ### Every ticket triaged and routed New ConnectWise PSA tickets are categorized, prioritized and routed, with the client’s business context attached. - ### Agreements and invoices reconciled ConnectWise PSA agreements are checked against QuickBooks invoices every month, and anything unbilled is flagged. QB With QuickBooks Online - ### New clients onboarded on rails A new client in ConnectWise PSA gets a checklist that tracks ConnectWise Automate agents, SentinelOne coverage and Datto BCDR jobs until every device is done. With ConnectWise Automate, SentinelOne and Datto BCDR - ### Failed patches retried, then explained Devices that fail patching in ConnectWise Automate get another try in the next window. If one fails again, a ConnectWise PSA ticket opens with the error and the device’s history. With ConnectWise Automate - ### Software requests installed on approval A software request in ConnectWise PSA installs through ConnectWise Automate once a tech approves it, and the ticket closes with what was installed. With ConnectWise Automate - ### Password resets handled from the ticket A reset request in ConnectWise PSA is done in Microsoft 365 once a tech approves it, and the ticket closes itself. With Microsoft 365 - ### Risky sign-ins investigated A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a ConnectWise PSA ticket with the user’s recent activity. With Microsoft 365 - ### MFA gaps turned into tickets Users in Microsoft 365 without MFA open one ConnectWise PSA ticket per client, with the list attached. With Microsoft 365 - ### Failed restore tests caught early When a Datto BCDR restore check fails, a ConnectWise PSA ticket opens before anyone needs that backup. With Datto BCDR - ### QBR action items become tickets Every action item agreed in a QBR becomes a ConnectWise PSA ticket or project, with an owner and a date. - ### Threats remediated on approval A tech approves remediation from the ConnectWise PSA ticket, and SentinelOne cleans up the device. With SentinelOne ## Standards checked in ConnectWise PSA Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Every client on a current agreement Clients in ConnectWise PSA with an expired or missing agreement. - ### Leavers fully removed Accounts in Microsoft 365 still enabled for people offboarded through ConnectWise PSA. With Microsoft 365 - ### Tickets closed properly ConnectWise PSA tickets closed without notes or time, by tech. For you, not the client. ## Reports from ConnectWise PSA Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, ConnectWise Automate, SentinelOne and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise Automate, SentinelOne and Datto BCDR - ### Service desk, in business terms Ticket volume, response times and repeat issues from ConnectWise PSA, explained by what they cost the client. - ### Your margin on every client Hours in ConnectWise PSA against revenue in QuickBooks. For you, not the client. QB With QuickBooks Online - ### Response and resolution against your SLA From ConnectWise PSA, per client and per priority. - ### Where the tickets come from Tickets from ConnectWise PSA by person and by issue, so you fix the cause, not the symptom. - ### What AI did this month Every AI service’s runs, hours returned and value, ready for the client’s QBR. - ### Standards scorecard Every standard you check, passed or failed at each client, with each gap priced as a ConnectWise PSA project. - ### A one-page monthly summary Tickets, devices, security and AI work from ConnectWise PSA and ConnectWise Automate, on one page for the client’s owner. With ConnectWise Automate - ### Any report you can describe Describe it in a sentence. Control Center builds it from ConnectWise PSA and your other connected tools, then sends it on a schedule. ## Ask about ConnectWise PSA in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “What did we do for Meridian this month?” Answered from ConnectWise PSA and ConnectWise Automate. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and ConnectWise PSA. - ### “What changed at Northbridge this week?” Answered from ConnectWise PSA, ConnectWise Automate and SentinelOne. - ### “Turn that into an automation.” Any answer can become a workflow, and a person approves it before it runs. - ### “Has this happened at Harbor before? What fixed it?” Answered from ConnectWise PSA ticket history and IT Glue. - ### “What’s left on Meridian’s onboarding?” Answered from ConnectWise PSA and IT Glue. - ### “What work did we do this month that we didn’t bill?” Answered from ConnectWise PSA time entries and agreements. - ### “Which clients made us the least per hour this quarter?” Answered from ConnectWise PSA and QuickBooks. - ### “Whose agreement renews next quarter, and what should we add to it?” Answered from ConnectWise PSA agreements and each client’s AI roadmap. - ### “Draft Northbridge’s QBR.” Built from ConnectWise PSA, ConnectWise Automate and every other connected tool, for your vCIO to edit. ## Billing with ConnectWise PSA Get paid for the AI work, through the tools you bill with. - ### AI services on the ConnectWise PSA agreement Every AI service you sell is added to the client’s agreement and billed each month, at your margin. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the ConnectWise PSA agreement, with missed billing flagged. With Microsoft 365 - ### Every AI run metered Usage per client and per workflow, behind every line you bill. ## What Control Center reads from ConnectWise PSA Tickets, agreements, billing and time entries. Control Center connects to ConnectWise PSA through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: The docs need a ConnectWise Developer Network account, which ConnectWise approves. The examples on this page use a stack MSPs often run with ConnectWise PSA: SentinelOne, ConnectWise Automate, IT Glue, Microsoft 365, Datto BCDR and QuickBooks Online. Build your AI plan to see them with your own tools. [Connection details and what you need from ConnectWise PSA](https://www.resultsiq.ai/docs/tools/cwpsa/) ## Questions about ConnectWise PSA and Control Center ### Does Control Center work with ConnectWise PSA? Yes. Control Center connects to ConnectWise PSA through its public API and uses tickets, agreements, billing and time entries. You add it once, then choose which clients it covers. ### What can an MSP automate with ConnectWise PSA and AI? With Control Center, 18 automations, including: threats triaged before a tech looks; isolation, approved from the ticket; known fixes run when a tech approves; new hires set up from one request; offboarding that misses nothing; failed backups handled overnight. A person approves the steps that matter. ### Can I use ConnectWise PSA with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about ConnectWise PSA at every client, with the same roles and client scopes as their login. For example: “What did we do for Meridian this month?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for Autotask PSA](https://www.resultsiq.ai/integrations/autotask/) [AI for HaloPSA](https://www.resultsiq.ai/integrations/halopsa/) [AI for Syncro](https://www.resultsiq.ai/integrations/syncro/) --- Page: https://www.resultsiq.ai/integrations/autotask/ Integrations # AI for Autotask PSA Autotask already tracks your tickets, contracts and time for every client. Connected to Control Center, every automation, report and approval runs through it, and every AI service you sell is billed through it each month. - 19 automations - 3 standards - 10 reports - 11 MCP questions - 3 billing items ## Automations with Autotask PSA Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached Datto RMM alerts are grouped and duplicates dropped. One Autotask ticket opens with the device, the user and the fix from IT Glue. With Datto RMM and IT Glue - ### Threats triaged before a tech looks When Datto EDR flags a threat, a priority Autotask ticket opens with who uses the device and what it can reach. With Datto EDR - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through Datto RMM, and the time lands on the Autotask ticket. With Datto RMM and IT Glue - ### New hires set up from one request A request in Autotask creates the user in Microsoft 365 with the right groups and licenses, documents them in IT Glue and closes the ticket. With Microsoft 365 and IT Glue - ### Offboarding that misses nothing One Autotask ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step. With Microsoft 365 - ### Failed backups handled overnight When a Datto BCDR job fails, a Autotask ticket opens with the error, the last good backup and the device’s health from Datto RMM. With Datto BCDR and Datto RMM - ### Missed time entries caught daily Tickets with work but no time in Autotask are flagged to the tech each afternoon. - ### Every ticket triaged and routed New Autotask tickets are categorized, prioritized and routed, with the client’s business context attached. - ### Agreements and invoices reconciled Autotask agreements are checked against QuickBooks invoices every month, and anything unbilled is flagged. QB With QuickBooks Online - ### New clients onboarded on rails A new client in Autotask gets a checklist that tracks Datto RMM agents, Datto EDR coverage and Datto BCDR jobs until every device is done. With Datto RMM, Datto EDR and Datto BCDR - ### Full disks cleaned up before anyone calls When Datto RMM flags a disk filling up, the cleanup script your team approved runs. A Autotask ticket opens only if that doesn’t fix it. With Datto RMM - ### Failed patches retried, then explained Devices that fail patching in Datto RMM get another try in the next window. If one fails again, a Autotask ticket opens with the error and the device’s history. With Datto RMM - ### Software requests installed on approval A software request in Autotask installs through Datto RMM once a tech approves it, and the ticket closes with what was installed. With Datto RMM - ### Password resets handled from the ticket A reset request in Autotask is done in Microsoft 365 once a tech approves it, and the ticket closes itself. With Microsoft 365 - ### Risky sign-ins investigated A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a Autotask ticket with the user’s recent activity. With Microsoft 365 - ### MFA gaps turned into tickets Users in Microsoft 365 without MFA open one Autotask ticket per client, with the list attached. With Microsoft 365 - ### Failed restore tests caught early When a Datto BCDR restore check fails, a Autotask ticket opens before anyone needs that backup. With Datto BCDR - ### QBR action items become tickets Every action item agreed in a QBR becomes a Autotask ticket or project, with an owner and a date. - ### Threats remediated on approval A tech approves remediation from the Autotask ticket, and Datto EDR cleans up the device. With Datto EDR ## Standards checked in Autotask PSA Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Every client on a current agreement Clients in Autotask with an expired or missing agreement. - ### Leavers fully removed Accounts in Microsoft 365 still enabled for people offboarded through Autotask. With Microsoft 365 - ### Tickets closed properly Autotask tickets closed without notes or time, by tech. For you, not the client. ## Reports from Autotask PSA Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted Autotask, Datto RMM, Datto EDR and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With Datto RMM, Datto EDR and Datto BCDR - ### Service desk, in business terms Ticket volume, response times and repeat issues from Autotask, explained by what they cost the client. - ### Your margin on every client Hours in Autotask against revenue in QuickBooks. For you, not the client. QB With QuickBooks Online - ### Alerts and what they cost Alert volume from Datto RMM per client, with the Autotask time spent on them. For you, not the client. With Datto RMM - ### Response and resolution against your SLA From Autotask, per client and per priority. - ### Where the tickets come from Tickets from Autotask by person and by issue, so you fix the cause, not the symptom. - ### What AI did this month Every AI service’s runs, hours returned and value, ready for the client’s QBR. - ### Standards scorecard Every standard you check, passed or failed at each client, with each gap priced as a Autotask project. - ### A one-page monthly summary Tickets, devices, security and AI work from Autotask and Datto RMM, on one page for the client’s owner. With Datto RMM - ### Any report you can describe Describe it in a sentence. Control Center builds it from Autotask and your other connected tools, then sends it on a schedule. ## Ask about Autotask PSA in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “What did we do for Meridian this month?” Answered from Autotask and Datto RMM. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and Autotask. - ### “Why does Harbor’s file server keep alerting?” Answered from Datto RMM alerts and Autotask history. - ### “What changed at Northbridge this week?” Answered from Autotask, Datto RMM and Datto EDR. - ### “Turn that into an automation.” Any answer can become a workflow, and a person approves it before it runs. - ### “Has this happened at Harbor before? What fixed it?” Answered from Autotask ticket history and IT Glue. - ### “What’s left on Meridian’s onboarding?” Answered from Autotask and IT Glue. - ### “What work did we do this month that we didn’t bill?” Answered from Autotask time entries and agreements. - ### “Which clients made us the least per hour this quarter?” Answered from Autotask and QuickBooks. - ### “Whose agreement renews next quarter, and what should we add to it?” Answered from Autotask agreements and each client’s AI roadmap. - ### “Draft Northbridge’s QBR.” Built from Autotask, Datto RMM and every other connected tool, for your vCIO to edit. ## Billing with Autotask PSA Get paid for the AI work, through the tools you bill with. - ### AI services on the Autotask agreement Every AI service you sell is added to the client’s agreement and billed each month, at your margin. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the Autotask agreement, with missed billing flagged. With Microsoft 365 - ### Every AI run metered Usage per client and per workflow, behind every line you bill. ## What Control Center reads from Autotask PSA Tickets, agreements, billing and time entries. Control Center connects to Autotask PSA through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An API user created in Autotask. The API address depends on your Autotask zone. The examples on this page use a stack MSPs often run with Autotask PSA: Datto RMM, IT Glue, Datto EDR, Microsoft 365, Datto BCDR and QuickBooks Online. Build your AI plan to see them with your own tools. [Connection details and what you need from Autotask PSA](https://www.resultsiq.ai/docs/tools/autotask/) ## Questions about Autotask PSA and Control Center ### Does Control Center work with Autotask PSA? Yes. Control Center connects to Autotask PSA through its public API and uses tickets, agreements, billing and time entries. You add it once, then choose which clients it covers. ### What can an MSP automate with Autotask PSA and AI? With Control Center, 19 automations, including: alerts become one ticket, with the fix attached; threats triaged before a tech looks; known fixes run when a tech approves; new hires set up from one request; offboarding that misses nothing; failed backups handled overnight. A person approves the steps that matter. ### Can I use Autotask PSA with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Autotask PSA at every client, with the same roles and client scopes as their login. For example: “What did we do for Meridian this month?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for HaloPSA](https://www.resultsiq.ai/integrations/halopsa/) [AI for Syncro](https://www.resultsiq.ai/integrations/syncro/) --- Page: https://www.resultsiq.ai/integrations/halopsa/ Integrations # AI for HaloPSA HaloPSA already holds your tickets, contracts, time and invoices. Connected to Control Center, it is where AI triages and routes tickets, where your team approves the work, and where every AI service you sell gets billed. - 20 automations - 3 standards - 10 reports - 11 MCP questions - 3 billing items ## Automations with HaloPSA Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached NinjaOne alerts are grouped and duplicates dropped. One HaloPSA ticket opens with the device, the user and the fix from Hudu. With NinjaOne and Hudu - ### Threats triaged before a tech looks When Huntress flags a threat, a priority HaloPSA ticket opens with who uses the device and what it can reach. With Huntress - ### Isolation, approved from the ticket A tech approves from the HaloPSA ticket and Huntress isolates the device. Releasing it works the same way. With Huntress - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in Hudu runs through NinjaOne, and the time lands on the HaloPSA ticket. With NinjaOne and Hudu - ### New hires set up from one request A request in HaloPSA creates the user in Microsoft 365 with the right groups and licenses, documents them in Hudu and closes the ticket. With Microsoft 365 and Hudu - ### Offboarding that misses nothing One HaloPSA ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step. With Microsoft 365 - ### Failed backups handled overnight When a Datto BCDR job fails, a HaloPSA ticket opens with the error, the last good backup and the device’s health from NinjaOne. With Datto BCDR and NinjaOne - ### Missed time entries caught daily Tickets with work but no time in HaloPSA are flagged to the tech each afternoon. - ### Every ticket triaged and routed New HaloPSA tickets are categorized, prioritized and routed, with the client’s business context attached. - ### Agreements and invoices reconciled HaloPSA agreements are checked against Xero invoices every month, and anything unbilled is flagged. With Xero - ### New clients onboarded on rails A new client in HaloPSA gets a checklist that tracks NinjaOne agents, Huntress coverage and Datto BCDR jobs until every device is done. With NinjaOne, Huntress and Datto BCDR - ### Full disks cleaned up before anyone calls When NinjaOne flags a disk filling up, the cleanup script your team approved runs. A HaloPSA ticket opens only if that doesn’t fix it. With NinjaOne - ### Failed patches retried, then explained Devices that fail patching in NinjaOne get another try in the next window. If one fails again, a HaloPSA ticket opens with the error and the device’s history. With NinjaOne - ### Software requests installed on approval A software request in HaloPSA installs through NinjaOne once a tech approves it, and the ticket closes with what was installed. With NinjaOne - ### Password resets handled from the ticket A reset request in HaloPSA is done in Microsoft 365 once a tech approves it, and the ticket closes itself. With Microsoft 365 - ### Risky sign-ins investigated A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a HaloPSA ticket with the user’s recent activity. With Microsoft 365 - ### MFA gaps turned into tickets Users in Microsoft 365 without MFA open one HaloPSA ticket per client, with the list attached. With Microsoft 365 - ### Failed restore tests caught early When a Datto BCDR restore check fails, a HaloPSA ticket opens before anyone needs that backup. With Datto BCDR - ### QBR action items become tickets Every action item agreed in a QBR becomes a HaloPSA ticket or project, with an owner and a date. - ### Threats remediated on approval A tech approves remediation from the HaloPSA ticket, and Huntress cleans up the device. With Huntress ## Standards checked in HaloPSA Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Every client on a current agreement Clients in HaloPSA with an expired or missing agreement. - ### Leavers fully removed Accounts in Microsoft 365 still enabled for people offboarded through HaloPSA. With Microsoft 365 - ### Tickets closed properly HaloPSA tickets closed without notes or time, by tech. For you, not the client. ## Reports from HaloPSA Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted HaloPSA, NinjaOne, Huntress and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With NinjaOne, Huntress and Datto BCDR - ### Service desk, in business terms Ticket volume, response times and repeat issues from HaloPSA, explained by what they cost the client. - ### Your margin on every client Hours in HaloPSA against revenue in Xero. For you, not the client. With Xero - ### Alerts and what they cost Alert volume from NinjaOne per client, with the HaloPSA time spent on them. For you, not the client. With NinjaOne - ### Response and resolution against your SLA From HaloPSA, per client and per priority. - ### Where the tickets come from Tickets from HaloPSA by person and by issue, so you fix the cause, not the symptom. - ### What AI did this month Every AI service’s runs, hours returned and value, ready for the client’s QBR. - ### Standards scorecard Every standard you check, passed or failed at each client, with each gap priced as a HaloPSA project. - ### A one-page monthly summary Tickets, devices, security and AI work from HaloPSA and NinjaOne, on one page for the client’s owner. With NinjaOne - ### Any report you can describe Describe it in a sentence. Control Center builds it from HaloPSA and your other connected tools, then sends it on a schedule. ## Ask about HaloPSA in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “What did we do for Meridian this month?” Answered from HaloPSA and NinjaOne. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and HaloPSA. - ### “Why does Harbor’s file server keep alerting?” Answered from NinjaOne alerts and HaloPSA history. - ### “What changed at Northbridge this week?” Answered from HaloPSA, NinjaOne and Huntress. - ### “Turn that into an automation.” Any answer can become a workflow, and a person approves it before it runs. - ### “Has this happened at Harbor before? What fixed it?” Answered from HaloPSA ticket history and Hudu. - ### “What’s left on Meridian’s onboarding?” Answered from HaloPSA and Hudu. - ### “What work did we do this month that we didn’t bill?” Answered from HaloPSA time entries and agreements. - ### “Which clients made us the least per hour this quarter?” Answered from HaloPSA and Xero. - ### “Whose agreement renews next quarter, and what should we add to it?” Answered from HaloPSA agreements and each client’s AI roadmap. - ### “Draft Northbridge’s QBR.” Built from HaloPSA, NinjaOne and every other connected tool, for your vCIO to edit. ## Billing with HaloPSA Get paid for the AI work, through the tools you bill with. - ### AI services on the HaloPSA agreement Every AI service you sell is added to the client’s agreement and billed each month, at your margin. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the HaloPSA agreement, with missed billing flagged. With Microsoft 365 - ### Every AI run metered Usage per client and per workflow, behind every line you bill. ## What Control Center reads from HaloPSA Tickets, agreements, billing and time entries. Control Center connects to HaloPSA through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An API application registered in HaloPSA (client ID and secret). Addresses are specific to your instance. The examples on this page use a stack MSPs often run with HaloPSA: NinjaOne, Hudu, Huntress, Microsoft 365, Datto BCDR and Xero. Build your AI plan to see them with your own tools. [Connection details and what you need from HaloPSA](https://www.resultsiq.ai/docs/tools/halo/) ## Questions about HaloPSA and Control Center ### Does Control Center work with HaloPSA? Yes. Control Center connects to HaloPSA through its public API and uses tickets, agreements, billing and time entries. You add it once, then choose which clients it covers. ### What can an MSP automate with HaloPSA and AI? With Control Center, 20 automations, including: alerts become one ticket, with the fix attached; threats triaged before a tech looks; isolation, approved from the ticket; known fixes run when a tech approves; new hires set up from one request; offboarding that misses nothing. A person approves the steps that matter. ### Can I use HaloPSA with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about HaloPSA at every client, with the same roles and client scopes as their login. For example: “What did we do for Meridian this month?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for Autotask PSA](https://www.resultsiq.ai/integrations/autotask/) [AI for Syncro](https://www.resultsiq.ai/integrations/syncro/) --- Page: https://www.resultsiq.ai/integrations/datto-rmm/ Integrations # AI for Datto RMM Datto RMM already knows every device, alert, patch, component and installed app across your clients. Connected to Control Center, that data runs automations, morning standards checks, client reports, and answers your team gets in Claude or ChatGPT. - 10 automations - 9 standards - 6 reports - 11 MCP questions ## Automations with Datto RMM Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached Datto RMM alerts are grouped and duplicates dropped. One Autotask ticket opens with the device, the user and the fix from IT Glue. With Autotask PSA and IT Glue - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through Datto RMM, and the time lands on the Autotask ticket. With Autotask PSA and IT Glue - ### Failed backups handled overnight When a Datto BCDR job fails, a Autotask ticket opens with the error, the last good backup and the device’s health from Datto RMM. With Datto BCDR and Autotask PSA - ### Documentation that updates itself Devices from Datto RMM and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and Microsoft 365 - ### New clients onboarded on rails A new client in Autotask gets a checklist that tracks Datto RMM agents, Datto EDR coverage and Datto BCDR jobs until every device is done. With Autotask PSA, Datto EDR and Datto BCDR - ### Full disks cleaned up before anyone calls When Datto RMM flags a disk filling up, the cleanup script your team approved runs. A Autotask ticket opens only if that doesn’t fix it. With Autotask PSA - ### Failed patches retried, then explained Devices that fail patching in Datto RMM get another try in the next window. If one fails again, a Autotask ticket opens with the error and the device’s history. With Autotask PSA - ### Software requests installed on approval A software request in Autotask installs through Datto RMM once a tech approves it, and the ticket closes with what was installed. With Autotask PSA - ### New devices set up to your standard When a new device checks in to Datto RMM, your baseline scripts run and the device is documented in IT Glue. With IT Glue - ### Broken agents reinstalled When an Datto EDR agent stops reporting, Datto RMM reinstalls it with your script once a tech approves. With Datto EDR ## Standards checked in Datto RMM Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Datto EDR on every device Devices in Datto RMM without a healthy Datto EDR agent become a ticket. With Datto EDR - ### Patches inside your window Every device in Datto RMM, against the patch window you set. - ### Supported operating systems only Devices in Datto RMM on Windows or macOS versions past end of support. - ### Every server backed up Servers in Datto RMM with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### No stale devices or accounts Devices in Datto RMM that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Only approved software Software in Datto RMM’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in Datto RMM’s inventory that isn’t on your approved list, at every client. - ### Every device has an owner Devices in Datto RMM that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in Datto RMM that are missing from IT Glue. With IT Glue ## Reports from Datto RMM Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted Autotask, Datto RMM, Datto EDR and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With Autotask PSA, Datto EDR and Datto BCDR - ### Patch compliance From Datto RMM, per device and per site. - ### Devices by age and operating system From Datto RMM, per client and per site, with the devices due for replacement. - ### Software inventory From Datto RMM, with unapproved software called out. - ### Alerts and what they cost Alert volume from Datto RMM per client, with the Autotask time spent on them. For you, not the client. With Autotask PSA - ### A one-page monthly summary Tickets, devices, security and AI work from Autotask and Datto RMM, on one page for the client’s owner. With Autotask PSA ## Ask about Datto RMM in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have Datto EDR?” Answered from Datto RMM and Datto EDR. - ### “What did we do for Meridian this month?” Answered from Autotask and Datto RMM. - ### “Why does Harbor’s file server keep alerting?” Answered from Datto RMM alerts and Autotask history. - ### “What changed at Northbridge this week?” Answered from Autotask, Datto RMM and Datto EDR. - ### “Which servers at Northwind are low on disk space?” Answered from Datto RMM. - ### “Which patches failed at Meridian last night?” Answered from Datto RMM. - ### “Which computers still have the old VPN client?” Answered from Datto RMM’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from Datto RMM. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and Datto RMM. - ### “Draft Northbridge’s QBR.” Built from Autotask, Datto RMM and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a Datto RMM script that a tech approves before it runs. ## What Control Center reads from Datto RMM Devices, alerts, patching, scripts and software inventory. Control Center connects to Datto RMM through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: Turn on API access in Global Settings. Each user gets their own keys, and the address depends on your Datto RMM platform. The examples on this page use a stack MSPs often run with Datto RMM: Autotask PSA, IT Glue, Datto BCDR, Microsoft 365 and Datto EDR. Build your AI plan to see them with your own tools. [Connection details and what you need from Datto RMM](https://www.resultsiq.ai/docs/tools/dattormm/) ## Questions about Datto RMM and Control Center ### Does Control Center work with Datto RMM? Yes. Control Center connects to Datto RMM through its public API and uses devices, alerts, patching, scripts and software inventory. You add it once, then choose which clients it covers. ### What can an MSP automate with Datto RMM and AI? With Control Center, 10 automations, including: alerts become one ticket, with the fix attached; known fixes run when a tech approves; failed backups handled overnight; documentation that updates itself; new clients onboarded on rails; full disks cleaned up before anyone calls. A person approves the steps that matter. ### Can I use Datto RMM with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Datto RMM at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have Datto EDR?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) [AI for N-able N-central](https://www.resultsiq.ai/integrations/n-able-n-central/) [AI for ConnectWise Automate](https://www.resultsiq.ai/integrations/connectwise-automate/) --- Page: https://www.resultsiq.ai/integrations/n-able-n-central/ Integrations # AI for N-able N-central N-central already monitors every device, patch and script across your clients. Connected to Control Center, alerts become one ticket with the fix attached, your standards are checked every morning, and your team can ask about any device in Claude or ChatGPT. - 10 automations - 9 standards - 6 reports - 11 MCP questions ## Automations with N-able N-central Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached N-central alerts are grouped and duplicates dropped. One ConnectWise PSA ticket opens with the device, the user and the fix from IT Glue. With ConnectWise PSA and IT Glue - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through N-central, and the time lands on the ConnectWise PSA ticket. With ConnectWise PSA and IT Glue - ### Failed backups handled overnight When a Cove job fails, a ConnectWise PSA ticket opens with the error, the last good backup and the device’s health from N-central. With Cove Data Protection and ConnectWise PSA - ### Documentation that updates itself Devices from N-central and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and Microsoft 365 - ### New clients onboarded on rails A new client in ConnectWise PSA gets a checklist that tracks N-central agents, SentinelOne coverage and Cove jobs until every device is done. With ConnectWise PSA, SentinelOne and Cove Data Protection - ### Full disks cleaned up before anyone calls When N-central flags a disk filling up, the cleanup script your team approved runs. A ConnectWise PSA ticket opens only if that doesn’t fix it. With ConnectWise PSA - ### Failed patches retried, then explained Devices that fail patching in N-central get another try in the next window. If one fails again, a ConnectWise PSA ticket opens with the error and the device’s history. With ConnectWise PSA - ### Software requests installed on approval A software request in ConnectWise PSA installs through N-central once a tech approves it, and the ticket closes with what was installed. With ConnectWise PSA - ### New devices set up to your standard When a new device checks in to N-central, your baseline scripts run and the device is documented in IT Glue. With IT Glue - ### Broken agents reinstalled When an SentinelOne agent stops reporting, N-central reinstalls it with your script once a tech approves. With SentinelOne ## Standards checked in N-able N-central Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### SentinelOne on every device Devices in N-central without a healthy SentinelOne agent become a ticket. With SentinelOne - ### Patches inside your window Every device in N-central, against the patch window you set. - ### Supported operating systems only Devices in N-central on Windows or macOS versions past end of support. - ### Every server backed up Servers in N-central with no Cove backup, or none that finished in the last 24 hours. With Cove Data Protection - ### No stale devices or accounts Devices in N-central that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Only approved software Software in N-central’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in N-central’s inventory that isn’t on your approved list, at every client. - ### Every device has an owner Devices in N-central that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in N-central that are missing from IT Glue. With IT Glue ## Reports from N-able N-central Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, N-central, SentinelOne and Cove in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise PSA, SentinelOne and Cove Data Protection - ### Patch compliance From N-central, per device and per site. - ### Devices by age and operating system From N-central, per client and per site, with the devices due for replacement. - ### Software inventory From N-central, with unapproved software called out. - ### Alerts and what they cost Alert volume from N-central per client, with the ConnectWise PSA time spent on them. For you, not the client. With ConnectWise PSA - ### A one-page monthly summary Tickets, devices, security and AI work from ConnectWise PSA and N-central, on one page for the client’s owner. With ConnectWise PSA ## Ask about N-able N-central in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have SentinelOne?” Answered from N-central and SentinelOne. - ### “What did we do for Meridian this month?” Answered from ConnectWise PSA and N-central. - ### “Why does Harbor’s file server keep alerting?” Answered from N-central alerts and ConnectWise PSA history. - ### “What changed at Northbridge this week?” Answered from ConnectWise PSA, N-central and SentinelOne. - ### “Which servers at Northwind are low on disk space?” Answered from N-central. - ### “Which patches failed at Meridian last night?” Answered from N-central. - ### “Which computers still have the old VPN client?” Answered from N-central’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from N-central. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and N-central. - ### “Draft Northbridge’s QBR.” Built from ConnectWise PSA, N-central and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a N-central script that a tech approves before it runs. ## What Control Center reads from N-able N-central Devices, alerts, patching, scripts and software inventory. Control Center connects to N-able N-central through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An API-only user and its token, created in N-central. The examples on this page use a stack MSPs often run with N-able N-central: ConnectWise PSA, IT Glue, Cove Data Protection, Microsoft 365 and SentinelOne. Build your AI plan to see them with your own tools. [Connection details and what you need from N-able N-central](https://www.resultsiq.ai/docs/tools/ncentral/) ## Questions about N-able N-central and Control Center ### Does Control Center work with N-able N-central? Yes. Control Center connects to N-able N-central through its public API and uses devices, alerts, patching, scripts and software inventory. You add it once, then choose which clients it covers. ### What can an MSP automate with N-able N-central and AI? With Control Center, 10 automations, including: alerts become one ticket, with the fix attached; known fixes run when a tech approves; failed backups handled overnight; documentation that updates itself; new clients onboarded on rails; full disks cleaned up before anyone calls. A person approves the steps that matter. ### Can I use N-able N-central with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about N-able N-central at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have SentinelOne?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) [AI for Datto RMM](https://www.resultsiq.ai/integrations/datto-rmm/) [AI for ConnectWise Automate](https://www.resultsiq.ai/integrations/connectwise-automate/) --- Page: https://www.resultsiq.ai/integrations/connectwise-automate/ Integrations # AI for ConnectWise Automate ConnectWise Automate already manages every device, patch and script across your clients. Connected to Control Center, the fixes your team approves run through it, patching is held to your standard, and your team can ask about any device in Claude or ChatGPT. - 8 automations - 7 standards - 4 reports - 9 MCP questions ## Automations with ConnectWise Automate Work that runs on its own, across your tools. A person approves the steps that matter. - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through ConnectWise Automate, and the time lands on the ConnectWise PSA ticket. With ConnectWise PSA and IT Glue - ### Failed backups handled overnight When a Datto BCDR job fails, a ConnectWise PSA ticket opens with the error, the last good backup and the device’s health from ConnectWise Automate. With Datto BCDR and ConnectWise PSA - ### Documentation that updates itself Devices from ConnectWise Automate and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and Microsoft 365 - ### New clients onboarded on rails A new client in ConnectWise PSA gets a checklist that tracks ConnectWise Automate agents, SentinelOne coverage and Datto BCDR jobs until every device is done. With ConnectWise PSA, SentinelOne and Datto BCDR - ### Failed patches retried, then explained Devices that fail patching in ConnectWise Automate get another try in the next window. If one fails again, a ConnectWise PSA ticket opens with the error and the device’s history. With ConnectWise PSA - ### Software requests installed on approval A software request in ConnectWise PSA installs through ConnectWise Automate once a tech approves it, and the ticket closes with what was installed. With ConnectWise PSA - ### New devices set up to your standard When a new device checks in to ConnectWise Automate, your baseline scripts run and the device is documented in IT Glue. With IT Glue - ### Broken agents reinstalled When an SentinelOne agent stops reporting, ConnectWise Automate reinstalls it with your script once a tech approves. With SentinelOne ## Standards checked in ConnectWise Automate Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### SentinelOne on every device Devices in ConnectWise Automate without a healthy SentinelOne agent become a ticket. With SentinelOne - ### Patches inside your window Every device in ConnectWise Automate, against the patch window you set. - ### Supported operating systems only Devices in ConnectWise Automate on Windows or macOS versions past end of support. - ### Every server backed up Servers in ConnectWise Automate with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### No stale devices or accounts Devices in ConnectWise Automate that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Every device has an owner Devices in ConnectWise Automate that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in ConnectWise Automate that are missing from IT Glue. With IT Glue ## Reports from ConnectWise Automate Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, ConnectWise Automate, SentinelOne and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise PSA, SentinelOne and Datto BCDR - ### Patch compliance From ConnectWise Automate, per device and per site. - ### Devices by age and operating system From ConnectWise Automate, per client and per site, with the devices due for replacement. - ### A one-page monthly summary Tickets, devices, security and AI work from ConnectWise PSA and ConnectWise Automate, on one page for the client’s owner. With ConnectWise PSA ## Ask about ConnectWise Automate in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have SentinelOne?” Answered from ConnectWise Automate and SentinelOne. - ### “What did we do for Meridian this month?” Answered from ConnectWise PSA and ConnectWise Automate. - ### “What changed at Northbridge this week?” Answered from ConnectWise PSA, ConnectWise Automate and SentinelOne. - ### “Which servers at Northwind are low on disk space?” Answered from ConnectWise Automate. - ### “Which patches failed at Meridian last night?” Answered from ConnectWise Automate. - ### “Which devices haven’t checked in this week?” Answered from ConnectWise Automate. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and ConnectWise Automate. - ### “Draft Northbridge’s QBR.” Built from ConnectWise PSA, ConnectWise Automate and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a ConnectWise Automate script that a tech approves before it runs. ## What Control Center reads from ConnectWise Automate Devices, patching and scripts. Control Center connects to ConnectWise Automate through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: The docs need a ConnectWise Developer Network account, which ConnectWise approves. The examples on this page use a stack MSPs often run with ConnectWise Automate: ConnectWise PSA, IT Glue, Datto BCDR, Microsoft 365 and SentinelOne. Build your AI plan to see them with your own tools. [Connection details and what you need from ConnectWise Automate](https://www.resultsiq.ai/docs/tools/automate/) ## Questions about ConnectWise Automate and Control Center ### Does Control Center work with ConnectWise Automate? Yes. Control Center connects to ConnectWise Automate through its public API and uses devices, patching and scripts. You add it once, then choose which clients it covers. ### What can an MSP automate with ConnectWise Automate and AI? With Control Center, 8 automations, including: known fixes run when a tech approves; failed backups handled overnight; documentation that updates itself; new clients onboarded on rails; failed patches retried, then explained; software requests installed on approval. A person approves the steps that matter. ### Can I use ConnectWise Automate with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about ConnectWise Automate at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have SentinelOne?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) [AI for Datto RMM](https://www.resultsiq.ai/integrations/datto-rmm/) [AI for N-able N-central](https://www.resultsiq.ai/integrations/n-able-n-central/) --- Page: https://www.resultsiq.ai/integrations/it-glue/ Integrations # AI for IT Glue IT Glue holds the documentation and passwords your team relies on. Connected to Control Center, devices and users sync into it every night, the fixes your team wrote there run when a tech approves, and anyone on your team can ask about a client’s setup in Claude or ChatGPT. - 7 automations - 3 standards - 1 report - 4 MCP questions ## Automations with IT Glue Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached NinjaOne alerts are grouped and duplicates dropped. One ConnectWise PSA ticket opens with the device, the user and the fix from IT Glue. With NinjaOne and ConnectWise PSA - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through NinjaOne, and the time lands on the ConnectWise PSA ticket. With NinjaOne and ConnectWise PSA - ### New hires set up from one request A request in ConnectWise PSA creates the user in Microsoft 365 with the right groups and licenses, documents them in IT Glue and closes the ticket. With ConnectWise PSA and Microsoft 365 - ### Site down, details ready When Meraki reports a site offline, a ConnectWise PSA ticket opens with the circuit, the ISP’s number and the site contact from IT Glue. With Cisco Meraki and ConnectWise PSA - ### Documentation that updates itself Devices from NinjaOne and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With NinjaOne and Microsoft 365 - ### New devices set up to your standard When a new device checks in to NinjaOne, your baseline scripts run and the device is documented in IT Glue. With NinjaOne - ### Firewall configs documented every night Meraki configurations are saved to IT Glue every night, with changes highlighted. With Cisco Meraki ## Standards checked in IT Glue Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Shared passwords rotated Passwords in IT Glue older than your rotation window. - ### Documentation complete Every client in IT Glue has current contacts, sites and assets. - ### Every device documented Devices in NinjaOne that are missing from IT Glue. With NinjaOne ## Reports from IT Glue Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### Documentation coverage by client From IT Glue: what’s documented, what’s missing and what’s out of date. ## Ask about IT Glue in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Who’s the ISP contact for Northwind’s warehouse?” Answered from IT Glue. - ### “Has this happened at Harbor before? What fixed it?” Answered from ConnectWise PSA ticket history and IT Glue. - ### “What’s left on Meridian’s onboarding?” Answered from ConnectWise PSA and IT Glue. - ### “Who approves changes at Northbridge?” Answered from the contacts in IT Glue. ## What Control Center reads from IT Glue Documentation, read and write and stored passwords. Control Center connects to IT Glue through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: The Enterprise plan. An administrator creates the key under Admin > Settings, and North America, the EU and Australia have different addresses. The examples on this page use a stack MSPs often run with IT Glue: NinjaOne, ConnectWise PSA, Microsoft 365 and Cisco Meraki. Build your AI plan to see them with your own tools. [Connection details and what you need from IT Glue](https://www.resultsiq.ai/docs/tools/itglue/) ## Questions about IT Glue and Control Center ### Does Control Center work with IT Glue? Yes. Control Center connects to IT Glue through its public API and uses documentation, read and write and stored passwords. You add it once, then choose which clients it covers. ### What can an MSP automate with IT Glue and AI? With Control Center, 7 automations, including: alerts become one ticket, with the fix attached; known fixes run when a tech approves; new hires set up from one request; site down, details ready; documentation that updates itself; new devices set up to your standard. A person approves the steps that matter. ### Can I use IT Glue with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about IT Glue at every client, with the same roles and client scopes as their login. For example: “Who’s the ISP contact for Northwind’s warehouse?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for Hudu](https://www.resultsiq.ai/integrations/hudu/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) --- Page: https://www.resultsiq.ai/integrations/hudu/ Integrations # AI for Hudu Hudu holds your documentation, assets and passwords. Connected to Control Center, devices and users are documented every night, known fixes run from your Hudu articles when a tech approves, and your team can ask about any client’s setup in Claude or ChatGPT. - 5 automations - 3 standards - 1 report - 4 MCP questions ## Automations with Hudu Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached NinjaOne alerts are grouped and duplicates dropped. One HaloPSA ticket opens with the device, the user and the fix from Hudu. With NinjaOne and HaloPSA - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in Hudu runs through NinjaOne, and the time lands on the HaloPSA ticket. With NinjaOne and HaloPSA - ### New hires set up from one request A request in HaloPSA creates the user in Microsoft 365 with the right groups and licenses, documents them in Hudu and closes the ticket. With HaloPSA and Microsoft 365 - ### Documentation that updates itself Devices from NinjaOne and users from Microsoft 365 sync into Hudu every night, with changes flagged. With NinjaOne and Microsoft 365 - ### New devices set up to your standard When a new device checks in to NinjaOne, your baseline scripts run and the device is documented in Hudu. With NinjaOne ## Standards checked in Hudu Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Shared passwords rotated Passwords in Hudu older than your rotation window. - ### Documentation complete Every client in Hudu has current contacts, sites and assets. - ### Every device documented Devices in NinjaOne that are missing from Hudu. With NinjaOne ## Reports from Hudu Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### Documentation coverage by client From Hudu: what’s documented, what’s missing and what’s out of date. ## Ask about Hudu in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Who’s the ISP contact for Northwind’s warehouse?” Answered from Hudu. - ### “Has this happened at Harbor before? What fixed it?” Answered from HaloPSA ticket history and Hudu. - ### “What’s left on Meridian’s onboarding?” Answered from HaloPSA and Hudu. - ### “Who approves changes at Northbridge?” Answered from the contacts in Hudu. ## What Control Center reads from Hudu Documentation, read and write and stored passwords. Control Center connects to Hudu through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: Admins create keys under Admin > API Keys. The full reference is inside your Hudu instance. The examples on this page use a stack MSPs often run with Hudu: NinjaOne, HaloPSA and Microsoft 365. Build your AI plan to see them with your own tools. [Connection details and what you need from Hudu](https://www.resultsiq.ai/docs/tools/hudu/) ## Questions about Hudu and Control Center ### Does Control Center work with Hudu? Yes. Control Center connects to Hudu through its public API and uses documentation, read and write and stored passwords. You add it once, then choose which clients it covers. ### What can an MSP automate with Hudu and AI? With Control Center, 5 automations, including: alerts become one ticket, with the fix attached; known fixes run when a tech approves; new hires set up from one request; documentation that updates itself; new devices set up to your standard. A person approves the steps that matter. ### Can I use Hudu with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Hudu at every client, with the same roles and client scopes as their login. For example: “Who’s the ISP contact for Northwind’s warehouse?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for IT Glue](https://www.resultsiq.ai/integrations/it-glue/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) --- Page: https://www.resultsiq.ai/integrations/microsoft-365/ Integrations # AI for Microsoft 365 Microsoft 365 holds every user, license, sign-in and MFA setting at your clients. Connected to Control Center, new hires and leavers are handled from one ticket, risky sign-ins are investigated, and unused licenses are found and reclaimed. - 8 automations - 8 standards - 2 reports - 4 MCP questions - 1 billing item ## Automations with Microsoft 365 Work that runs on its own, across your tools. A person approves the steps that matter. - ### New hires set up from one request A request in ConnectWise PSA creates the user in Microsoft 365 with the right groups and licenses, documents them in IT Glue and closes the ticket. With ConnectWise PSA and IT Glue - ### Offboarding that misses nothing One ConnectWise PSA ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step. With ConnectWise PSA - ### Phishing pulled and checked When Avanan confirms a phish, it’s pulled from every inbox, Microsoft 365 sign-ins are checked for anyone who clicked, and it’s all on one ConnectWise PSA ticket. With Avanan and ConnectWise PSA - ### Documentation that updates itself Devices from NinjaOne and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and NinjaOne - ### Password resets handled from the ticket A reset request in ConnectWise PSA is done in Microsoft 365 once a tech approves it, and the ticket closes itself. With ConnectWise PSA - ### Risky sign-ins investigated A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a ConnectWise PSA ticket with the user’s recent activity. With ConnectWise PSA - ### MFA gaps turned into tickets Users in Microsoft 365 without MFA open one ConnectWise PSA ticket per client, with the list attached. With ConnectWise PSA - ### Unused licenses reclaimed on approval Microsoft 365 licenses nobody has used in 30 days are listed per client. A tech approves, and they’re removed. ## Standards checked in Microsoft 365 Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### MFA on every account Checked in Microsoft 365 for every user at every client. - ### Microsoft 365 locked down Legacy sign-in blocked, admin roles kept small and conditional access on. - ### No stale devices or accounts Devices in NinjaOne that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With NinjaOne - ### Guest accounts reviewed Guest accounts in Microsoft 365 older than 90 days, at every client. - ### Licenses only on active users Microsoft 365 licenses on disabled or unused accounts. - ### Every device has an owner Devices in NinjaOne that aren’t matched to a person in Microsoft 365. With NinjaOne - ### Sign-ins only from expected countries Microsoft 365 sign-ins from outside each client’s list of countries. - ### Leavers fully removed Accounts in Microsoft 365 still enabled for people offboarded through ConnectWise PSA. With ConnectWise PSA ## Reports from Microsoft 365 Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### MFA coverage and risky sign-ins From Microsoft 365. - ### Microsoft 365 licenses used vs. paid for Unused and unassigned licenses at every client. ## Ask about Microsoft 365 in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Who at Golden Gate still doesn’t have MFA?” Answered from Microsoft 365. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and ConnectWise PSA. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and NinjaOne. - ### “Did anyone at Golden Gate sign in from a new country this week?” Answered from Microsoft 365. ## Billing with Microsoft 365 Get paid for the AI work, through the tools you bill with. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the ConnectWise PSA agreement, with missed billing flagged. With ConnectWise PSA ## What Control Center reads from Microsoft 365 Users, MFA status, sign-ins and licenses. Control Center connects to Microsoft 365 through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: A Microsoft Entra app with Microsoft Graph permissions, and admin consent where required. The examples on this page use a stack MSPs often run with Microsoft 365: ConnectWise PSA, IT Glue, Avanan and NinjaOne. Build your AI plan to see them with your own tools. [Connection details and what you need from Microsoft 365](https://www.resultsiq.ai/docs/tools/m365/) ## Questions about Microsoft 365 and Control Center ### Does Control Center work with Microsoft 365? Yes. Control Center connects to Microsoft 365 through its public API and uses users, MFA status, sign-ins and licenses. You add it once, then choose which clients it covers. ### What can an MSP automate with Microsoft 365 and AI? With Control Center, 8 automations, including: new hires set up from one request; offboarding that misses nothing; phishing pulled and checked; documentation that updates itself; password resets handled from the ticket; risky sign-ins investigated. A person approves the steps that matter. ### Can I use Microsoft 365 with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Microsoft 365 at every client, with the same roles and client scopes as their login. For example: “Who at Golden Gate still doesn’t have MFA?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for Microsoft Intune](https://www.resultsiq.ai/integrations/microsoft-intune/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) --- Page: https://www.resultsiq.ai/integrations/sentinelone/ Integrations # AI for SentinelOne SentinelOne sees every threat and agent across your clients. Connected to Control Center, threats become tickets with the business context attached, isolation is approved from the ticket, and every device is checked for a healthy agent each morning. - 5 automations - 4 standards - 2 reports - 5 MCP questions ## Automations with SentinelOne Work that runs on its own, across your tools. A person approves the steps that matter. - ### Threats triaged before a tech looks When SentinelOne flags a threat, a priority ConnectWise PSA ticket opens with who uses the device and what it can reach. With ConnectWise PSA - ### Isolation, approved from the ticket A tech approves from the ConnectWise PSA ticket and SentinelOne isolates the device. Releasing it works the same way. With ConnectWise PSA - ### New clients onboarded on rails A new client in ConnectWise PSA gets a checklist that tracks NinjaOne agents, SentinelOne coverage and Datto BCDR jobs until every device is done. With ConnectWise PSA, NinjaOne and Datto BCDR - ### Threats remediated on approval A tech approves remediation from the ConnectWise PSA ticket, and SentinelOne cleans up the device. With ConnectWise PSA - ### Broken agents reinstalled When an SentinelOne agent stops reporting, NinjaOne reinstalls it with your script once a tech approves. With NinjaOne ## Standards checked in SentinelOne Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### SentinelOne on every device Devices in NinjaOne without a healthy SentinelOne agent become a ticket. With NinjaOne - ### SentinelOne agents healthy Agents offline, out of date or not reporting, at every client. - ### Threats closed within 24 hours SentinelOne threats still open after 24 hours, at every client. - ### Agents on a supported version SentinelOne agents running a version older than the one you approve. ## Reports from SentinelOne Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, NinjaOne, SentinelOne and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise PSA, NinjaOne and Datto BCDR - ### Threats stopped From SentinelOne, with what was at risk. ## Ask about SentinelOne in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have SentinelOne?” Answered from NinjaOne and SentinelOne. - ### “What changed at Northbridge this week?” Answered from ConnectWise PSA, NinjaOne and SentinelOne. - ### “What did SentinelOne catch at Northbridge this month, and was any of it real?” Answered from SentinelOne. - ### “Which devices are isolated right now, and why?” Answered from SentinelOne. - ### “Which devices at Meridian have an SentinelOne agent that stopped reporting?” Answered from SentinelOne. ## What Control Center reads from SentinelOne Threats, agent health, isolating devices and remediation. Control Center connects to SentinelOne through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: The API reference and API tokens are inside your SentinelOne management console. The examples on this page use a stack MSPs often run with SentinelOne: ConnectWise PSA, NinjaOne and Datto BCDR. Build your AI plan to see them with your own tools. [Connection details and what you need from SentinelOne](https://www.resultsiq.ai/docs/tools/s1/) ## Questions about SentinelOne and Control Center ### Does Control Center work with SentinelOne? Yes. Control Center connects to SentinelOne through its public API and uses threats, agent health, isolating devices and remediation. You add it once, then choose which clients it covers. ### What can an MSP automate with SentinelOne and AI? With Control Center, 5 automations, including: threats triaged before a tech looks; isolation, approved from the ticket; new clients onboarded on rails; threats remediated on approval; broken agents reinstalled. A person approves the steps that matter. ### Can I use SentinelOne with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about SentinelOne at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have SentinelOne?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for Huntress](https://www.resultsiq.ai/integrations/huntress/) [AI for CrowdStrike Falcon](https://www.resultsiq.ai/integrations/crowdstrike/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) --- Page: https://www.resultsiq.ai/integrations/huntress/ Integrations # AI for Huntress Huntress finds and stops threats across your clients. Connected to Control Center, every threat lands as a ticket with who uses the device and what it can reach, and devices without a healthy Huntress agent are flagged every morning. - 5 automations - 4 standards - 2 reports - 5 MCP questions ## Automations with Huntress Work that runs on its own, across your tools. A person approves the steps that matter. - ### Threats triaged before a tech looks When Huntress flags a threat, a priority HaloPSA ticket opens with who uses the device and what it can reach. With HaloPSA - ### Isolation, approved from the ticket A tech approves from the HaloPSA ticket and Huntress isolates the device. Releasing it works the same way. With HaloPSA - ### New clients onboarded on rails A new client in HaloPSA gets a checklist that tracks NinjaOne agents, Huntress coverage and Datto BCDR jobs until every device is done. With HaloPSA, NinjaOne and Datto BCDR - ### Threats remediated on approval A tech approves remediation from the HaloPSA ticket, and Huntress cleans up the device. With HaloPSA - ### Broken agents reinstalled When an Huntress agent stops reporting, NinjaOne reinstalls it with your script once a tech approves. With NinjaOne ## Standards checked in Huntress Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Huntress on every device Devices in NinjaOne without a healthy Huntress agent become a ticket. With NinjaOne - ### Huntress agents healthy Agents offline, out of date or not reporting, at every client. - ### Threats closed within 24 hours Huntress threats still open after 24 hours, at every client. - ### Agents on a supported version Huntress agents running a version older than the one you approve. ## Reports from Huntress Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted HaloPSA, NinjaOne, Huntress and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With HaloPSA, NinjaOne and Datto BCDR - ### Threats stopped From Huntress, with what was at risk. ## Ask about Huntress in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have Huntress?” Answered from NinjaOne and Huntress. - ### “What changed at Northbridge this week?” Answered from HaloPSA, NinjaOne and Huntress. - ### “What did Huntress catch at Northbridge this month, and was any of it real?” Answered from Huntress. - ### “Which devices are isolated right now, and why?” Answered from Huntress. - ### “Which devices at Meridian have an Huntress agent that stopped reporting?” Answered from Huntress. ## What Control Center reads from Huntress Threats, agent health, isolating devices and remediation. Control Center connects to Huntress through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: A user-based API key from your Huntress account. Huntress has deprecated the older account-level key. The examples on this page use a stack MSPs often run with Huntress: HaloPSA, NinjaOne and Datto BCDR. Build your AI plan to see them with your own tools. [Connection details and what you need from Huntress](https://www.resultsiq.ai/docs/tools/huntress/) ## Questions about Huntress and Control Center ### Does Control Center work with Huntress? Yes. Control Center connects to Huntress through its public API and uses threats, agent health, isolating devices and remediation. You add it once, then choose which clients it covers. ### What can an MSP automate with Huntress and AI? With Control Center, 5 automations, including: threats triaged before a tech looks; isolation, approved from the ticket; new clients onboarded on rails; threats remediated on approval; broken agents reinstalled. A person approves the steps that matter. ### Can I use Huntress with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Huntress at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have Huntress?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for SentinelOne](https://www.resultsiq.ai/integrations/sentinelone/) [AI for CrowdStrike Falcon](https://www.resultsiq.ai/integrations/crowdstrike/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) --- Page: https://www.resultsiq.ai/integrations/crowdstrike/ Integrations # AI for CrowdStrike Falcon CrowdStrike Falcon protects every endpoint at your clients. Connected to Control Center, threats become prioritized tickets with business context, isolation is approved from the ticket, and agent coverage is checked every morning. - 5 automations - 4 standards - 2 reports - 5 MCP questions ## Automations with CrowdStrike Falcon Work that runs on its own, across your tools. A person approves the steps that matter. - ### Threats triaged before a tech looks When CrowdStrike flags a threat, a priority ConnectWise PSA ticket opens with who uses the device and what it can reach. With ConnectWise PSA - ### Isolation, approved from the ticket A tech approves from the ConnectWise PSA ticket and CrowdStrike isolates the device. Releasing it works the same way. With ConnectWise PSA - ### New clients onboarded on rails A new client in ConnectWise PSA gets a checklist that tracks NinjaOne agents, CrowdStrike coverage and Datto BCDR jobs until every device is done. With ConnectWise PSA, NinjaOne and Datto BCDR - ### Threats remediated on approval A tech approves remediation from the ConnectWise PSA ticket, and CrowdStrike cleans up the device. With ConnectWise PSA - ### Broken agents reinstalled When an CrowdStrike agent stops reporting, NinjaOne reinstalls it with your script once a tech approves. With NinjaOne ## Standards checked in CrowdStrike Falcon Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### CrowdStrike on every device Devices in NinjaOne without a healthy CrowdStrike agent become a ticket. With NinjaOne - ### CrowdStrike agents healthy Agents offline, out of date or not reporting, at every client. - ### Threats closed within 24 hours CrowdStrike threats still open after 24 hours, at every client. - ### Agents on a supported version CrowdStrike agents running a version older than the one you approve. ## Reports from CrowdStrike Falcon Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, NinjaOne, CrowdStrike and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise PSA, NinjaOne and Datto BCDR - ### Threats stopped From CrowdStrike, with what was at risk. ## Ask about CrowdStrike Falcon in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have CrowdStrike?” Answered from NinjaOne and CrowdStrike. - ### “What changed at Northbridge this week?” Answered from ConnectWise PSA, NinjaOne and CrowdStrike. - ### “What did CrowdStrike catch at Northbridge this month, and was any of it real?” Answered from CrowdStrike. - ### “Which devices are isolated right now, and why?” Answered from CrowdStrike. - ### “Which devices at Meridian have an CrowdStrike agent that stopped reporting?” Answered from CrowdStrike. ## What Control Center reads from CrowdStrike Falcon Threats, agent health, isolating devices and remediation. Control Center connects to CrowdStrike Falcon through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: A Falcon Administrator creates an API client (ID and secret) with the scopes it needs. The examples on this page use a stack MSPs often run with CrowdStrike Falcon: ConnectWise PSA, NinjaOne and Datto BCDR. Build your AI plan to see them with your own tools. [Connection details and what you need from CrowdStrike Falcon](https://www.resultsiq.ai/docs/tools/crowdstrike/) ## Questions about CrowdStrike Falcon and Control Center ### Does Control Center work with CrowdStrike Falcon? Yes. Control Center connects to CrowdStrike Falcon through its public API and uses threats, agent health, isolating devices and remediation. You add it once, then choose which clients it covers. ### What can an MSP automate with CrowdStrike Falcon and AI? With Control Center, 5 automations, including: threats triaged before a tech looks; isolation, approved from the ticket; new clients onboarded on rails; threats remediated on approval; broken agents reinstalled. A person approves the steps that matter. ### Can I use CrowdStrike Falcon with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about CrowdStrike Falcon at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have CrowdStrike?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for SentinelOne](https://www.resultsiq.ai/integrations/sentinelone/) [AI for Huntress](https://www.resultsiq.ai/integrations/huntress/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) --- Page: https://www.resultsiq.ai/integrations/kaseya-vsa/ Integrations # AI for Kaseya VSA Kaseya VSA already manages every device, alert, patch, script and installed app across your clients. Connected to Control Center, alerts become one ticket with the fix attached, your standards are checked every morning, and your team can ask about any device in Claude or ChatGPT. - 10 automations - 9 standards - 6 reports - 11 MCP questions ## Automations with Kaseya VSA Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached Kaseya VSA alerts are grouped and duplicates dropped. One Autotask ticket opens with the device, the user and the fix from IT Glue. With Autotask PSA and IT Glue - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through Kaseya VSA, and the time lands on the Autotask ticket. With Autotask PSA and IT Glue - ### Failed backups handled overnight When a Datto BCDR job fails, a Autotask ticket opens with the error, the last good backup and the device’s health from Kaseya VSA. With Datto BCDR and Autotask PSA - ### Documentation that updates itself Devices from Kaseya VSA and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and Microsoft 365 - ### New clients onboarded on rails A new client in Autotask gets a checklist that tracks Kaseya VSA agents, Datto EDR coverage and Datto BCDR jobs until every device is done. With Autotask PSA, Datto EDR and Datto BCDR - ### Full disks cleaned up before anyone calls When Kaseya VSA flags a disk filling up, the cleanup script your team approved runs. A Autotask ticket opens only if that doesn’t fix it. With Autotask PSA - ### Failed patches retried, then explained Devices that fail patching in Kaseya VSA get another try in the next window. If one fails again, a Autotask ticket opens with the error and the device’s history. With Autotask PSA - ### Software requests installed on approval A software request in Autotask installs through Kaseya VSA once a tech approves it, and the ticket closes with what was installed. With Autotask PSA - ### New devices set up to your standard When a new device checks in to Kaseya VSA, your baseline scripts run and the device is documented in IT Glue. With IT Glue - ### Broken agents reinstalled When an Datto EDR agent stops reporting, Kaseya VSA reinstalls it with your script once a tech approves. With Datto EDR ## Standards checked in Kaseya VSA Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Datto EDR on every device Devices in Kaseya VSA without a healthy Datto EDR agent become a ticket. With Datto EDR - ### Patches inside your window Every device in Kaseya VSA, against the patch window you set. - ### Supported operating systems only Devices in Kaseya VSA on Windows or macOS versions past end of support. - ### Every server backed up Servers in Kaseya VSA with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### No stale devices or accounts Devices in Kaseya VSA that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Only approved software Software in Kaseya VSA’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in Kaseya VSA’s inventory that isn’t on your approved list, at every client. - ### Every device has an owner Devices in Kaseya VSA that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in Kaseya VSA that are missing from IT Glue. With IT Glue ## Reports from Kaseya VSA Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted Autotask, Kaseya VSA, Datto EDR and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With Autotask PSA, Datto EDR and Datto BCDR - ### Patch compliance From Kaseya VSA, per device and per site. - ### Devices by age and operating system From Kaseya VSA, per client and per site, with the devices due for replacement. - ### Software inventory From Kaseya VSA, with unapproved software called out. - ### Alerts and what they cost Alert volume from Kaseya VSA per client, with the Autotask time spent on them. For you, not the client. With Autotask PSA - ### A one-page monthly summary Tickets, devices, security and AI work from Autotask and Kaseya VSA, on one page for the client’s owner. With Autotask PSA ## Ask about Kaseya VSA in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have Datto EDR?” Answered from Kaseya VSA and Datto EDR. - ### “What did we do for Meridian this month?” Answered from Autotask and Kaseya VSA. - ### “Why does Harbor’s file server keep alerting?” Answered from Kaseya VSA alerts and Autotask history. - ### “What changed at Northbridge this week?” Answered from Autotask, Kaseya VSA and Datto EDR. - ### “Which servers at Northwind are low on disk space?” Answered from Kaseya VSA. - ### “Which patches failed at Meridian last night?” Answered from Kaseya VSA. - ### “Which computers still have the old VPN client?” Answered from Kaseya VSA’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from Kaseya VSA. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and Kaseya VSA. - ### “Draft Northbridge’s QBR.” Built from Autotask, Kaseya VSA and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a Kaseya VSA script that a tech approves before it runs. ## What Control Center reads from Kaseya VSA Devices, alerts, patching, scripts and software inventory. Control Center connects to Kaseya VSA through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An administrator creates an API token. Requests go to your own VSA server address. The examples on this page use a stack MSPs often run with Kaseya VSA: Autotask PSA, IT Glue, Datto BCDR, Microsoft 365 and Datto EDR. Build your AI plan to see them with your own tools. [Connection details and what you need from Kaseya VSA](https://www.resultsiq.ai/docs/tools/vsa/) ## Questions about Kaseya VSA and Control Center ### Does Control Center work with Kaseya VSA? Yes. Control Center connects to Kaseya VSA through its public API and uses devices, alerts, patching, scripts and software inventory. You add it once, then choose which clients it covers. ### What can an MSP automate with Kaseya VSA and AI? With Control Center, 10 automations, including: alerts become one ticket, with the fix attached; known fixes run when a tech approves; failed backups handled overnight; documentation that updates itself; new clients onboarded on rails; full disks cleaned up before anyone calls. A person approves the steps that matter. ### Can I use Kaseya VSA with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Kaseya VSA at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have Datto EDR?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) [AI for Datto RMM](https://www.resultsiq.ai/integrations/datto-rmm/) [AI for N-able N-central](https://www.resultsiq.ai/integrations/n-able-n-central/) --- Page: https://www.resultsiq.ai/integrations/syncro/ Integrations # AI for Syncro Syncro runs your tickets, contracts, time and RMM in one place. Connected to Control Center, alerts become tickets with the fix attached, known fixes run when a tech approves, and every AI service you sell is billed through Syncro each month. - 23 automations - 12 standards - 13 reports - 18 MCP questions - 3 billing items ## Automations with Syncro Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached Syncro alerts are grouped and duplicates dropped. One Syncro ticket opens with the device, the user and the fix from Hudu. With Hudu - ### Threats triaged before a tech looks When Huntress flags a threat, a priority Syncro ticket opens with who uses the device and what it can reach. With Huntress - ### Isolation, approved from the ticket A tech approves from the Syncro ticket and Huntress isolates the device. Releasing it works the same way. With Huntress - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in Hudu runs through Syncro, and the time lands on the Syncro ticket. With Hudu - ### New hires set up from one request A request in Syncro creates the user in Microsoft 365 with the right groups and licenses, documents them in Hudu and closes the ticket. With Microsoft 365 and Hudu - ### Offboarding that misses nothing One Syncro ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step. With Microsoft 365 - ### Failed backups handled overnight When a Datto BCDR job fails, a Syncro ticket opens with the error, the last good backup and the device’s health from Syncro. With Datto BCDR - ### Missed time entries caught daily Tickets with work but no time in Syncro are flagged to the tech each afternoon. - ### Every ticket triaged and routed New Syncro tickets are categorized, prioritized and routed, with the client’s business context attached. - ### Documentation that updates itself Devices from Syncro and users from Microsoft 365 sync into Hudu every night, with changes flagged. With Hudu and Microsoft 365 - ### Agreements and invoices reconciled Syncro agreements are checked against QuickBooks invoices every month, and anything unbilled is flagged. QB With QuickBooks Online - ### New clients onboarded on rails A new client in Syncro gets a checklist that tracks Syncro agents, Huntress coverage and Datto BCDR jobs until every device is done. With Huntress and Datto BCDR - ### Full disks cleaned up before anyone calls When Syncro flags a disk filling up, the cleanup script your team approved runs. A Syncro ticket opens only if that doesn’t fix it. - ### Failed patches retried, then explained Devices that fail patching in Syncro get another try in the next window. If one fails again, a Syncro ticket opens with the error and the device’s history. - ### Software requests installed on approval A software request in Syncro installs through Syncro once a tech approves it, and the ticket closes with what was installed. - ### New devices set up to your standard When a new device checks in to Syncro, your baseline scripts run and the device is documented in Hudu. With Hudu - ### Password resets handled from the ticket A reset request in Syncro is done in Microsoft 365 once a tech approves it, and the ticket closes itself. With Microsoft 365 - ### Risky sign-ins investigated A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a Syncro ticket with the user’s recent activity. With Microsoft 365 - ### MFA gaps turned into tickets Users in Microsoft 365 without MFA open one Syncro ticket per client, with the list attached. With Microsoft 365 - ### Failed restore tests caught early When a Datto BCDR restore check fails, a Syncro ticket opens before anyone needs that backup. With Datto BCDR - ### QBR action items become tickets Every action item agreed in a QBR becomes a Syncro ticket or project, with an owner and a date. - ### Threats remediated on approval A tech approves remediation from the Syncro ticket, and Huntress cleans up the device. With Huntress - ### Broken agents reinstalled When an Huntress agent stops reporting, Syncro reinstalls it with your script once a tech approves. With Huntress ## Standards checked in Syncro Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Huntress on every device Devices in Syncro without a healthy Huntress agent become a ticket. With Huntress - ### Patches inside your window Every device in Syncro, against the patch window you set. - ### Supported operating systems only Devices in Syncro on Windows or macOS versions past end of support. - ### Every server backed up Servers in Syncro with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### Every client on a current agreement Clients in Syncro with an expired or missing agreement. - ### No stale devices or accounts Devices in Syncro that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Only approved software Software in Syncro’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in Syncro’s inventory that isn’t on your approved list, at every client. - ### Every device has an owner Devices in Syncro that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in Syncro that are missing from Hudu. With Hudu - ### Leavers fully removed Accounts in Microsoft 365 still enabled for people offboarded through Syncro. With Microsoft 365 - ### Tickets closed properly Syncro tickets closed without notes or time, by tech. For you, not the client. ## Reports from Syncro Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted Syncro, Syncro, Huntress and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With Huntress and Datto BCDR - ### Service desk, in business terms Ticket volume, response times and repeat issues from Syncro, explained by what they cost the client. - ### Patch compliance From Syncro, per device and per site. - ### Your margin on every client Hours in Syncro against revenue in QuickBooks. For you, not the client. QB With QuickBooks Online - ### Devices by age and operating system From Syncro, per client and per site, with the devices due for replacement. - ### Software inventory From Syncro, with unapproved software called out. - ### Alerts and what they cost Alert volume from Syncro per client, with the Syncro time spent on them. For you, not the client. - ### Response and resolution against your SLA From Syncro, per client and per priority. - ### Where the tickets come from Tickets from Syncro by person and by issue, so you fix the cause, not the symptom. - ### What AI did this month Every AI service’s runs, hours returned and value, ready for the client’s QBR. - ### Standards scorecard Every standard you check, passed or failed at each client, with each gap priced as a Syncro project. - ### A one-page monthly summary Tickets, devices, security and AI work from Syncro and Syncro, on one page for the client’s owner. - ### Any report you can describe Describe it in a sentence. Control Center builds it from Syncro and your other connected tools, then sends it on a schedule. ## Ask about Syncro in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have Huntress?” Answered from Syncro and Huntress. - ### “What did we do for Meridian this month?” Answered from Syncro and Syncro. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and Syncro. - ### “Why does Harbor’s file server keep alerting?” Answered from Syncro alerts and Syncro history. - ### “What changed at Northbridge this week?” Answered from Syncro, Syncro and Huntress. - ### “Turn that into an automation.” Any answer can become a workflow, and a person approves it before it runs. - ### “Which servers at Northwind are low on disk space?” Answered from Syncro. - ### “Which patches failed at Meridian last night?” Answered from Syncro. - ### “Which computers still have the old VPN client?” Answered from Syncro’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from Syncro. - ### “Has this happened at Harbor before? What fixed it?” Answered from Syncro ticket history and Hudu. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and Syncro. - ### “What’s left on Meridian’s onboarding?” Answered from Syncro and Hudu. - ### “What work did we do this month that we didn’t bill?” Answered from Syncro time entries and agreements. - ### “Which clients made us the least per hour this quarter?” Answered from Syncro and QuickBooks. - ### “Whose agreement renews next quarter, and what should we add to it?” Answered from Syncro agreements and each client’s AI roadmap. - ### “Draft Northbridge’s QBR.” Built from Syncro, Syncro and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a Syncro script that a tech approves before it runs. ## Billing with Syncro Get paid for the AI work, through the tools you bill with. - ### AI services on the Syncro agreement Every AI service you sell is added to the client’s agreement and billed each month, at your margin. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the Syncro agreement, with missed billing flagged. With Microsoft 365 - ### Every AI run metered Usage per client and per workflow, behind every line you bill. ## What Control Center reads from Syncro Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Control Center connects to Syncro through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An API token from Admin > API Tokens. The address uses your Syncro subdomain. The examples on this page use a stack MSPs often run with Syncro: Hudu, Huntress, Microsoft 365, Datto BCDR and QuickBooks Online. Build your AI plan to see them with your own tools. [Connection details and what you need from Syncro](https://www.resultsiq.ai/docs/tools/syncro/) ## Questions about Syncro and Control Center ### Does Control Center work with Syncro? Yes. Control Center connects to Syncro through its public API and uses tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. You add it once, then choose which clients it covers. ### What can an MSP automate with Syncro and AI? With Control Center, 23 automations, including: alerts become one ticket, with the fix attached; threats triaged before a tech looks; isolation, approved from the ticket; known fixes run when a tech approves; new hires set up from one request; offboarding that misses nothing. A person approves the steps that matter. ### Can I use Syncro with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Syncro at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have Huntress?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for Autotask PSA](https://www.resultsiq.ai/integrations/autotask/) [AI for HaloPSA](https://www.resultsiq.ai/integrations/halopsa/) --- Page: https://www.resultsiq.ai/integrations/superops/ Integrations # AI for SuperOps SuperOps puts your PSA and RMM on one platform. Connected to Control Center, tickets are triaged with each client’s business context, your standards are checked on every device each morning, and your team can ask about any client in Claude or ChatGPT. - 23 automations - 12 standards - 13 reports - 18 MCP questions - 3 billing items ## Automations with SuperOps Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached SuperOps alerts are grouped and duplicates dropped. One SuperOps ticket opens with the device, the user and the fix from IT Glue. With IT Glue - ### Threats triaged before a tech looks When Huntress flags a threat, a priority SuperOps ticket opens with who uses the device and what it can reach. With Huntress - ### Isolation, approved from the ticket A tech approves from the SuperOps ticket and Huntress isolates the device. Releasing it works the same way. With Huntress - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through SuperOps, and the time lands on the SuperOps ticket. With IT Glue - ### New hires set up from one request A request in SuperOps creates the user in Microsoft 365 with the right groups and licenses, documents them in IT Glue and closes the ticket. With Microsoft 365 and IT Glue - ### Offboarding that misses nothing One SuperOps ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step. With Microsoft 365 - ### Failed backups handled overnight When a Datto BCDR job fails, a SuperOps ticket opens with the error, the last good backup and the device’s health from SuperOps. With Datto BCDR - ### Missed time entries caught daily Tickets with work but no time in SuperOps are flagged to the tech each afternoon. - ### Every ticket triaged and routed New SuperOps tickets are categorized, prioritized and routed, with the client’s business context attached. - ### Documentation that updates itself Devices from SuperOps and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and Microsoft 365 - ### Agreements and invoices reconciled SuperOps agreements are checked against QuickBooks invoices every month, and anything unbilled is flagged. QB With QuickBooks Online - ### New clients onboarded on rails A new client in SuperOps gets a checklist that tracks SuperOps agents, Huntress coverage and Datto BCDR jobs until every device is done. With Huntress and Datto BCDR - ### Full disks cleaned up before anyone calls When SuperOps flags a disk filling up, the cleanup script your team approved runs. A SuperOps ticket opens only if that doesn’t fix it. - ### Failed patches retried, then explained Devices that fail patching in SuperOps get another try in the next window. If one fails again, a SuperOps ticket opens with the error and the device’s history. - ### Software requests installed on approval A software request in SuperOps installs through SuperOps once a tech approves it, and the ticket closes with what was installed. - ### New devices set up to your standard When a new device checks in to SuperOps, your baseline scripts run and the device is documented in IT Glue. With IT Glue - ### Password resets handled from the ticket A reset request in SuperOps is done in Microsoft 365 once a tech approves it, and the ticket closes itself. With Microsoft 365 - ### Risky sign-ins investigated A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a SuperOps ticket with the user’s recent activity. With Microsoft 365 - ### MFA gaps turned into tickets Users in Microsoft 365 without MFA open one SuperOps ticket per client, with the list attached. With Microsoft 365 - ### Failed restore tests caught early When a Datto BCDR restore check fails, a SuperOps ticket opens before anyone needs that backup. With Datto BCDR - ### QBR action items become tickets Every action item agreed in a QBR becomes a SuperOps ticket or project, with an owner and a date. - ### Threats remediated on approval A tech approves remediation from the SuperOps ticket, and Huntress cleans up the device. With Huntress - ### Broken agents reinstalled When an Huntress agent stops reporting, SuperOps reinstalls it with your script once a tech approves. With Huntress ## Standards checked in SuperOps Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Huntress on every device Devices in SuperOps without a healthy Huntress agent become a ticket. With Huntress - ### Patches inside your window Every device in SuperOps, against the patch window you set. - ### Supported operating systems only Devices in SuperOps on Windows or macOS versions past end of support. - ### Every server backed up Servers in SuperOps with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### Every client on a current agreement Clients in SuperOps with an expired or missing agreement. - ### No stale devices or accounts Devices in SuperOps that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Only approved software Software in SuperOps’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in SuperOps’s inventory that isn’t on your approved list, at every client. - ### Every device has an owner Devices in SuperOps that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in SuperOps that are missing from IT Glue. With IT Glue - ### Leavers fully removed Accounts in Microsoft 365 still enabled for people offboarded through SuperOps. With Microsoft 365 - ### Tickets closed properly SuperOps tickets closed without notes or time, by tech. For you, not the client. ## Reports from SuperOps Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted SuperOps, SuperOps, Huntress and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With Huntress and Datto BCDR - ### Service desk, in business terms Ticket volume, response times and repeat issues from SuperOps, explained by what they cost the client. - ### Patch compliance From SuperOps, per device and per site. - ### Your margin on every client Hours in SuperOps against revenue in QuickBooks. For you, not the client. QB With QuickBooks Online - ### Devices by age and operating system From SuperOps, per client and per site, with the devices due for replacement. - ### Software inventory From SuperOps, with unapproved software called out. - ### Alerts and what they cost Alert volume from SuperOps per client, with the SuperOps time spent on them. For you, not the client. - ### Response and resolution against your SLA From SuperOps, per client and per priority. - ### Where the tickets come from Tickets from SuperOps by person and by issue, so you fix the cause, not the symptom. - ### What AI did this month Every AI service’s runs, hours returned and value, ready for the client’s QBR. - ### Standards scorecard Every standard you check, passed or failed at each client, with each gap priced as a SuperOps project. - ### A one-page monthly summary Tickets, devices, security and AI work from SuperOps and SuperOps, on one page for the client’s owner. - ### Any report you can describe Describe it in a sentence. Control Center builds it from SuperOps and your other connected tools, then sends it on a schedule. ## Ask about SuperOps in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have Huntress?” Answered from SuperOps and Huntress. - ### “What did we do for Meridian this month?” Answered from SuperOps and SuperOps. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and SuperOps. - ### “Why does Harbor’s file server keep alerting?” Answered from SuperOps alerts and SuperOps history. - ### “What changed at Northbridge this week?” Answered from SuperOps, SuperOps and Huntress. - ### “Turn that into an automation.” Any answer can become a workflow, and a person approves it before it runs. - ### “Which servers at Northwind are low on disk space?” Answered from SuperOps. - ### “Which patches failed at Meridian last night?” Answered from SuperOps. - ### “Which computers still have the old VPN client?” Answered from SuperOps’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from SuperOps. - ### “Has this happened at Harbor before? What fixed it?” Answered from SuperOps ticket history and IT Glue. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and SuperOps. - ### “What’s left on Meridian’s onboarding?” Answered from SuperOps and IT Glue. - ### “What work did we do this month that we didn’t bill?” Answered from SuperOps time entries and agreements. - ### “Which clients made us the least per hour this quarter?” Answered from SuperOps and QuickBooks. - ### “Whose agreement renews next quarter, and what should we add to it?” Answered from SuperOps agreements and each client’s AI roadmap. - ### “Draft Northbridge’s QBR.” Built from SuperOps, SuperOps and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a SuperOps script that a tech approves before it runs. ## Billing with SuperOps Get paid for the AI work, through the tools you bill with. - ### AI services on the SuperOps agreement Every AI service you sell is added to the client’s agreement and billed each month, at your margin. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the SuperOps agreement, with missed billing flagged. With Microsoft 365 - ### Every AI run metered Usage per client and per workflow, behind every line you bill. ## What Control Center reads from SuperOps Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Control Center connects to SuperOps through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An API token from your SuperOps profile settings, plus your SuperOps subdomain. The examples on this page use a stack MSPs often run with SuperOps: IT Glue, Huntress, Microsoft 365, Datto BCDR and QuickBooks Online. Build your AI plan to see them with your own tools. [Connection details and what you need from SuperOps](https://www.resultsiq.ai/docs/tools/superops/) ## Questions about SuperOps and Control Center ### Does Control Center work with SuperOps? Yes. Control Center connects to SuperOps through its public API and uses tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. You add it once, then choose which clients it covers. ### What can an MSP automate with SuperOps and AI? With Control Center, 23 automations, including: alerts become one ticket, with the fix attached; threats triaged before a tech looks; isolation, approved from the ticket; known fixes run when a tech approves; new hires set up from one request; offboarding that misses nothing. A person approves the steps that matter. ### Can I use SuperOps with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about SuperOps at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have Huntress?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for Autotask PSA](https://www.resultsiq.ai/integrations/autotask/) [AI for HaloPSA](https://www.resultsiq.ai/integrations/halopsa/) --- Page: https://www.resultsiq.ai/integrations/atera/ Integrations # AI for Atera Atera combines RMM and ticketing for your clients. Connected to Control Center, alerts become one ticket, patching is checked against your window every morning, and your team can ask about any device or ticket in Claude or ChatGPT. - 18 automations - 10 standards - 12 reports - 16 MCP questions - 2 billing items ## Automations with Atera Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached Atera alerts are grouped and duplicates dropped. One Atera ticket opens with the device, the user and the fix from IT Glue. With IT Glue - ### Threats triaged before a tech looks When SentinelOne flags a threat, a priority Atera ticket opens with who uses the device and what it can reach. With SentinelOne - ### Isolation, approved from the ticket A tech approves from the Atera ticket and SentinelOne isolates the device. Releasing it works the same way. With SentinelOne - ### New hires set up from one request A request in Atera creates the user in Microsoft 365 with the right groups and licenses, documents them in IT Glue and closes the ticket. With Microsoft 365 and IT Glue - ### Offboarding that misses nothing One Atera ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step. With Microsoft 365 - ### Failed backups handled overnight When a Datto BCDR job fails, a Atera ticket opens with the error, the last good backup and the device’s health from Atera. With Datto BCDR - ### Missed time entries caught daily Tickets with work but no time in Atera are flagged to the tech each afternoon. - ### Every ticket triaged and routed New Atera tickets are categorized, prioritized and routed, with the client’s business context attached. - ### Documentation that updates itself Devices from Atera and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and Microsoft 365 - ### Agreements and invoices reconciled Atera agreements are checked against QuickBooks invoices every month, and anything unbilled is flagged. QB With QuickBooks Online - ### New clients onboarded on rails A new client in Atera gets a checklist that tracks Atera agents, SentinelOne coverage and Datto BCDR jobs until every device is done. With SentinelOne and Datto BCDR - ### Failed patches retried, then explained Devices that fail patching in Atera get another try in the next window. If one fails again, a Atera ticket opens with the error and the device’s history. - ### Password resets handled from the ticket A reset request in Atera is done in Microsoft 365 once a tech approves it, and the ticket closes itself. With Microsoft 365 - ### Risky sign-ins investigated A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a Atera ticket with the user’s recent activity. With Microsoft 365 - ### MFA gaps turned into tickets Users in Microsoft 365 without MFA open one Atera ticket per client, with the list attached. With Microsoft 365 - ### Failed restore tests caught early When a Datto BCDR restore check fails, a Atera ticket opens before anyone needs that backup. With Datto BCDR - ### QBR action items become tickets Every action item agreed in a QBR becomes a Atera ticket or project, with an owner and a date. - ### Threats remediated on approval A tech approves remediation from the Atera ticket, and SentinelOne cleans up the device. With SentinelOne ## Standards checked in Atera Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### SentinelOne on every device Devices in Atera without a healthy SentinelOne agent become a ticket. With SentinelOne - ### Patches inside your window Every device in Atera, against the patch window you set. - ### Supported operating systems only Devices in Atera on Windows or macOS versions past end of support. - ### Every server backed up Servers in Atera with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### Every client on a current agreement Clients in Atera with an expired or missing agreement. - ### No stale devices or accounts Devices in Atera that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Every device has an owner Devices in Atera that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in Atera that are missing from IT Glue. With IT Glue - ### Leavers fully removed Accounts in Microsoft 365 still enabled for people offboarded through Atera. With Microsoft 365 - ### Tickets closed properly Atera tickets closed without notes or time, by tech. For you, not the client. ## Reports from Atera Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted Atera, Atera, SentinelOne and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With SentinelOne and Datto BCDR - ### Service desk, in business terms Ticket volume, response times and repeat issues from Atera, explained by what they cost the client. - ### Patch compliance From Atera, per device and per site. - ### Your margin on every client Hours in Atera against revenue in QuickBooks. For you, not the client. QB With QuickBooks Online - ### Devices by age and operating system From Atera, per client and per site, with the devices due for replacement. - ### Alerts and what they cost Alert volume from Atera per client, with the Atera time spent on them. For you, not the client. - ### Response and resolution against your SLA From Atera, per client and per priority. - ### Where the tickets come from Tickets from Atera by person and by issue, so you fix the cause, not the symptom. - ### What AI did this month Every AI service’s runs, hours returned and value, ready for the client’s QBR. - ### Standards scorecard Every standard you check, passed or failed at each client, with each gap priced as a Atera project. - ### A one-page monthly summary Tickets, devices, security and AI work from Atera and Atera, on one page for the client’s owner. - ### Any report you can describe Describe it in a sentence. Control Center builds it from Atera and your other connected tools, then sends it on a schedule. ## Ask about Atera in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have SentinelOne?” Answered from Atera and SentinelOne. - ### “What did we do for Meridian this month?” Answered from Atera and Atera. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and Atera. - ### “Why does Harbor’s file server keep alerting?” Answered from Atera alerts and Atera history. - ### “What changed at Northbridge this week?” Answered from Atera, Atera and SentinelOne. - ### “Turn that into an automation.” Any answer can become a workflow, and a person approves it before it runs. - ### “Which servers at Northwind are low on disk space?” Answered from Atera. - ### “Which patches failed at Meridian last night?” Answered from Atera. - ### “Which devices haven’t checked in this week?” Answered from Atera. - ### “Has this happened at Harbor before? What fixed it?” Answered from Atera ticket history and IT Glue. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and Atera. - ### “What’s left on Meridian’s onboarding?” Answered from Atera and IT Glue. - ### “What work did we do this month that we didn’t bill?” Answered from Atera time entries and agreements. - ### “Which clients made us the least per hour this quarter?” Answered from Atera and QuickBooks. - ### “Whose agreement renews next quarter, and what should we add to it?” Answered from Atera agreements and each client’s AI roadmap. - ### “Draft Northbridge’s QBR.” Built from Atera, Atera and every other connected tool, for your vCIO to edit. ## Billing with Atera Get paid for the AI work, through the tools you bill with. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the Atera agreement, with missed billing flagged. With Microsoft 365 - ### Every AI run metered Usage per client and per workflow, behind every line you bill. ## What Control Center reads from Atera Tickets, agreements, time entries, devices, alerts and patching. Control Center connects to Atera through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: The docs need an Atera login. The API key is under Admin > API and isn’t available during a trial. The examples on this page use a stack MSPs often run with Atera: IT Glue, SentinelOne, Microsoft 365, Datto BCDR and QuickBooks Online. Build your AI plan to see them with your own tools. [Connection details and what you need from Atera](https://www.resultsiq.ai/docs/tools/atera/) ## Questions about Atera and Control Center ### Does Control Center work with Atera? Yes. Control Center connects to Atera through its public API and uses tickets, agreements, time entries, devices, alerts and patching. You add it once, then choose which clients it covers. ### What can an MSP automate with Atera and AI? With Control Center, 18 automations, including: alerts become one ticket, with the fix attached; threats triaged before a tech looks; isolation, approved from the ticket; new hires set up from one request; offboarding that misses nothing; failed backups handled overnight. A person approves the steps that matter. ### Can I use Atera with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Atera at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have SentinelOne?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for Autotask PSA](https://www.resultsiq.ai/integrations/autotask/) [AI for HaloPSA](https://www.resultsiq.ai/integrations/halopsa/) --- Page: https://www.resultsiq.ai/integrations/microsoft-intune/ Integrations # AI for Microsoft Intune Microsoft Intune holds every managed device’s compliance, encryption, apps and updates. Connected to Control Center, compliance and encryption are checked at every client each morning, patches and apps are held to your standard, and your team can ask about any device in Claude or ChatGPT. - 9 automations - 10 standards - 6 reports - 10 MCP questions - 1 billing item ## Automations with Microsoft Intune Work that runs on its own, across your tools. A person approves the steps that matter. - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through Intune, and the time lands on the ConnectWise PSA ticket. With ConnectWise PSA and IT Glue - ### Failed backups handled overnight When a Datto BCDR job fails, a ConnectWise PSA ticket opens with the error, the last good backup and the device’s health from Intune. With Datto BCDR and ConnectWise PSA - ### Documentation that updates itself Devices from Intune sync into IT Glue every night, with changes flagged. With IT Glue - ### New clients onboarded on rails A new client in ConnectWise PSA gets a checklist that tracks Intune agents, SentinelOne coverage and Datto BCDR jobs until every device is done. With ConnectWise PSA, SentinelOne and Datto BCDR - ### Failed patches retried, then explained Devices that fail patching in Intune get another try in the next window. If one fails again, a ConnectWise PSA ticket opens with the error and the device’s history. With ConnectWise PSA - ### Software requests installed on approval A software request in ConnectWise PSA installs through Intune once a tech approves it, and the ticket closes with what was installed. With ConnectWise PSA - ### New devices set up to your standard When a new device checks in to Intune, your baseline scripts run and the device is documented in IT Glue. With IT Glue - ### Unused licenses reclaimed on approval Microsoft 365 licenses nobody has used in 30 days are listed per client. A tech approves, and they’re removed. - ### Broken agents reinstalled When an SentinelOne agent stops reporting, Intune reinstalls it with your script once a tech approves. With SentinelOne ## Standards checked in Microsoft Intune Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### SentinelOne on every device Devices in Intune without a healthy SentinelOne agent become a ticket. With SentinelOne - ### Patches inside your window Every device in Intune, against the patch window you set. - ### Supported operating systems only Devices in Intune on Windows or macOS versions past end of support. - ### Every server backed up Servers in Intune with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### Microsoft 365 locked down Legacy sign-in blocked, admin roles kept small and conditional access on. - ### Devices compliant in Intune Compliance and encryption for every managed device. - ### Only approved software Software in Intune’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in Intune’s inventory that isn’t on your approved list, at every client. - ### Licenses only on active users Microsoft 365 licenses on disabled or unused accounts. - ### Every device documented Devices in Intune that are missing from IT Glue. With IT Glue ## Reports from Microsoft Intune Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, Intune, SentinelOne and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise PSA, SentinelOne and Datto BCDR - ### Patch compliance From Intune, per device and per site. - ### Microsoft 365 licenses used vs. paid for Unused and unassigned licenses at every client. - ### Devices by age and operating system From Intune, per client and per site, with the devices due for replacement. - ### Software inventory From Intune, with unapproved software called out. - ### A one-page monthly summary Tickets, devices, security and AI work from ConnectWise PSA and Intune, on one page for the client’s owner. With ConnectWise PSA ## Ask about Microsoft Intune in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have SentinelOne?” Answered from Intune and SentinelOne. - ### “What did we do for Meridian this month?” Answered from ConnectWise PSA and Intune. - ### “Which clients have more licenses than we bill for?” Answered from Microsoft 365 and ConnectWise PSA. - ### “What changed at Northbridge this week?” Answered from ConnectWise PSA, Intune and SentinelOne. - ### “Which servers at Northwind are low on disk space?” Answered from Intune. - ### “Which patches failed at Meridian last night?” Answered from Intune. - ### “Which computers still have the old VPN client?” Answered from Intune’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from Intune. - ### “Draft Northbridge’s QBR.” Built from ConnectWise PSA, Intune and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a Intune script that a tech approves before it runs. ## Billing with Microsoft Intune Get paid for the AI work, through the tools you bill with. - ### Licenses matched to what you bill Microsoft 365 licenses at every client against the ConnectWise PSA agreement, with missed billing flagged. With ConnectWise PSA ## What Control Center reads from Microsoft Intune Devices, patching, scripts, software inventory and device compliance. Control Center connects to Microsoft Intune through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An Intune license and a Microsoft Entra app with Microsoft Graph permissions. The examples on this page use a stack MSPs often run with Microsoft Intune: ConnectWise PSA, IT Glue, Datto BCDR and SentinelOne. Build your AI plan to see them with your own tools. [Connection details and what you need from Microsoft Intune](https://www.resultsiq.ai/docs/tools/intune/) ## Questions about Microsoft Intune and Control Center ### Does Control Center work with Microsoft Intune? Yes. Control Center connects to Microsoft Intune through its public API and uses devices, patching, scripts, software inventory and device compliance. You add it once, then choose which clients it covers. ### What can an MSP automate with Microsoft Intune and AI? With Control Center, 9 automations, including: known fixes run when a tech approves; failed backups handled overnight; documentation that updates itself; new clients onboarded on rails; failed patches retried, then explained; software requests installed on approval. A person approves the steps that matter. ### Can I use Microsoft Intune with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Microsoft Intune at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have SentinelOne?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) [AI for Datto RMM](https://www.resultsiq.ai/integrations/datto-rmm/) [AI for N-able N-central](https://www.resultsiq.ai/integrations/n-able-n-central/) --- Page: https://www.resultsiq.ai/integrations/veeam/ Integrations # AI for Veeam Veeam protects your clients’ servers and workloads. Connected to Control Center, failed backup jobs are ticketed overnight, restore checks are watched every day, and every server is checked for a recent backup. - 3 automations - 3 standards - 3 reports - 3 MCP questions ## Automations with Veeam Work that runs on its own, across your tools. A person approves the steps that matter. - ### Failed backups handled overnight When a Veeam job fails, a ConnectWise PSA ticket opens with the error, the last good backup and the device’s health from NinjaOne. With ConnectWise PSA and NinjaOne - ### New clients onboarded on rails A new client in ConnectWise PSA gets a checklist that tracks NinjaOne agents, SentinelOne coverage and Veeam jobs until every device is done. With ConnectWise PSA, NinjaOne and SentinelOne - ### Failed restore tests caught early When a Veeam restore check fails, a ConnectWise PSA ticket opens before anyone needs that backup. With ConnectWise PSA ## Standards checked in Veeam Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Every server backed up Servers in NinjaOne with no Veeam backup, or none that finished in the last 24 hours. With NinjaOne - ### Backups that actually restore Veeam verification results, checked every day. - ### Backups recent enough to recover from Servers whose last good Veeam backup is older than your recovery point target. ## Reports from Veeam Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, NinjaOne, SentinelOne and Veeam in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise PSA, NinjaOne and SentinelOne - ### Backup success and recovery readiness From Veeam, per server and per site. - ### Restore tests, passed and failed From Veeam, per server, ready for the client’s QBR. ## Ask about Veeam in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which clients missed a backup last night?” Answered from Veeam. - ### “When did we last test a restore of Golden Gate’s file server?” Answered from Veeam. - ### “If Golden Gate’s file server died now, how much work would they lose?” Answered from Veeam: the last good backup and when it finished. ## What Control Center reads from Veeam Backup jobs and restore checks. Control Center connects to Veeam through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: For MSPs, Veeam Service Provider Console uses API keys created in its portal. The examples on this page use a stack MSPs often run with Veeam: ConnectWise PSA, NinjaOne and SentinelOne. Build your AI plan to see them with your own tools. [Connection details and what you need from Veeam](https://www.resultsiq.ai/docs/tools/veeam/) ## Questions about Veeam and Control Center ### Does Control Center work with Veeam? Yes. Control Center connects to Veeam through its public API and uses backup jobs and restore checks. You add it once, then choose which clients it covers. ### What can an MSP automate with Veeam and AI? With Control Center, 3 automations, including: failed backups handled overnight; new clients onboarded on rails; failed restore tests caught early. A person approves the steps that matter. ### Can I use Veeam with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Veeam at every client, with the same roles and client scopes as their login. For example: “Which clients missed a backup last night?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for Datto BCDR](https://www.resultsiq.ai/integrations/datto-bcdr/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) --- Page: https://www.resultsiq.ai/integrations/datto-bcdr/ Integrations # AI for Datto BCDR Datto BCDR protects your clients’ servers. Connected to Control Center, failed backups are ticketed overnight with the error and the last good backup, restore checks are watched every day, and every server is checked for a backup that finished. - 3 automations - 3 standards - 3 reports - 3 MCP questions ## Automations with Datto BCDR Work that runs on its own, across your tools. A person approves the steps that matter. - ### Failed backups handled overnight When a Datto BCDR job fails, a Autotask ticket opens with the error, the last good backup and the device’s health from Datto RMM. With Autotask PSA and Datto RMM - ### New clients onboarded on rails A new client in Autotask gets a checklist that tracks Datto RMM agents, Datto EDR coverage and Datto BCDR jobs until every device is done. With Autotask PSA, Datto RMM and Datto EDR - ### Failed restore tests caught early When a Datto BCDR restore check fails, a Autotask ticket opens before anyone needs that backup. With Autotask PSA ## Standards checked in Datto BCDR Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Every server backed up Servers in Datto RMM with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto RMM - ### Backups that actually restore Datto BCDR verification results, checked every day. - ### Backups recent enough to recover from Servers whose last good Datto BCDR backup is older than your recovery point target. ## Reports from Datto BCDR Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted Autotask, Datto RMM, Datto EDR and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With Autotask PSA, Datto RMM and Datto EDR - ### Backup success and recovery readiness From Datto BCDR, per server and per site. - ### Restore tests, passed and failed From Datto BCDR, per server, ready for the client’s QBR. ## Ask about Datto BCDR in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which clients missed a backup last night?” Answered from Datto BCDR. - ### “When did we last test a restore of Golden Gate’s file server?” Answered from Datto BCDR. - ### “If Golden Gate’s file server died now, how much work would they lose?” Answered from Datto BCDR: the last good backup and when it finished. ## What Control Center reads from Datto BCDR Backup jobs and restore checks. Control Center connects to Datto BCDR through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: A Datto Partner Portal admin creates the key under Admin > Integrations > API Keys. The examples on this page use a stack MSPs often run with Datto BCDR: Autotask PSA, Datto RMM and Datto EDR. Build your AI plan to see them with your own tools. [Connection details and what you need from Datto BCDR](https://www.resultsiq.ai/docs/tools/dattobcdr/) ## Questions about Datto BCDR and Control Center ### Does Control Center work with Datto BCDR? Yes. Control Center connects to Datto BCDR through its public API and uses backup jobs and restore checks. You add it once, then choose which clients it covers. ### What can an MSP automate with Datto BCDR and AI? With Control Center, 3 automations, including: failed backups handled overnight; new clients onboarded on rails; failed restore tests caught early. A person approves the steps that matter. ### Can I use Datto BCDR with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Datto BCDR at every client, with the same roles and client scopes as their login. For example: “Which clients missed a backup last night?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for Veeam](https://www.resultsiq.ai/integrations/veeam/) [AI for ConnectWise PSA](https://www.resultsiq.ai/integrations/connectwise-psa/) [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) --- Page: https://www.resultsiq.ai/docs/connections/ # How connections work Control Center connects to each tool through the vendor’s own documented API, with access you grant and scope. Here’s how, and what to have before you connect a tool. ## Through the vendor’s own API Control Center works through the documented API each vendor publishes, using access you grant in that tool, such as an API key or an app you approve. ## Scoped per client Every integration is enabled per tenant with the exact API operations you allow, and nothing else. ## Logged, and approved by a person Every document, price, workflow and approval is logged with who, when and on what input. A person approves before any client sees anything. ## Keys stay in the vault API keys and passwords live in Control Center’s vault. Your team’s AI never sees them, and nothing is pasted into a chat. ## Your AI follows the same rules Your team reaches the same tools from Claude or ChatGPT through [Control Center MCP](https://www.resultsiq.ai/docs/mcp/), with the same roles and client scopes as their login. ## Before you connect a tool - An admin sign-in for the tool. - A plan that includes API access. A few vendors keep it to certain plans, and each tool’s page says so. - Permission to create an API key or register an app in the tool. - Your region or instance address, where the vendor uses one. Each tool’s page in [Every tool](https://www.resultsiq.ai/docs/tools/) lists what that vendor needs on top of this. ## Where each vendor’s API docs are - Public docs : Anyone can read the vendor’s API docs. - Docs need a login : You sign in with a customer or partner account to read them. - Partner access : The vendor opens its API through a partner or developer program, so the connection depends on the vendor’s approval. ## A tool that isn’t listed If it has a documented API, Control Center can connect to it. [Email us](mailto:connor.reece@resultsiq.ai?subject=API%20docs%20for%20a%20tool) the tool’s name and a link to its API docs. --- Page: https://www.resultsiq.ai/docs/tools/ # Every tool The 159 tools Control Center connects to, by category: what it uses from each, what the vendor needs, and the link to the vendor’s API docs. 156 connect today, and 3 depend on the vendor’s partner program. Public docs: anyone can read them. Docs need a login: a customer or partner login. Partner access: the vendor opens its API through a partner or developer program. ## PSA - [ConnectWise PSA](https://www.resultsiq.ai/docs/tools/cwpsa/): Uses: Tickets, agreements, billing and time entries. Needs: The docs need a ConnectWise Developer Network account, which ConnectWise approves. API docs: https://developer.connectwise.com/Products/ConnectWise_PSA (docs need a login). - [Autotask PSA](https://www.resultsiq.ai/docs/tools/autotask/): Uses: Tickets, agreements, billing and time entries. Needs: An API user created in Autotask. The API address depends on your Autotask zone. API docs: https://www.autotask.net/help/DeveloperHelp/Content/APIs/REST/REST_API_Home.htm (public docs). - [HaloPSA](https://www.resultsiq.ai/docs/tools/halo/): Uses: Tickets, agreements, billing and time entries. Needs: An API application registered in HaloPSA (client ID and secret). Addresses are specific to your instance. API docs: https://halopsa.com/apidoc (public docs). - [Kaseya BMS](https://www.resultsiq.ai/docs/tools/bms/): Uses: Tickets, agreements, billing and time entries. Needs: A BMS username, password and tenant. Use your region’s API: US, EMEA or APAC. API docs: https://help.bms.kaseya.com/help/Content/BMS%20API/bms-api-v2-bms-rest-apis.html (public docs). - [Syncro](https://www.resultsiq.ai/docs/tools/syncro/): Uses: Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Needs: An API token from Admin > API Tokens. The address uses your Syncro subdomain. API docs: https://api-docs.syncromsp.com/ (public docs). - [SuperOps](https://www.resultsiq.ai/docs/tools/superops/): Uses: Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Needs: An API token from your SuperOps profile settings, plus your SuperOps subdomain. API docs: https://developer.superops.com/ (public docs). - [Atera](https://www.resultsiq.ai/docs/tools/atera/): Uses: Tickets, agreements, time entries, devices, alerts and patching. Needs: The docs need an Atera login. The API key is under Admin > API and isn’t available during a trial. API docs: https://app.atera.com/apidocs (docs need a login). - [Accelo](https://www.resultsiq.ai/docs/tools/accelo/): Uses: Tickets, agreements and time entries. Needs: An API application registered under Configuration > API (OAuth 2.0). API docs: https://accelo.github.io/docs/ (public docs). - [ServiceNow](https://www.resultsiq.ai/docs/tools/servicenow/): Uses: Tickets. Needs: Your instance address and a user with roles for the tables it reads. API docs: https://www.servicenow.com/docs/r/api-reference (public docs). - [Freshservice](https://www.resultsiq.ai/docs/tools/freshservice/): Uses: Tickets and time entries. Needs: An API key from your profile settings. Rate limits depend on your plan. API docs: https://api.freshservice.com/ (public docs). - [Zendesk](https://www.resultsiq.ai/docs/tools/zendesk/): Uses: Tickets. Needs: Requests go to your own Zendesk subdomain. API docs: https://developer.zendesk.com/api-reference/ticketing/introduction/ (public docs). - [Jira Service Management](https://www.resultsiq.ai/docs/tools/jsm/): Uses: Tickets and time entries. Needs: An Atlassian account email and API token, against your site address. API docs: https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/ (public docs). ## RMM - [Syncro](https://www.resultsiq.ai/docs/tools/syncro/): Uses: Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Needs: An API token from Admin > API Tokens. The address uses your Syncro subdomain. API docs: https://api-docs.syncromsp.com/ (public docs). - [SuperOps](https://www.resultsiq.ai/docs/tools/superops/): Uses: Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. Needs: An API token from your SuperOps profile settings, plus your SuperOps subdomain. API docs: https://developer.superops.com/ (public docs). - [Atera](https://www.resultsiq.ai/docs/tools/atera/): Uses: Tickets, agreements, time entries, devices, alerts and patching. Needs: The docs need an Atera login. The API key is under Admin > API and isn’t available during a trial. API docs: https://app.atera.com/apidocs (docs need a login). - [NinjaOne](https://www.resultsiq.ai/docs/tools/ninja/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: An API client app (OAuth 2.0) created in NinjaOne. API docs: https://app.ninjaone.com/apidocs-beta/ (public docs). - [Datto RMM](https://www.resultsiq.ai/docs/tools/dattormm/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: Turn on API access in Global Settings. Each user gets their own keys, and the address depends on your Datto RMM platform. API docs: https://rmm.datto.com/help/en/Content/2SETUP/APIv2.htm (public docs). - [ConnectWise Automate](https://www.resultsiq.ai/docs/tools/automate/): Uses: Devices, patching and scripts. Needs: The docs need a ConnectWise Developer Network account, which ConnectWise approves. API docs: https://developer.connectwise.com/Products/ConnectWise_Automate (docs need a login). - [ConnectWise RMM](https://www.resultsiq.ai/docs/tools/cwrmm/): Uses: Devices, patching and scripts. Needs: Regional API addresses for the US, EU and Australia, with OAuth 2.0 client credentials. API docs: https://openapi.service.itsupport247.net. - [Kaseya VSA](https://www.resultsiq.ai/docs/tools/vsa/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: An administrator creates an API token. Requests go to your own VSA server address. API docs: https://api.vsax.net (public docs). - [N-able N-central](https://www.resultsiq.ai/docs/tools/ncentral/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: An API-only user and its token, created in N-central. API docs: https://developer.n-able.com/n-central (public docs). - [N-able N-sight](https://www.resultsiq.ai/docs/tools/nsight/): Uses: Devices, alerts, patching, scripts and software inventory. Needs: An API key generated in N-sight. API docs: https://documentation.n-able.com/remote-management/userguide/Content/api_calls.htm (public docs). - [Level](https://www.resultsiq.ai/docs/tools/level/): Uses: Devices, alerts, patching and scripts. Needs: An API key from Settings > API keys, read-only or read-write. API docs: https://developers.level.io/ (public docs). - [Action1](https://www.resultsiq.ai/docs/tools/action1/): Uses: Devices, patching, scripts and software inventory. Needs: An API client ID and secret from Action1’s API Credentials page. API docs: https://www.action1.com/api-documentation/ (public docs). - [Pulseway](https://www.resultsiq.ai/docs/tools/pulseway/): Uses: Devices. API docs: https://api.pulseway.com/ (public docs). - [ImmyBot](https://www.resultsiq.ai/docs/tools/immy/): Uses: Devices, scripts and software inventory. Needs: A Microsoft Entra app registration. Each instance has its own API reference at your-subdomain.immy.bot/swagger. API docs: https://www.immy.bot/documentation/reference/api-documentation/ (public docs). - [Automox](https://www.resultsiq.ai/docs/tools/automox/): Uses: Devices, patching, scripts and software inventory. Needs: An API key from the Automox console. API docs: https://docs.automox.com/product/Developer/Developer_LP.htm (public docs). - [Microsoft Intune](https://www.resultsiq.ai/docs/tools/intune/): Uses: Devices, patching, scripts, software inventory and device compliance. Needs: An Intune license and a Microsoft Entra app with Microsoft Graph permissions. API docs: https://learn.microsoft.com/graph/api/resources/intune-graph-overview?view=graph-rest-1.0 (public docs). ## Endpoint security - [SentinelOne](https://www.resultsiq.ai/docs/tools/s1/): Uses: Threats, agent health, isolating devices and remediation. Needs: The API reference and API tokens are inside your SentinelOne management console. API docs: no public link (docs need a login). - [CrowdStrike Falcon](https://www.resultsiq.ai/docs/tools/crowdstrike/): Uses: Threats, agent health, isolating devices and remediation. Needs: A Falcon Administrator creates an API client (ID and secret) with the scopes it needs. API docs: https://developer.crowdstrike.com/api-reference/ (public docs). - [Huntress](https://www.resultsiq.ai/docs/tools/huntress/): Uses: Threats, agent health, isolating devices and remediation. Needs: A user-based API key from your Huntress account. Huntress has deprecated the older account-level key. API docs: https://api.huntress.io/docs (public docs). - [Microsoft Defender for Endpoint](https://www.resultsiq.ai/docs/tools/defender/): Uses: Threats, agent health, isolating devices and remediation. Needs: A Microsoft Entra app registration. Use your region’s API address. API docs: https://learn.microsoft.com/defender-endpoint/api/apis-intro (public docs). - [Sophos Central](https://www.resultsiq.ai/docs/tools/sophos/): Uses: Threats, agent health, isolating devices and remediation. Needs: A Super Admin creates API credentials in Sophos Central. Each tenant has its own data-region address. API docs: https://developer.sophos.com/ (public docs). - [Bitdefender GravityZone](https://www.resultsiq.ai/docs/tools/bitdefender/): Uses: Threats, agent health, isolating devices and remediation. Needs: An API key from your GravityZone account settings. API docs: https://www.bitdefender.com/business/support/en/77209-125277-public-api.html (public docs). - [ESET PROTECT](https://www.resultsiq.ai/docs/tools/eset/): Uses: Threats, agent health, isolating devices and remediation. Needs: Through ESET Connect, for ESET PROTECT Cloud, ESET Inspect and ESET Cloud Office Security. API docs: https://help.eset.com/eset_connect/en-US/index.html (public docs). - [ThreatDown](https://www.resultsiq.ai/docs/tools/threatdown/): Uses: Threats, agent health, isolating devices and remediation. Needs: A Global or Site Administrator creates an OAuth client (read, write or execute) under Integrate in OneView. API docs: https://support.threatdown.com/hc/en-us/articles/4413799441683 (public docs). - [Webroot](https://www.resultsiq.ai/docs/tools/webroot/): Uses: Threats, agent health and remediation. Needs: An API client ID and secret, which come from your Webroot representative. API docs: https://unityapi.webrootcloudav.com/Docs/en/APIDoc (public docs). - [Blackpoint Cyber](https://www.resultsiq.ai/docs/tools/blackpoint/): Uses: Threats. Needs: We couldn’t find public API docs. Ask Blackpoint for them. API docs: no public link (docs need a login). - [Arctic Wolf](https://www.resultsiq.ai/docs/tools/arcticwolf/): Uses: Threats. Needs: A personal API key from the Unified Portal. The Data Retrieval API needs a Data Explorer license. API docs: https://docs.arcticwolf.com/en/developer-and-oem/data-retrieval-api/arctic-wolf-data-retrieval-api/use-the-data-retrieval-api (public docs). - [Cynet](https://www.resultsiq.ai/docs/tools/cynet/): Uses: Threats, agent health and remediation. API docs: https://help.api.cynet.com/docs/API-V3/9g00cv3m8b10g-cynet-api-documentation (public docs). - [Datto EDR](https://www.resultsiq.ai/docs/tools/dattoedr/): Uses: Threats, agent health and remediation. Needs: The API explorer is inside each customer’s own Datto EDR instance. API docs: https://edr.datto.com/help/Content/2-manage/api-loopback-explorer.html (docs need a login). Note: Datto EDR’s API explorer is inside each customer’s own Datto EDR instance. ## SIEM and managed SOC - [Microsoft Sentinel](https://www.resultsiq.ai/docs/tools/sentinel/): Uses: Alerts, incidents and log search. Needs: A Microsoft Entra app with a Microsoft Sentinel role on the workspace. Log search runs through the Azure Monitor Logs API. API docs: https://learn.microsoft.com/en-us/rest/api/securityinsights/ (public docs). - [Blumira](https://www.resultsiq.ai/docs/tools/blumira/): Uses: Alerts, incidents and agent health. Needs: Its MSP endpoints cover every client account you manage. API docs: https://support.blumira.com/hc/en-us/articles/41813668396435-Using-the-Blumira-API (public docs). - [Stellar Cyber](https://www.resultsiq.ai/docs/tools/stellar/): Uses: Alerts, incidents and log search. API docs: https://docs.stellarcyber.ai/Using/API/API-Intro.htm (public docs). - [RocketCyber](https://www.resultsiq.ai/docs/tools/rocketcyber/): Uses: Alerts and incidents. Needs: The API is read-only. API docs: https://api-doc.rocketcyber.com/ (public docs). - [N-able Adlumin](https://www.resultsiq.ai/docs/tools/adlumin/): Uses: Alerts. Needs: Requests are made per tenant. API docs: https://developer.n-able.com/adlumin/reference (public docs). - [Rapid7 InsightIDR](https://www.resultsiq.ai/docs/tools/insightidr/): Uses: Alerts, incidents and log search. API docs: https://docs.rapid7.com/insightidr/insightidr-rest-api/ (public docs). - [Splunk](https://www.resultsiq.ai/docs/tools/splunk/): Uses: Alerts and log search. Needs: Splunk Enterprise Security adds endpoints for findings, investigations and risk. API docs: https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.2 (public docs). - [Elastic Security](https://www.resultsiq.ai/docs/tools/elastic/): Uses: Alerts, incidents and log search. API docs: https://www.elastic.co/docs/api/doc/kibana (public docs). - [Sumo Logic](https://www.resultsiq.ai/docs/tools/sumo/): Uses: Alerts and log search. API docs: https://www.sumologic.com/help/docs/api/ (public docs). - [Exabeam](https://www.resultsiq.ai/docs/tools/exabeam/): Uses: Alerts, incidents and log search. API docs: https://developers.exabeam.com/exabeam/reference/ (public docs). - [LogRhythm](https://www.resultsiq.ai/docs/tools/logrhythm/): Uses: Alerts, incidents and log search. API docs: https://developers.exabeam.com/logrhythm-siem/docs (public docs). - [Fortinet FortiSIEM](https://www.resultsiq.ai/docs/tools/fortisiem/): Uses: Alerts and incidents. Needs: The guide for version 6.7 is public. Guides for 7.x need a Fortinet login. API docs: https://docs.fortinet.com/document/fortisiem/6.7.5/integration-api-guide (public docs). - [Coro](https://www.resultsiq.ai/docs/tools/coro/): Uses: Alerts. API docs: https://developers.coro.net/openapi/reference/overview (public docs). - [Wazuh](https://www.resultsiq.ai/docs/tools/wazuh/): Uses: Alerts and agent health. Needs: Open source. Alerts come through the Wazuh indexer’s API. API docs: https://documentation.wazuh.com/current/user-manual/api/reference.html (public docs). - [SaaS Alerts](https://www.resultsiq.ai/docs/tools/saasalerts/): Uses: Alerts. API docs: https://help.saasalerts.kaseya.com/help/Content/How-To/using-the-saas-alerts-api.htm (public docs). - [Field Effect MDR](https://www.resultsiq.ai/docs/tools/fieldeffect/): Uses: What the API covers isn’t public; its docs need a Field Effect login. Needs: An API key and an approved IP address, both from Field Effect support. API docs: https://support.fieldeffect.com/en/support/solutions/articles/16000205372 (docs need a login). Note: Field Effect’s API needs a key and an approved IP address from Field Effect support. ## Email security - [Avanan](https://www.resultsiq.ai/docs/tools/avanan/): Uses: Threats and remediation. Needs: A client ID and secret. MSPs use an MSP key, and Avanan support issues them if you don’t have one. API docs: https://sc1.checkpoint.com/documents/Avanan_API_Reference/Topics-HEC-Avanan-API-Reference-Guide/Overview/API-Overview.htm (public docs). - [Mimecast](https://www.resultsiq.ai/docs/tools/mimecast/): Uses: Threats, remediation and users. Needs: An API application registered in Mimecast, which you can set up yourself. API docs: https://developer.services.mimecast.com/api-overview (public docs). - [IRONSCALES](https://www.resultsiq.ai/docs/tools/ironscales/): Uses: Threats and remediation. Needs: A company token from Settings > General, exchanged for a scoped token. Limit: 120 calls a minute. API docs: https://appapi.ironscales.com/appapi/docs/ (public docs). - [Abnormal](https://www.resultsiq.ai/docs/tools/abnormal/): Uses: Threats and remediation. Needs: A token from the Abnormal portal, under Settings > Integrations > Abnormal REST API. API docs: https://api.swaggerhub.com/apis/abnormal-security/abx/1.8.0 (public docs). - [Proofpoint](https://www.resultsiq.ai/docs/tools/pfpt/): Uses: Threats. Needs: A service principal and secret from the TAP Dashboard settings. API docs: https://help.proofpoint.com/Threat_Insight_Dashboard/API_Documentation (public docs). - [Proofpoint Essentials](https://www.resultsiq.ai/docs/tools/pfpte/): Uses: Users. Needs: An organization admin’s credentials. The address depends on your Essentials stack (us1, eu1 and others). API docs: https://us1.proofpointessentials.com/api/v1/docs/index.php (public docs). - [Material Security](https://www.resultsiq.ai/docs/tools/material/): Uses: Threats and users. Needs: A token from Integrations > API and MCP > Tokens. The address is your own instance. API docs: https://docs.material.security/reference (public docs). - [Barracuda](https://www.resultsiq.ai/docs/tools/barracuda/): Uses: Account and email traffic numbers. The API is read-only for now. Needs: An app registered in the Barracuda Token Service. The API is in beta, for the US and UK regions. API docs: https://documentation.campus.barracuda.com/wiki/display/EGD/API+Overview (public docs). Note: Barracuda’s email API is an early, read-only version, so Control Center can read its account and traffic numbers only. - [SpamTitan](https://www.resultsiq.ai/docs/tools/spamtitan/): Uses: Threats. API docs: https://api-spamtitan.titanhq.com/ (public docs). - [EasyDMARC](https://www.resultsiq.ai/docs/tools/easydmarc/): Uses: Domains, DMARC reports and DNS checks. API docs: https://developers.easydmarc.com/ (public docs). ## Backup - [Datto BCDR](https://www.resultsiq.ai/docs/tools/dattobcdr/): Uses: Backup jobs and restore checks. Needs: A Datto Partner Portal admin creates the key under Admin > Integrations > API Keys. API docs: https://portal.dattobackup.com/integrations/api (docs need a login). - [Datto SaaS Protection](https://www.resultsiq.ai/docs/tools/dattosaas/): Uses: Backup jobs and which accounts are backed up. Needs: A Datto Partner Portal admin creates the key under Admin > Integrations > API Keys. API docs: https://portal.dattobackup.com/integrations/api (docs need a login). - [Veeam](https://www.resultsiq.ai/docs/tools/veeam/): Uses: Backup jobs and restore checks. Needs: For MSPs, Veeam Service Provider Console uses API keys created in its portal. API docs: https://helpcenter.veeam.com/references/vbr/13/rest/1.3-rev2/tag/SectionAbout (public docs). Service Provider Console: https://helpcenter.veeam.com/references/vac/9.3/rest/. - [Acronis](https://www.resultsiq.ai/docs/tools/acronis/): Uses: Backup jobs. Needs: An API client (ID and secret) registered in the management console. The address depends on your data center. API docs: https://developer.acronis.com/doc/account-management/v2/guide/getting-started/authenticating.html (public docs). - [Axcient x360Recover](https://www.resultsiq.ai/docs/tools/axcient/): Uses: Backup jobs and restore checks. Needs: An administrator creates an API key in the partner portal, under Settings > API Keys. API docs: https://developer.axcient.com/ (public docs). - [Cove Data Protection](https://www.resultsiq.ai/docs/tools/cove/): Uses: Backup jobs. API docs: https://documentation.n-able.com/covedataprotection/USERGUIDE/documentation/Content/service-management/json-api/home.htm (public docs). - [Rubrik](https://www.resultsiq.ai/docs/tools/rubrik/): Uses: Backup jobs and restore checks. Needs: A service account (client ID and secret). Tokens come from your tenant’s my.rubrik.com address. API docs: https://developer.rubrik.com/ (public docs). - [Dropsuite](https://www.resultsiq.ai/docs/tools/dropsuite/): Uses: Which accounts are backed up. Needs: API tokens are for direct partners and distributors of Dropsuite (NinjaOne SaaS Backup). API docs: https://help.dropsuite.com/hc/en-us/articles/20422080552855-15-API-Settings (partner access). - [Keepit](https://www.resultsiq.ai/docs/tools/keepit/): Uses: Backup jobs and which accounts are backed up. Needs: API token credentials created in Keepit. API docs: https://developers.keepit.com/authentication (public docs). - [AvePoint](https://www.resultsiq.ai/docs/tools/avepoint/): Uses: Backup jobs and which accounts are backed up. Needs: An app registered in AvePoint Online Services. Token addresses depend on your region. API docs: https://learn.avepoint.com/docs/Overview.html (public docs). - [Redstor](https://www.resultsiq.ai/docs/tools/redstor/): Uses: Backup jobs. Needs: A Partner Admin creates a service account. Redstor’s docs tie the API to its newer pricing plan. API docs: https://helpdesk.redstor.com/support/solutions/articles/4000219746-1607-how-to-use-the-redapi (public docs). ## Documentation - [IT Glue](https://www.resultsiq.ai/docs/tools/itglue/): Uses: Documentation, read and write and stored passwords. Needs: The Enterprise plan. An administrator creates the key under Admin > Settings, and North America, the EU and Australia have different addresses. API docs: https://api.itglue.com/developer/ (public docs). - [Hudu](https://www.resultsiq.ai/docs/tools/hudu/): Uses: Documentation, read and write and stored passwords. Needs: Admins create keys under Admin > API Keys. The full reference is inside your Hudu instance. API docs: https://support.hudu.com/hc/en-us/articles/11422780787735-REST-API (docs need a login). - [Confluence](https://www.resultsiq.ai/docs/tools/confluence/): Uses: Documentation, read and write. Needs: An Atlassian account email and API token, against your site address. API docs: https://developer.atlassian.com/cloud/confluence/rest/v2/ (public docs). - [SharePoint](https://www.resultsiq.ai/docs/tools/sharepoint/): Uses: Documentation, read and write. Needs: A Microsoft Entra app with Microsoft Graph permissions. Some permissions need admin consent. API docs: https://learn.microsoft.com/en-us/graph/api/resources/sharepoint?view=graph-rest-1.0 (public docs). - [Notion](https://www.resultsiq.ai/docs/tools/notion/): Uses: Documentation, read and write. Needs: An internal connection token, or OAuth. API docs: https://developers.notion.com/reference/intro (public docs). ## Microsoft 365 and identity - [Microsoft 365](https://www.resultsiq.ai/docs/tools/m365/): Uses: Users, MFA status, sign-ins and licenses. Needs: A Microsoft Entra app with Microsoft Graph permissions, and admin consent where required. API docs: https://learn.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0 (public docs). - [Google Workspace](https://www.resultsiq.ai/docs/tools/gws/): Uses: Users, MFA status, sign-ins and licenses. Needs: A Google Cloud project. A service account needs domain-wide delegation from a super admin. API docs: https://developers.google.com/workspace/admin/overview (public docs). - [Microsoft Entra ID](https://www.resultsiq.ai/docs/tools/entra/): Uses: Users, MFA status and sign-ins. Needs: Sign-in logs need Microsoft Entra ID P1 or P2, and AuditLog.Read.All or Directory.Read.All. API docs: https://learn.microsoft.com/en-us/graph/api/resources/identity-network-access-overview?view=graph-rest-1.0 (public docs). - [Okta](https://www.resultsiq.ai/docs/tools/okta/): Uses: Users, MFA status and sign-ins. Needs: A scoped OAuth 2.0 service app (Okta’s recommendation) or an API token. API docs: https://developer.okta.com/docs/api/openapi/okta-management/guides/overview (public docs). - [JumpCloud](https://www.resultsiq.ai/docs/tools/jumpcloud/): Uses: Users, MFA status and sign-ins. Needs: An admin API key. An admin with the Billing role has to turn on API access. API docs: https://docs.jumpcloud.com/ (public docs). - [Duo](https://www.resultsiq.ai/docs/tools/duo/): Uses: MFA status and sign-ins. Needs: An Owner creates an Admin API application. Duo Essentials, Advantage or Premier; each account has its own API hostname. API docs: https://duo.com/docs/adminapi (public docs). - [CIPP](https://www.resultsiq.ai/docs/tools/cipp/): Uses: MFA status and sign-ins. Needs: An API client set up in CIPP (Entra client credentials), against your own CIPP address. API docs: https://docs.cipp.app/api-documentation/setup-and-authentication (public docs). - [Microsoft Purview](https://www.resultsiq.ai/docs/tools/purview/): Uses: Audit log searches, eDiscovery, sensitivity labels and data loss prevention. Needs: Through Microsoft Graph, with a Microsoft Entra app. API docs: https://learn.microsoft.com/purview/developer/microsoft-purview-sdk-documentation-overview (public docs). ## Network - [Cisco Meraki](https://www.resultsiq.ai/docs/tools/meraki/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: An API key from Organization > API & Webhooks. API docs: https://developer.cisco.com/meraki/api-v1/getting-started/ (public docs). - [Ubiquiti UniFi](https://www.resultsiq.ai/docs/tools/unifi/): Uses: Device status and uptime and configuration and firmware. Needs: A Site Manager API key from unifi.ui.com, under Settings > API Keys. It’s read-only for now. API docs: https://developer.ui.com/site-manager/v1.0.0/gettingstarted (public docs). - [Fortinet FortiGate](https://www.resultsiq.ai/docs/tools/fortigate/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: The full REST reference is on the Fortinet Developer Network, which needs two Fortinet employees to sponsor your account. API docs: https://fndn.fortinet.net/ (partner access). - [SonicWall](https://www.resultsiq.ai/docs/tools/sonicwall/): Uses: Configuration and firmware. Needs: A full admin turns on API access in Device > Settings > Administration. API docs: https://sonicos-api.sonicwall.com (public docs). - [Auvik](https://www.resultsiq.ai/docs/tools/auvik/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: A per-user API key. The address depends on your region. API docs: https://support.auvik.com/hc/en-us/articles/360031007111-Auvik-API-Integration-Guide (public docs). - [Domotz](https://www.resultsiq.ai/docs/tools/domotz/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: An API key from Portal Settings > API Key. API docs: https://portal.domotz.com/developers/ (public docs). - [Liongard](https://www.resultsiq.ai/docs/tools/liongard/): Uses: Configuration and firmware and alerts. Needs: An access key ID and secret. The address is your own Liongard instance. API docs: https://docs.liongard.com/reference/developer-guide (public docs). - [PRTG](https://www.resultsiq.ai/docs/tools/prtg/): Uses: Device status and uptime and alerts. Needs: An API key from Account Settings > My Account > API Keys. API docs: https://www.paessler.com/support/prtg/api/v2/overview/index.html (public docs). - [Cisco Catalyst Center](https://www.resultsiq.ai/docs/tools/catalyst/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: Catalyst Center credentials, exchanged for a token that lasts 60 minutes. API docs: https://developer.cisco.com/docs/catalyst-center/getting-started/ (public docs). - [Aruba Central](https://www.resultsiq.ai/docs/tools/aruba/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: New Central uses a personal API client in HPE GreenLake. Classic Central uses an API Gateway token. API docs: https://developer.arubanetworks.com/new-central/docs/generating-and-managing-access-tokens (public docs). Classic Central: https://developer.arubanetworks.com/hpe-aruba-networking-central/docs/rest-api-getting-started. - [Ruckus](https://www.resultsiq.ai/docs/tools/ruckus/): Uses: Device status and uptime, configuration and firmware and alerts. Needs: RUCKUS One has regional addresses. SmartZone has an API guide for each release. API docs: https://docs.ruckus.cloud/api (public docs). SmartZone: https://support.ruckuswireless.com/documents/6125-ruckus-smartzone-lt-ga-public-api-reference-guide-sz144-7-3-0. - [WatchGuard Cloud](https://www.resultsiq.ai/docs/tools/watchguard/): Uses: Configuration and firmware and alerts. API docs: https://www.watchguard.com/help/docs/API/Content/en-US/home.html (public docs). ## Billing and accounting - [QuickBooks Online](https://www.resultsiq.ai/docs/tools/qbo/): Uses: Invoices. Needs: An app on the Intuit Developer portal. Intuit’s free Builder tier caps some read calls. API docs: https://developer.intuit.com/app/developer/qbo/docs/get-started (public docs). - [Xero](https://www.resultsiq.ai/docs/tools/xero/): Uses: Invoices. Needs: An OAuth 2.0 app. Xero’s free Starter tier allows five connections, and paid tiers allow more. API docs: https://developer.xero.com/documentation/getting-started-guide/ (public docs). - [Stripe](https://www.resultsiq.ai/docs/tools/stripe/): Uses: Invoices. Needs: An API key from your Stripe account. API docs: https://docs.stripe.com/api (public docs). - [Sherweb](https://www.resultsiq.ai/docs/tools/sherweb/): Uses: Costs and usage. Needs: API keys from the Security > APIs section of the Sherweb partner portal. API docs: https://developers.sherweb.com/docs/get-started (partner access). - [QuoteWerks](https://www.resultsiq.ai/docs/tools/quotewerks/): Uses: Quotes. Needs: QuoteWerks Web; the desktop edition has no web API. The key is under Setup > Options > Zapier and API. API docs: https://qwwapi.quotewerks.com/docs (public docs). Note: QuoteWerks connects through its QuoteWerks Web API. The desktop edition has no web API. - [Sage Intacct](https://www.resultsiq.ai/docs/tools/intacct/): Uses: Accounting data, once Sage approves the connection. Needs: A Web Services license (sender ID) from Sage. The connection depends on Sage’s approval. API docs: https://developer.intacct.com/ (partner access). Note: Sage opens the Intacct API through its developer program, so this connection depends on Sage’s approval. - [Pax8](https://www.resultsiq.ai/docs/tools/pax8/): Uses: Costs and usage. Needs: API credentials from the Pax8 Integrations Hub, created by a Partner Admin. API docs: https://devx.pax8.com/docs/introduction (partner access). Note: Pax8 opens its API to its partners, so Control Center connects through your own Pax8 partner account. - [ConnectWise CPQ](https://www.resultsiq.ai/docs/tools/cwcpq/): Uses: Quotes, once ConnectWise approves the connection. Needs: The docs need a ConnectWise Developer Network account. ConnectWise opens the CPQ API to its program partners. API docs: https://developer.connectwise.com/Products/ConnectWise_CPQ (partner access). Note: ConnectWise opens the CPQ API to its own program partners, so this connection depends on ConnectWise. - [Gradient MSP](https://www.resultsiq.ai/docs/tools/gradient/): Uses: Billing data, once Gradient approves the connection. Needs: Vendors get an API key through Gradient’s Technology Alliances team, and each MSP adds its own partner key. API docs: https://api-docs.meetgradient.com/docs/getting-started (partner access). Note: Gradient connects outside platforms through its alliance program, so this connection depends on Gradient. - [Microsoft Partner Center](https://www.resultsiq.ai/docs/tools/partnercenter/): Uses: Costs and usage. Needs: For Microsoft CSP partners. API docs: https://learn.microsoft.com/en-us/partner-center/developer/partner-center-rest-api-reference (public docs). - [Ingram Micro Xvantage](https://www.resultsiq.ai/docs/tools/ingram/): Uses: Costs and usage. Needs: For Ingram Micro reseller accounts. API docs: https://developer.ingrammicro.com/reseller/getting-started (public docs). - [Quoter](https://www.resultsiq.ai/docs/tools/quoter/): Uses: Quotes. API docs: https://docs.quoter.com/ (public docs). ## Security training and compliance - [KnowBe4](https://www.resultsiq.ai/docs/tools/knowbe4/): Uses: Training completion and phishing tests. Needs: The reporting API comes with the Platinum, Diamond, SAT Foundation and SAT Advanced plans. The address depends on your region. API docs: https://developer.knowbe4.com/rest/reporting (public docs). Note: KnowBe4’s reporting API comes with its Platinum, Diamond, SAT Foundation and SAT Advanced plans. - [Huntress Security Awareness Training](https://www.resultsiq.ai/docs/tools/huntresssat/): Uses: Phishing tests. Needs: The same Huntress API key. Phishing campaign results are part of the Huntress API. API docs: https://api.huntress.io/docs (public docs). - [Vanta](https://www.resultsiq.ai/docs/tools/vanta/): Uses: Training completion and compliance controls. Needs: An admin creates an OAuth app in Settings > Developer Console. API docs: https://developer.vanta.com/ (public docs). - [Drata](https://www.resultsiq.ai/docs/tools/drata/): Uses: Compliance controls. Needs: An API key or OAuth. Some endpoints need specific plan features. API docs: https://developers.drata.com/ (public docs). ## Vulnerability scanning - [Tenable](https://www.resultsiq.ai/docs/tools/tenable/): Uses: Vulnerabilities, assets and scans. Needs: Includes an MSSP Portal API that works across clients. API docs: https://developer.tenable.com/reference (public docs). - [Qualys](https://www.resultsiq.ai/docs/tools/qualys/): Uses: Vulnerabilities, assets and scans. API docs: https://docs.qualys.com/en/vm/qweb-all-api/mergedProjects/qapi-user/get_started/get_started.htm (public docs). - [Rapid7 InsightVM](https://www.resultsiq.ai/docs/tools/insightvm/): Uses: Vulnerabilities, assets and scans. API docs: https://help.rapid7.com/insightvm/en-us/api/index.html (public docs). - [ConnectSecure](https://www.resultsiq.ai/docs/tools/connectsecure/): Uses: Vulnerabilities and assets. Needs: The API reference is inside the ConnectSecure portal, under your profile. API docs: https://cybercns.atlassian.net/wiki/spaces/CVB/pages/2128314664/API+FAQ (docs need a login). Note: ConnectSecure’s API reference is inside its portal, under your profile. - [runZero](https://www.resultsiq.ai/docs/tools/runzero/): Uses: Assets. API docs: https://help.runzero.com/docs/leveraging-the-api/ (public docs). ## DNS filtering - [DNSFilter](https://www.resultsiq.ai/docs/tools/dnsfilter/): Uses: Filtering policies and blocked threats. Needs: An API key from Account Settings in the dashboard. API docs: https://api.dnsfilter.com/docs (public docs). - [Cisco Umbrella](https://www.resultsiq.ai/docs/tools/umbrella/): Uses: Filtering policies, agent health and blocked threats. Needs: An Umbrella API key and secret, exchanged for an OAuth 2.0 token. API docs: https://developer.cisco.com/docs/cloud-security/umbrella-api-getting-started/ (public docs). - [Cloudflare Zero Trust](https://www.resultsiq.ai/docs/tools/cloudflare/): Uses: Filtering policies, agent health and blocked threats. Needs: A scoped API token with Zero Trust permissions. API docs: https://developers.cloudflare.com/cloudflare-one/api-terraform/ (public docs). - [Zscaler](https://www.resultsiq.ai/docs/tools/zscaler/): Uses: Filtering policies and agent health. Needs: API clients and roles in ZIdentity (Zscaler OneAPI). Zscaler now calls the older ZIA API legacy. API docs: https://help.zscaler.com/zia/getting-started-zia-api (public docs). - [SafeDNS](https://www.resultsiq.ai/docs/tools/safedns/): Uses: Filtering policies. Needs: Your SafeDNS account sign-in. The API is in beta. API docs: https://docs.safedns.com/books/rest-api/page/rest-api-guide (public docs). - [WebTitan](https://www.resultsiq.ai/docs/tools/webtitan/): Uses: Filtering policies and blocked threats. API docs: https://apidoc.webtitancloud.com/ (public docs). ## Passwords - [1Password](https://www.resultsiq.ai/docs/tools/1password/): Uses: Vault items and user provisioning. Needs: 1Password Business, with a token from the integration you set up, such as Events Reporting. API docs: https://www.1password.dev/events-api (public docs). - [Bitwarden](https://www.resultsiq.ai/docs/tools/bitwarden/): Uses: User provisioning. Needs: A Teams or Enterprise organization. The organization API key is in the Admin Console; US, EU and self-hosted addresses differ. API docs: https://bitwarden.com/help/public-api/ (public docs). - [Passportal](https://www.resultsiq.ai/docs/tools/passportal/): Uses: Vault items. Needs: An API key generated in Passportal. API docs: https://developer.n-able.com/passportal/docs/introduction (public docs). - [Devolutions](https://www.resultsiq.ai/docs/tools/devolutions/): Uses: Vault items and user provisioning. Needs: Devolutions Server: an application key and secret. The reference is built into your server. API docs: https://docs.devolutions.net/server/web-interface/utilities/api-documentation (public docs). - [Keeper Security](https://www.resultsiq.ai/docs/tools/keeper/): Uses: User provisioning. API docs: https://docs.keeper.io/enterprise-guide/keeper-msp/account-management-apis (public docs). ## Admin rights and allowlisting - [ThreatLocker](https://www.resultsiq.ai/docs/tools/threatlocker/): Uses: Approval requests. Needs: An API user (token or OAuth 2.0) created in the portal. The address is your own instance. API docs: https://threatlocker.kb.help/api-documentation/ (public docs). - [Admin By Request](https://www.resultsiq.ai/docs/tools/abr/): Uses: Approval requests. Needs: Included with your license. The API key is in Tenant Settings, and the address depends on your data center. API docs: https://docs.adminbyrequest.com/integrations/public-api.htm (public docs). ## Remote access - [ConnectWise ScreenConnect](https://www.resultsiq.ai/docs/tools/screenconnect/): Uses: Remote sessions. Needs: Install the RESTful API Manager extension. API docs: https://docs.connectwise.com/ConnectWise_ScreenConnect_Documentation/Supported_extensions/Administration/RESTful_API_Manager (public docs). Note: ScreenConnect connects through its RESTful API Manager extension. - [TeamViewer](https://www.resultsiq.ai/docs/tools/teamviewer/): Uses: Remote sessions and devices. API docs: https://webapi.teamviewer.com/api/v1/docs/index (public docs). - [Splashtop](https://www.resultsiq.ai/docs/tools/splashtop/): Uses: Remote sessions and devices. Needs: Splashtop’s Enterprise plans. API docs: https://support-splashtopbusiness.splashtop.com/hc/articles/16772899906459 (public docs). Note: Splashtop’s API comes with its Enterprise plans. - [BeyondTrust Remote Support](https://www.resultsiq.ai/docs/tools/beyondtrust/): Uses: Remote sessions. API docs: https://docs.beyondtrust.com/rs/reference (public docs). ## Teams, chat and phones - [Microsoft Teams](https://www.resultsiq.ai/docs/tools/teams/): Uses: Messages. Needs: A Microsoft Entra app with Microsoft Graph permissions. API docs: https://learn.microsoft.com/en-us/graph/api/resources/teams-api-overview (public docs). - [Slack](https://www.resultsiq.ai/docs/tools/slack/): Uses: Messages. Needs: A Slack app with a bot or user token. API docs: https://docs.slack.dev/apis/web-api/ (public docs). - [Zoom](https://www.resultsiq.ai/docs/tools/zoom/): Uses: Messages. Needs: An OAuth or Server-to-Server OAuth app with the scopes it needs. API docs: https://developers.zoom.us/docs/api/ (public docs). - [RingCentral](https://www.resultsiq.ai/docs/tools/ringcentral/): Uses: Messages. Needs: An app in the RingCentral Developer Console (client ID and secret). Some scopes need RingCentral’s approval. API docs: https://developers.ringcentral.com/api-reference (public docs). - [3CX](https://www.resultsiq.ai/docs/tools/3cx/): Uses: Users and call control. Needs: An 8SC+ license. The API client is created under Admin Console > Integrations > API. API docs: https://www.3cx.com/docs/configuration-rest-api/ (public docs). Note: 3CX’s API needs an 8SC+ license and covers users and call control. ## Cloud and files - [Microsoft Azure](https://www.resultsiq.ai/docs/tools/azure/): Uses: Costs and usage. Needs: A Microsoft Entra app with an Azure role on the subscriptions it reads. API docs: https://learn.microsoft.com/en-us/rest/api/azure/ (public docs). Cost Management: https://learn.microsoft.com/en-us/rest/api/cost-management/. - [AWS](https://www.resultsiq.ai/docs/tools/aws/): Uses: Costs and usage. Needs: AWS charges $0.01 for each Cost Explorer API request. API docs: https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/Welcome.html (public docs). - [Dropbox](https://www.resultsiq.ai/docs/tools/dropbox/): Uses: Users. API docs: https://www.dropbox.com/developers/documentation/http/documentation (public docs). - [Box](https://www.resultsiq.ai/docs/tools/box/): Uses: Users. Needs: An OAuth 2.0 access token. API docs: https://developer.box.com/reference (public docs). - [Wasabi](https://www.resultsiq.ai/docs/tools/wasabi/): Uses: Costs and usage. API docs: https://docs.wasabi.com/apidocs/api-guides (public docs). ## Reporting and lifecycle - [ScalePad](https://www.resultsiq.ai/docs/tools/scalepad/): Uses: Warranties. Needs: Lifecycle Manager’s API needs a higher subscription tier and an administrator’s API key. US only. API docs: https://developer.scalepad.com/ (public docs). - [Power BI](https://www.resultsiq.ai/docs/tools/powerbi/): Uses: Sending your metrics to dashboards. Needs: A Microsoft Entra app. A Power BI admin allows service principal access. API docs: https://learn.microsoft.com/en-us/rest/api/power-bi/ (public docs). - [Grafana](https://www.resultsiq.ai/docs/tools/grafana/): Uses: Sending your metrics to dashboards. Needs: A service account token. API docs: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/ (public docs). - [Datadog](https://www.resultsiq.ai/docs/tools/datadog/): Uses: Sending your metrics to dashboards. Needs: An API key, plus an application key for some endpoints. API docs: https://docs.datadoghq.com/api/latest/ (public docs). - [CloudRadial](https://www.resultsiq.ai/docs/tools/cloudradial/): Uses: Companies, users, endpoints, assessments and the service catalog. API docs: https://support.cloudradial.com/hc/en-us/articles/360050153571-Using-the-CloudRadial-API (public docs). - [Crewhu](https://www.resultsiq.ai/docs/tools/crewhu/): Uses: Surveys, users and contest metrics. API docs: https://get-help-tnt.crewhu.com/hc/en-us/articles/360002286094 (public docs). ## Automation platforms - [Rewst](https://www.resultsiq.ai/docs/tools/rewst/): Uses: Starting your workflows. Needs: Rewst’s API is GraphQL, and Rewst workflows can also start from webhook triggers. API docs: https://docs.rewst.help/documentation/automations/actions-in-rewst/generic-graphql-request-action (public docs). - [Power Automate](https://www.resultsiq.ai/docs/tools/powerautomate/): Uses: Starting your workflows. Needs: Through the Dataverse Web API, for flows that live in solutions. API docs: https://learn.microsoft.com/en-us/power-automate/manage-flows-with-code (public docs). - [n8n](https://www.resultsiq.ai/docs/tools/n8n/): Uses: Starting your workflows. Needs: Not on the free trial: n8n Cloud Starter, Pro or Enterprise, or any self-hosted edition. API docs: https://docs.n8n.io/connect/n8n-api (public docs). - [Zapier](https://www.resultsiq.ai/docs/tools/zapier/): Uses: Starting your workflows. Needs: Zapier’s Workflow API needs a publicly listed Zapier integration or White Label onboarding. API docs: https://docs.zapier.com/powered-by-zapier/zap-creation/getting-started (partner access). - [Make](https://www.resultsiq.ai/docs/tools/make/): Uses: Starting your workflows. Needs: Use your organization’s zone address, such as eu1 or us1. API docs: https://developers.make.com/api-documentation (public docs). ## No public API yet We couldn’t find a public API for these tools, so Control Center can’t connect to them yet. If your vendor gives you API docs for one of them, send them to us and we’ll check them. - Todyl (Endpoint security) - ConnectWise SIEM (SIEM and managed SOC) - Barracuda XDR (SIEM and managed SOC) - IT Portal (SI Portal) (Documentation) - ITBoost (Documentation) - Breach Secure Now (Security training and compliance) - Hook Security (Security training and compliance) - Apptega (Security training and compliance) - Compliance Scorecard (Security training and compliance) - Cynomi (Security training and compliance) - RapidFire VulScan (Vulnerability scanning) - RapidFire Network Detective (Vulnerability scanning) - RapidFire Cyber Hawk (Vulnerability scanning) - Nodeware (Vulnerability scanning) - AutoElevate (Admin rights and allowlisting) - BrightGauge (Reporting and lifecycle) - SmileBack (Reporting and lifecycle) ## Not listed? If it has a documented API, Control Center can connect to it. Email connor.reece@resultsiq.ai with the tool’s name and a link to its API docs. --- ## Contact - connor.reece@resultsiq.ai · (904) 895-7558 · ResultsIQ LLC, 7901 4th St N, Ste 300, St. Petersburg, FL 33702