Operations

    A helpdesk built into your RMM

    The Ticket System turns NetLock RMM into a lightweight helpdesk β€” capturing requests from end users or inbound email, driving them to resolution, and recording every action with its own contacts, SLA engine, and per-ticket history.

    Try Demo
    Ticket lifecycle

    From Open to Closed, your way

    A ticket moves through five statuses β€” with free any-to-any transitions, so you are never boxed in by a rigid workflow.

    1

    Open

    A newly raised request, waiting to be picked up.

    2

    In Progress

    An operator is actively working the ticket.

    3

    Waiting

    Paused β€” waiting on the customer or a third party.

    4

    Resolved

    Work is done and the resolution is awaiting confirmation.

    5

    Closed

    Finished. Closing never deletes a ticket β€” it stays fully searchable.

    The ticket detail view

    Everything about a ticket, in six tabs

    Open a ticket and every part of it β€” the conversation, the metadata, the history β€” is one click away.

    Conversation

    The message thread β€” internal notes, outbound replies, and inbound email β€” in one place.

    Details

    Status, priority, assignee, department, contact, type, and labels.

    Time Tracking

    Time logged against the ticket, automatically and by hand.

    History

    The ticket's own audit log β€” every change recorded, separate from the global Events and Audit streams.

    Attachments

    Every file from replies, inbound email, or direct upload, gathered together.

    NEW

    AI

    Summarise conversations in seconds, ask scoped questions about the ticket history, and get one-click answer drafts based on prior replies β€” powered by your own AI provider (ChatGPT, Claude or self-hosted).

    Departments, SLA & time

    Structured for real support teams

    Departments, service levels, and time tracking keep the helpdesk organised and accountable.

    Departments

    Each department carries its own IMAP/SMTP mailbox, notification recipients, members, and webhooks.

    SLA engine

    Response and resolution targets in wall-clock hours, with sla_warning and sla_breached events as deadlines approach.

    Time tracking

    An automatic timer runs while a ticket is open, alongside manual entries β€” all visible on a daily calendar.

    Measured and connected

    A statistics dashboard and outbound webhooks turn the helpdesk into something you can report on and integrate.

    Statistics dashboard

    A five-tab dashboard covering volume, resolution times, SLA compliance, and per-operator workload.

    Webhooks & notifications

    Per-department webhooks fire on eight ticket events, alongside email and live in-app notifications.

    Run support without leaving your RMM

    One console for managing endpoints and resolving the tickets they generate.

    View Pricing