AI for MSPs
One AI session patched into the whole stack — RMM, PSA, Microsoft 365, distribution, network, security, backup, books. Every answer traced to a real tool call against your systems. Read-only by default, and on most platforms read-only by construction.
What MSPs actually ask
The questions, not the demo script.
Most MSP AI tools demo against a sample dataset. Every prompt below is lifted verbatim from a live integration page on this site, one per platform — these are the questions the engine answers today, against your own tenant.
The board
13 platforms answering today.
An AI assistant for MSPs is worth exactly what it can reach. Here is the whole board, with the real status on each one — 13 live and 3 in flight. Each page lists every skill that platform ships with and, just as plainly, what it cannot do.
In the day
Where it fits in the day.
Four moments where an MSP AI session earns its keep. Every capability named here is shipped and documented on the platform page it links to.
NOC triage
Something is down and nobody knows where to start. Ask how many agents are offline across the whole tenant and it counts them in Automate; ask which automation tasks failed on the last run and it reads them out of Asio; ask why wireless dropped at the clinic this morning and it works the Meraki network-health tools for auth, DHCP and DNS. Meraki is the one place a read can become an action, and only five of them — ping, cable test, switch-port cycle, LED blink, and reboot.
Grounded in ConnectWise Automate · ConnectWise Asio · Cisco Meraki
Service desk
The queue is the question. How many tickets are open with nobody assigned, across every board? What's been sitting on Help Desk longer than a week? Who logged hours against the migration project last month? ConnectWise PSA answers all of it by reading, and it carries the only three writes on the whole board — create a ticket, update a ticket, add a note. No invoice, agreement, company, configuration, project or time entry can be created, edited or deleted from a session.
Grounded in ConnectWise PSA
Account management and QBRs
The review deck is a set of questions nobody has time to chase. Which agreements renew this quarter and what are they worth? How many seats is this client paying for on each Microsoft SKU but not assigning? Who owes us money more than 60 days past due, and what does their month-to-date P&L look like? Four systems, one session — and every number in the deck traces back to the call that produced it.
Grounded in ConnectWise PSA · Microsoft 365 · Pax8 · Xero
Vendor and licensing ops
The margin leak is usually in the paperwork. Which clients hold the same product on both annual and month-to-month terms? What's on the next Pax8 invoice that wasn't on the last one, and what's accruing toward it right now? How many Business Standard seats is this client paying for, and who actually holds them? Which Meraki licenses expire in the next 90 days? All reads — Pax8 has a single GET method behind it, so nothing here can place an order or move a seat count.
Grounded in Pax8 · Google Workspace · Cisco Meraki
Field notes
AI for MSPs, answered straight.
What can AI actually do for an MSP today?
Answer questions about your own systems, in plain English, without anyone opening five consoles. A Switchboard session is patched into the platforms you have connected — RMM, PSA, Microsoft 365, Google Workspace, distribution, network, security, backup, books — and works the same read APIs a tech would click through, then reports what came back. What it does not do is run the business for you. It reads, correlates and explains; the judgement, and on most platforms the changes, stay with your team.
Can it change things in my stack, or does it only read?
Read-only unless you deliberately grant otherwise, and on most platforms read-only is structural rather than a setting. ConnectWise Automate, ConnectWise Asio, ConnectWise ScreenConnect, Pax8, Webroot, Xero and Axcient x360Recover have no write path at all — the clients behind them implement reads only, so a write cannot be constructed. Four platforms have a named write surface, and that is the whole of it. ConnectWise PSA can create a ticket, update a ticket, and add a ticket note. Cisco Meraki has exactly five device actions: ping, cable test, switch-port cycle, LED blink, and reboot. Microsoft 365 and Google Workspace writes exist only as separate capability packs the client's own Global Admin or super admin consents to, tenant by tenant — a pack that was never granted has no token minted for it, so it cannot be used at all.
How are credentials handled?
Each platform agent authenticates with its own scoped credential, held server-side in a credential vault. Nothing sensitive ships to the browser and there is no shared master key. The shape follows whatever the vendor offers: a dedicated Integrator service account on ConnectWise Automate, an OAuth2 grant from Xero's own consent screen, a GSM-scoped Unity API client on Webroot, a partner API key from x360Portal on Axcient, a separate Entra app registration per consented pack on Microsoft 365. Each credential carries exactly the rights the admin who created it holds — a session can never see more than its credential can — and you revoke it on the vendor's side, not ours.
Which platforms are live right now?
Live on the board today: ConnectWise Automate, ConnectWise PSA, ConnectWise Asio, ConnectWise ScreenConnect, Microsoft 365, Google Workspace, Pax8, Cisco Meraki, Webroot, Xero, Axcient x360Recover, Ninety, and ImmyBot. In flight: Datto RMM, NinjaOne, and Hudu. Every one of them has its own page listing each skill it ships with and, just as plainly, the things it cannot do.
What does it cost?
The free trial is the full read-only engine against your own environment — no card, and you cancel by walking away. After that, read-only is $149/mo per platform you connect, for the whole team, with the estate cache, per-org memory, session search and tags, and every answer traced to a real tool call. Managed is quoted rather than listed, because it is a dedicated brain server and database for your org, write access designed and operated with you, and automations built for your workflows — a managed agreement, not a plan you click. Individual platform agents are also listed on their own in the app library.
How is this different from a chatbot?
A chatbot predicts an answer from what it read on the internet. Switchboard makes calls against your systems and reports what came back. Ask how many agents are offline and the session runs a named tool against your RMM, gets the list, and counts it — and you can open the tool calls behind any answer and see what was asked and what came back. An accuracy guard traces every figure in an answer to a tool result from your systems; if the data did not come back from a real call, it does not go in the answer. That is also why it will say it could not read something rather than invent a ticket count.
How long does it take to connect a platform?
An afternoon for the first one, and every platform after that is independent of it. ConnectWise Automate is a dedicated Integrator account, a read-focused user class, and your server address. Microsoft 365 is the guided connect plus the client's own Global Admin walking Microsoft's consent screens, one per pack, in a single sitting — every other tenant then connects the same way, on its own. Xero is one sign-in through Xero's consent screen, which binds every organisation you authorize in that flow. Each integration page carries its own connect steps and links out to the vendor's documentation.
The full commissioning ladder — trial, read-only, managed — is on the Switchboard sheet.
Patch your stack in.
Start the Switchboard free trial against your own environment — read-only, traced answers, live in an afternoon. The apps are on the shelf when you want them.