For MSPs whose clients are asking for AI
Implement AI for your clients without a new stack
“They're seeing speed and consistency in the responses. Their tickets are being handled more efficiently.”
Thanksgiving Offer
$50$100USD per technician per month*
Prefer a walkthrough? Book a demo
How does an MSP implement AI for a client without a separate stack?
Through the NetZen you already run. A client asks you to set up AI for their staff (an example, not a customer). Instead of standing up tools on their side, you add their handbook and procedures to the knowledge base, scoped to that client, and connect the chat and email their users already have, web chat or your client portal. The assistant answers from their own documents and cites the source, under your MSP's name.
Then you build what they need in Automations: scripts on their devices, tasks in their SaaS tenant and business apps, run books for recurring requests, each scoped to that client and run after the approvers you set. On their tickets the AI investigates the device and applies the fixes you enabled, and every run is in History.
What does the client get, and what do they need to buy?
Their users get an assistant that knows their procedures, opens tickets with the right details, reports progress and fixes devices through the automations you chose; your technicians get the handoff with findings attached. Built-in cloud tenant checks are read-only; changes to a client's apps run through automations your technicians build and test first.
The client needs no AI subscriptions, tools or staff of its own: it all runs in your seat. NetZen is the full PSA, service desk and RMM, priced per technician with AI and automations included; client devices, clients and end users are not billed. What you charge each client for the AI you implement is your decision.
What would separate AI products have cost instead?
Matt Kerekes, CEO, Cinema Hero Solutions, an MSP serving cinema and hospitality operators, had looked at tools that each handled one narrow task on its own subscription. His estimate: covering every function his team needed with separate AI products would run about $200 a month per person.
The customer's own estimate, not a measured result. Read the case study.
Before you install anything
No. Each knowledge source is scoped to a client or to all clients, and client-scoped content is used only on that client’s tickets. Internal documents stay with your team and the AI; external ones also appear in that client’s portal.
As your MSP. End users see your organization’s name followed by AI, on the ticket and in your client portal where they follow tickets and answer approvals.
Changes started from tickets wait for the approver you set: the requester, your technicians or the client’s site manager. The AI cannot approve its own changes, and every run is logged with its status, who started it and any error.
The built-in cloud packs are read-only checks. Changes to a client’s apps run through the API or browser automations your technicians build, test, enable and scope to that client.
Begin the free work-account trial, no card. Tour the sample client, load one real client's handbook and put their first automation on a ticket.