Insights & Control

    An AI assistant, right in the console

    AI Chat puts a conversational assistant inside NetLock RMM β€” for quick lookups, explaining logs, and drafting wording, without leaving the tools you already work in.

    Try Demo
    The chat experience

    A conversation that keeps up

    AI Chat is a full conversational surface, not a one-shot prompt box.

    Streamed answers

    Responses stream in incrementally, rendered as markdown, with a typing indicator and a stop control.

    Organised conversations

    Past conversations are grouped by recency, with search, rename, and delete.

    Context-aware

    Launched from an Analyze with AI action, the chat opens with the relevant record's context already in place.

    Ask anything

    General-purpose Q&A β€” explain a log line, draft a message, or talk through an approach.

    File attachments

    Bring your files into the conversation

    Attach text-based files so the assistant sees both your question and the content it refers to.

    Text-based files

    Attach text files across more than forty supported extensions β€” logs, configs, scripts, and more.

    Generous limits

    Up to ten files per message, each as large as 10 MB.

    Content in context

    File contents are included alongside your prompt so answers can reason about the actual data.

    In Action

    See it in action

    The AI Assistant opens inside any tool, sees only the data of that tool, and answers a scoped question with a structured result. Here applied to a Windows Event Log Viewer session β€” 100 entries analysed, root cause identified in seconds.

    Windows Event Log Analysis on a remote endpoint

    Windows Event Log Analysis on a remote endpoint

    1

    Context-aware

    The AI sees only the active tool β€” in this case the Event Log Viewer of one specific endpoint (WINSRV2025). No other data is shared.

    2

    Structured output

    Tables, key findings, root-cause hints β€” formatted Markdown with event IDs and meaning, not a wall of text.

    3

    Same scope, same thread

    Ask follow-up questions in the same conversation β€” every reply stays inside the active tool context.

    Optimising a script in the editor

    The same assistant sits beside the Scripts editor. It already knows the open script, suggests a better version on request, and inserts it with a single click.

    Improving a PowerShell script in the Scripts editor

    Improving a PowerShell script in the Scripts editor

    1

    Knows the open script

    The panel opens next to the editor with the current script as context β€” name, platform, shell and code (OS Information Β· Windows/PowerShell).

    2

    Optimises on request

    Ask β€œCan you improve the script?” and it returns a modernised version β€” Get-CimInstance instead of the deprecated Get-WmiObject, error handling, and a clear list of changes.

    3

    Apply with one click

    Apply Code inserts the revised script straight into the editor β€” no copy-paste, ready to save and run.

    Building a sensor from a sentence

    Open the Sensors editor, describe what you want to watch for, and the assistant picks the right sensor type, fills in the event ID, and configures the whole form.

    Creating a failed-login sensor in the Sensors editor

    Creating a failed-login sensor in the Sensors editor

    1

    Right sensor, right event

    Ask for a sensor to detect failed Windows logins and it chooses a Windows Security Eventlog sensor on Event ID 4625 β€” the standard failed-logon event β€” with a sensible check interval and severity.

    2

    Explains its choices

    Alongside the config it returns a Key Details table and notes β€” why Event ID 4625, the Audit Logon Events policy it depends on, and how to narrow alerts with an expected_result regex.

    3

    Configures the form

    Apply Config fills in name, platform, severity, schedule, category and the Eventlog rule in one step β€” review and save, no manual field-by-field setup.

    Polished replies and instant ticket summaries

    Inside a ticket, the assistant cleans up your reply before it goes out β€” and answers questions about the whole ticket on demand.

    AI Improve and ticket summaries in the ticket system

    AI Improve and ticket summaries in the ticket system

    1

    One-click reply polish

    Write a rough reply β€” β€œPlz senD Me PICTURES of your tASK Manager…” β€” hit AI Improve, and it returns clear, professional wording ready to send.

    2

    Summarise any ticket

    Summarize Ticket condenses the whole conversation into a short overview with status, priority, assignee and contact β€” ideal when picking up a ticket cold.

    3

    Ask about the ticket

    Ask a question in plain language β€” β€œWhat is this ticket about?” β€” and get an answer grounded in that ticket's own notes and replies.

    Your provider, your control

    AI is opt-in, configurable, and fully under administrator control.

    Bring your own provider

    The AI provider, API key, and model are configured under Settings β†’ AI/LLM. AI Chat stays off until an administrator enables it.

    Permission-gated

    A system-wide AI toggle plus a per-user AI Chat permission decide exactly who can open the assistant.

    For your end users

    Sovereign AI for your whole team β€” right in the tray icon

    Give every employee a private AI assistant they open straight from the NetLock RMM tray icon. Sovereign, fully controlled by you, and end-to-end encrypted β€” no shadow IT, no sending your people off to yet another external chatbot.

    End-to-end encrypted β€” true zero-knowledge

    Conversations are encrypted on the device with the user's own password before they ever leave the machine. The NetLock RMM server only ever stores ciphertext it cannot read, and administrators never see a single message. If a user forgets their password, the history is gone for good β€” and that is exactly the point.

    Right in the tray icon

    Users open the AI chat from the system tray β€” no separate app, no browser tab, no extra portal to sign into. It is simply there the moment they need it.

    Your provider, your budget

    Requests run through the AI provider you configured, or managed NetLock AI. Set monthly token limits per user and an overall cap per tenant so spend never surprises you.

    You stay in control

    New accounts stay inactive until you approve them β€” or switch on per-tenant auto-approval. Enforce password rules and require your terms & privacy policy to be accepted first.

    Usage you can actually see

    Live percentage usage with an automatic monthly reset, per-user and per-tenant statistics, and one-click usage reset β€” all from the web console.

    Self-service accounts

    Employees register once with their email (or a free-form username) and a password. Activation, limits and access stay centrally managed by your team.

    Fully white-label

    Every label, button and message in the tray chat is configurable through policy β€” match it to your brand, tone and language.

    Put an AI assistant in your console

    Configure your own provider and switch on AI Chat for the operators who need it.

    View Pricing