AI for MSPs, across your PSA, RMM and Microsoft 365

Switchboard brings an engineered system for MSP work: platform-specific skills, vetted playbooks and enforced access controls. We build the integrations, test their behavior and permission boundaries, and check playbook instructions against the tools and data available. Skills handle specific jobs; playbooks guide the investigation, cross-checks and limits of what can be concluded. You can inspect the tool calls behind an answer. Your admin controls who can reach each system, credentials stay server-side, and Switchboard sessions run in isolated environments. Access is read-only today. Any change a platform could make is held back — refused by our server before anything reaches the platform — until a person switches it on, and nothing is switched on today. Your preferred AI client can be your interface to this controlled access; your chosen client’s own data-handling terms still apply.

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.

Hosted and external AI connections provide read-only access. ConnectWise Automate, ConnectWise Asio, Pax8, Webroot, Xero, Axcient x360Recover, Ninety, SentinelOne and ConnectWise PSA are read-only today: no credential we issue carries a write scope, and where an agent's code holds write actions, each is held back — refused by our server before anything reaches the platform — until a person switches it on; nothing is switched on today. Nothing in those platforms can be created, edited or deleted from a session. Platforms with a named write surface include Cisco Meraki, with exactly five device actions — ping, cable test, switch-port cycle, LED blink and reboot; and ConnectWise ScreenConnect, whose write surface — session actions, machine commands and an access-issuance action — ships unreachable, with nothing scoped to it. Microsoft 365 and Google Workspace also need capability-pack consent from the client's Global Admin or super admin, tenant by tenant. That vendor consent is separate from approval for a call and does not enable writes through your external AI connector.

Yes. Once your systems are connected, tell Grace, your in-app guide, the job you want done, for example “give me a morning report of which clients' backups failed”. She sets up the agent (name, brief, which Space it works in, which systems it may read) and you confirm it in the app, or you make one yourself with New agent. There is no limit on how many you make. Each one is read-only, keeps notes on what it learns about your MSP, and works in the Space you put it in. The AI Agents page shows twelve examples we designed, from a client churn radar to backup assurance.

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 Viewer service-user token on SentinelOne, a partner key on Trend Vision One that we use for reads only, 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.

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, ImmyBot, NinjaOne, SentinelOne, and Trend Vision One. In flight: Datto RMM 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.

Dedicated starts from $1,386/mo for three users, including your own EdgeKeeper Server and database. Hosted starts from $387/mo for three users on shared infrastructure and supports up to five. Dedicated is required for six through ten users; above ten, talk to Brian. Microsoft 365 and Google Workspace tenants count together: the first 5 are included on Hosted, and the first 10 on Dedicated. Each additional tenant is $10 per month. Dedicated includes all platforms and all Switchboard usage, with no extra token charges, per-question fees or usage top-ups. Reasonable rate limits per user and platform prevent abuse. Hosted includes up to 5 connected platforms, 50 questions per team per day, 3 concurrent sessions, 5 scheduled report runs per week and refreshes every 6 hours. Both packages process requests privately, with your MSP’s data isolated and no separate token bill. Your own AI client’s subscription is separate. On Dedicated, your EdgeKeeper Server and database are provisioned at signup. No onboarding fee and no separate setup wait. Connect your systems and get started. Headless MCP access is included in every seat. Connect your own Claude, ChatGPT or Copilot at no extra cost. Guidance, shared playbooks and automations we release for everyone are included with Dedicated. Bespoke automation builds are scoped separately. Any change a platform could make is held back — refused by our server before anything reaches the platform — until a person switches it on, and nothing is switched on today. The trial covers seats and database for 14 days; the server bills from activation. See Pricing for annual rates and a complete estimate.

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. Those calls give you evidence to check. AI can still misinterpret a result or make a mistake, so review the source before acting on an answer.

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.