NetLock RMMNetLock RMM Docs
II — Console Reference

Tickets

The optional helpdesk module: ticket list and detail view, lifecycle, time tracking, statistics, and the admin areas for departments, customers, contacts, templates, labels, SLAs, and webhooks.

Tickets

10.1 Overview

The Ticket System turns NetLock RMM into a lightweight helpdesk. Tickets capture requests and incidents raised by end users or ingested from email, carry a status through to resolution, and record every action on the ticket. The module has its own contact list, its own SLA engine and its own history log on each ticket. Ticket changes are not written to the Events log; creating, changing, assigning and deleting a ticket is also recorded in the Audit log (entity type ticket).

Operators work on three pages: the Tickets list at /tickets, Time Tracking at /tickets/time-tracking, and Statistics at /tickets/statistics. Configuration sits under the same menu group (Departments, Customers, Contacts, Templates), with dialogs for Labels & Types, SLA, and per-department Webhooks. Global defaults live on Settings → Ticket System.

Tickets navigation group expanded to show Tickets, Time Tracking, Statistics, Departments, Customers, Contacts, Templates

10.2 Enabling the ticket system

The module is off by default. An operator sees the Tickets menu only when two conditions are met: the module must be turned on globally, and the operator must hold the tickets_enabled permission.

The master toggle is at Settings → Ticket System on the General tab, labelled Ticket System Enabled. One other setting on the same tab applies deployment-wide:

  • Blocked File Extensions: a chip input with one file extension per chip. Attachments with these extensions are stripped from inbound email before the ticket is created, and an internal note on the ticket names the files that were blocked. Extensions are normalised to lowercase with a leading dot, so .EXE, exe, and .exe all match.

Ticket numbers are not configured here. They come from the prefix on the customer record when the ticket belongs to a customer that sets one (see 10.11), and otherwise from the built-in default numbering, which produces identifiers such as TKT-12345678.

The Settings page itself is gated by settings_system_enabled. The two extra tabs on the same page (Labels & Types and SLA) manage the same data as the dialogs reachable from inside a ticket.

10.3 The tickets list page

Route: /tickets. The list opens on the Open tab by default, refreshes every 60 seconds in the background, and shows a toast whenever a new inbound email or reply arrives on a ticket the current user can see.

Tickets list with status tabs, filter bar, and a table of open tickets

Columns

The list carries nine columns: Ticket #, Subject, Contact, Status, Priority, Last Contact (direction badge plus a relative time), SLA (a colour-coded urgency chip), Updated, and Assigned To. Drag a column header to change the column order. The order is stored in the browser's local storage, so it is kept across sessions in the same browser but is not shared between machines.

Six tabs sit above the table: All, Open, In Progress, Waiting, Resolved, Closed. Each tab shows a live count for the current filter set; switching tabs swaps the underlying query but preserves filters, search, and column order. On the All tab, closed rows are dimmed.

Five filter dropdowns narrow the query:

  • Department: All Departments or a named department. Users without tickets_view_all_departments see only their own department regardless of this control.
  • Priority: All, Critical, High, Medium, or Low.
  • Assigned To: All, Unassigned, or any operator by username.
  • Type: options drawn from Labels & Types (see 10.14).
  • Label: All or any colour-coded label.

Filters combine. A single search field searches Ticket #, Title, Contact Email, Contact Name, and the Assigned To username at once.

Bulk toolbar

Selecting one or more rows reveals a toolbar with Close Selected, Delete Selected, and Deselect All. Close Selected moves every chosen ticket straight to Closed without asking for a closing comment. To record one, use the detail dialog (see 10.4). Delete Selected is gated by tickets_delete and deletes the tickets permanently.

10.4 The ticket detail view

Clicking a row opens the ticket detail dialog. Its title shows the ticket number followed by a coloured chip for the current status. The body is a six-tab editor: Conversation, Details, Time Tracking, History, Attachments, and AI.

Ticket detail view with the Conversation tab open in Chat View, showing inbound and outbound messages

Conversation

The Conversation tab is the main working area. A toggle at the top switches between Chat View (bubbles with alternating alignment) and List View (a denser CRM-style list). Both render the same messages in chronological order.

Every message carries a direction badge that also determines its styling:

  • Internal note: left-aligned, tinted for internal use, marked with a lock icon. Not sent to the customer.
  • Outbound: right-aligned, tinted blue, with an arrow-out icon. A public message; it is mailed to the contact through the department's SMTP when the ticket has a department with an SMTP server and a valid contact email (see below).
  • Inbound: left-aligned, tinted green, with an arrow-in icon. Ingested from the department's IMAP mailbox.

A note added through the public API keeps its line breaks when it is plain text and is shown formatted when it contains HTML; see X.9.18.

A composer sits at the bottom of the tab with three editor modes: Rich Text, HTML, and Plain Text. Regardless of mode, both a rich-text rendering and a plain-text fallback are persisted, so replies display correctly for recipients that strip HTML. A lock/globe icon toggles the outgoing message between Internal note and Outbound before sending, and a Template Picker button inserts a saved response (see 10.13); the text stays editable after insertion.

A public reply is mailed with the department and contact email saved on the ticket. When it cannot be mailed, a hint above the editor names the reason before you send: the ticket has no contact email, the contact email is not a valid address, the ticket has no department, or the department has no SMTP server. If you changed Support Department or Contact Email on the Details tab without saving, a second hint asks you to save first; until then the reply still uses the saved values. After sending, the result is shown and recorded in the History tab:

  • Mailed: Reply sent.; history Reply sent to <address>.
  • Not mailed: a warning; history Reply saved, not mailed: <reason>. On a ticket from the tray icon the reply is still shown on the device (Reply sent to the device.).
  • Sending failed (SMTP error): a warning naming the address; history Reply saved, mail to <address> failed. The cause is in the error log, module Tickets.EmailService.

Files attached with Attach are stored on the ticket and mailed with a public reply under their original names. Files with a blocked extension (see 10.2) are neither stored nor mailed. If the attachments of one reply exceed 20 MB together, the reply is mailed without them, a warning says so and the history reads Reply sent to <address> without attachments (too large); the files remain on the Attachments tab. A single file can be up to 25 MB.

Details

Ticket detail view with the Details tab showing editable fields for status, priority, assignee, department, contact, type, and labels

The Details tab exposes every metadata field on the ticket:

  • Title.
  • Status: Open, In Progress, Waiting, Resolved, or Closed.
  • Priority: Low, Medium, High, or Critical.
  • Assigned To Operator.
  • Support Department.
  • Contact Name: read-only when a contact is linked; edit the contact on the Contacts page to change it.
  • Contact Email: an autocomplete-searchable input when editable. If the entered email has no matching contact, a Create Contact action appears next to it, so the operator can create one without leaving the dialog.
  • Type: a clearable dropdown.
  • Labels: multi-select with the colour of each label previewed inline.
  • Created / Source: captions rather than editors. Source reads Manual for tickets created from the UI and Email for tickets ingested from a department mailbox.

Edit rights split across two flags. Every field on this tab except Assigned To Operator is gated by tickets_edit; the assignee dropdown alone is gated by tickets_assign. A user who can reassign but not edit sees every other field disabled and the assignee dropdown live.

Time Tracking

The per-ticket Time Tracking tab opens with an alert reporting the state of the auto-timer: when the department has automatic time tracking enabled (see 10.10), opening this ticket starts a timer, and the timer pauses after the department's configured idle timeout.

A collapsible Add Entry form books time manually with Date, Start Time, End Time (24-hour clock), and Notes; Duration is computed read-only. Below the form, a table lists every entry on the ticket with User, Date, Start, End, Duration, Rounded (reflecting the department's rounding step), Notes and a Delete action. A footer shows the raw and rounded totals.

History

The History tab is the ticket's own audit log. Every status change, assignee change, field edit, and comment addition appends an entry automatically. Each row captures the author, the date and time, the field that changed, and the old and new values. Ticket changes do not appear in /events; the Audit log records them with less detail (see 10.17).

Attachments

The Attachments tab lists every file attached to the ticket (on a comment, as an inbound email attachment, or by direct upload) in a single table with File Name, Size, Type (MIME), Uploaded By, Date, and Actions.

Every attachment offers Download. A second action, View, appears for text-like types (.txt, .log, .json, .xml, .csv, and anything with a text/* MIME) and renders the file in an inline viewer so operators can read logs, JSON, or XML without leaving the dialog.

AI

The AI tab is present only when the AI module is enabled globally (see Chapter 13). It offers Summarize Ticket, which produces a short summary of the conversation so far, and a free-form question field for chat-style Q&A scoped to this ticket. Output renders in paper-style cards. Both features use the provider and model configured in the AI & LLM settings.

10.5 Ticket lifecycle

A ticket moves through five statuses: Open, In Progress, Waiting, Resolved, and Closed. Any status can change to any other, so an operator can move a ticket from Closed back to Open in a single step.

Three routes lead to Closed:

  • Change Status to Closed on the Details tab and save.
  • Open the Close Ticket confirmation. It asks for an optional Closing Comment, which is stored as an internal note on the ticket.
  • Select rows on the list and use Close Selected in the bulk toolbar. This route does not ask for a closing comment.

Closing a ticket never deletes it. Closed tickets remain visible in the Closed tab and in All, slightly dimmed. To reopen a ticket, set Status back to Open or In Progress and save. The Reopened Tickets metric on the Statistics page tracks how often that happens.

Tickets can also be closed automatically by a scheduled sweep; the per-department Cleanup settings control how long a ticket must be inactive before it is closed (10.10).

10.6 Creating a ticket

The New Ticket button on the list opens the create dialog. Creation is gated by tickets_create.

New Ticket dialog with required Title field and optional Department, Priority, Contact, and Description fields

One field is required: Title. Submitting an empty title raises a Title is required validation error. Every other field is optional:

  • Department: preselected with the department chosen in the list's Department filter, otherwise the first department you are a member of, otherwise None. A ticket without a department has no mailbox, no auto reply and no notification recipients, and its contact cannot be mailed, so pick one when department notifications or mails to the contact are expected. A ticket created through the public API (POST /v1/tickets, departmentId optional) behaves the same.

  • Priority: defaults to Medium.

  • Contact: autocomplete over existing contacts; typing searches name, email, and company.

  • Contact Email: can be entered directly without selecting a contact. A contact can be created later from the detail dialog using Create Contact on the Details tab.

  • Assigned To: the initial assignee.

  • Type.

  • Description: the operator's description of the request. If provided, it is stored as the first comment on the ticket as an Internal note authored by the creator; it is never mailed to the contact.

  • Notify contact by email: off by default. Available when the selected department has an SMTP server and Contact Email holds a valid address; otherwise the checkbox is disabled and a line below it names what is missing. When checked, a Message to the contact field appears and must be filled.

    Only this message is mailed: through the department's SMTP, from its From Address, with the ticket title and number as subject (<Title> [TKT-…]) and your e-mail signature appended. It is stored as an Outbound comment, and the contact's answer to the mail is added to the ticket like any reply that reaches the department's mailbox. If the mail cannot be sent, the ticket is still created; a warning names the address and the history reads Message to contact to <address> not sent, see the error log (otherwise Message to contact sent to <address>).

A ticket created through the public API (POST /v1/tickets) also gets its description as the first comment, styled as Inbound and authored by the contact, or by the token's account when no contact is named.

Creating the ticket auto-fills the following:

  • Ticket #: generated from the customer's prefix plus a sequential number when the matched contact belongs to a customer that sets one, otherwise from the built-in default numbering.
  • Source: Manual (Email is reserved for tickets ingested from a mailbox).
  • Status: Open.
  • Created Date and Created By: set from the current session.
  • SLA: if the contact's email resolves to a customer with an SLA attached, the SLA's deadlines are computed and stored on the ticket.

The ticket_created webhook fires on save (see 10.16).

The form has no device field. Tickets reach devices through the contact: a contact can have linked devices in their tenant, and those devices appear on the Details tab once the ticket is saved. See Chapter 3 for the device side of that linkage.

From the tray icon

End users can open a ticket from the tray icon of their device when the device's policy enables it (Policy Settings → Tray Icon → Support tickets, Chapter 6.5). The tray menu then carries a Support entry that opens a small window: the user describes the problem, optionally picks a category, a type and how urgent it is, gives a name and an e-mail address, adds a screenshot or a file and sends the request. The ticket number is shown right away. A request that cannot be sent (device offline, server unreachable) is kept as a draft on the device and sent again with the same request id, so a retry never files a second ticket.

Such a ticket is filed into the department chosen in the policy with Source = Tray and carries what the console would otherwise need entered by hand:

  • Requested from device and Windows user on the Details tab: the device (linked to its page for accounts that may open it) and the Windows account (DOMAIN\user) that filed the request. The account is determined by the agent on the device, not entered by the user.
  • Customer: the customer of the device's tenant, or the one fixed in the policy. A tenant without a customer gets one created, named after the tenant.
  • Contact: matched by the e-mail address inside that customer, otherwise by the device and the name, otherwise created; the contact is linked to the device.
  • Created By = Tray Icon, the opening message as the first comment (Inbound), the history entries created and requester.
  • Attachments uploaded from the device are stored in the database rather than on the console's file system; the Attachments tab shows them with a database icon and downloads them like any other.

The department's auto reply, notifications, webhooks, SLA and automation rules apply as for any other ticket; the auto reply is sent to the user's e-mail address by the console's reminder service through the department's SMTP settings. In the tickets list a computer icon in front of the title marks a ticket from a device.

What the user sees on the device: only the tickets created from that device under their own Windows account, with the public conversation. Internal notes are not sent to the device. Under My tickets the user reads the public replies, answers them (which reopens a resolved or closed ticket like an e-mail reply) and can mark the ticket as solved (Resolved, with a system comment). Resolved, closed and merged tickets stay visible on the device for 30 days. Which of these options the window offers, whether an e-mail address is required and every text of the window come from the policy.

10.7 Assignment and escalation

A ticket's Assigned To Operator is set manually by default: an operator with tickets_assign picks an assignee from the dropdown. Round-robin or weighted distribution is not available.

The only automated path to an assignee is Auto-assign on open, a per-department switch on the Departments admin page. When enabled, an unassigned ticket of that department is assigned to the first operator who opens it in the web console; opening the detail dialog triggers the assignment.

  • Who is assigned: an operator with both tickets_edit and tickets_assign who can see the ticket (an account with tickets_view_all_departments, or a member whose department view is the ticket's department). Read-only accounts open the ticket without taking it.
  • Which tickets: only open tickets (Open, In Progress, Waiting) without an assignee. Resolved, Closed and Merged tickets and tickets without a department are never assigned this way. Tickets created, read or changed through the Public API, the tray icon or the mailbox poll are not assigned either; only opening in the web console counts.
  • Several operators at once: when two operators open the same ticket at the same moment, exactly one becomes the assignee.
  • What it records: the operator sees a short notice, the history shows the change of the assignee, the audit log records it, and the department's webhooks and notification mails report it like a manual assignment (ticket_updated and ticket_assigned).
  • Auto-assigned flag: the ticket is marked as auto-assigned (Public API field and filter autoAssigned). Any later change of the assignee, in the console or through the Public API, clears the mark. A ticket that is set back to unassigned is assigned again the next time an operator opens it.

SLA escalation sends notifications and webhooks and does not change the ticket. Tickets under an SLA carry a deadline and the list shows the current urgency as a coloured chip. When the deadline crosses a warning threshold the department's Notifications fire sla_warning, and on breach they fire sla_breached. Those events drive email notifications and webhooks (10.16). Tickets whose SLA is at risk are not reassigned automatically.

10.8 Time tracking

Requires permission: tickets_view_time_tracking.

Route: /tickets/time-tracking. The page is a single-day calendar showing every time entry across every ticket the operator can see.

Time Tracking calendar with a 24-hour vertical timeline and coloured blocks for manual and automatic entries

A vertical 24-hour timeline runs from midnight to midnight with half-hour gridlines. Entries are rendered as coloured rectangles positioned by their start and end times. The colour encodes origin: manual entries are blue, automatic entries (booked by the auto-timer) are green. On today's view, a red indicator tracks the current time.

A sidebar lists the same day's entries in chronological order with a delete button on each row. Navigation across days uses Previous, Next, a date picker, and a Today shortcut.

Each entry records Date, Start Time, End Time, Duration (computed), Rounded Duration, and Notes, plus an internal flag noting whether it was booked manually or automatically. The rounded duration applies the department's Rounding (minutes, 0 = exact) step; with 0 the rounded value equals the raw duration.

Automatic tracking is driven by three department settings:

  • Idle Timeout (minutes): after this many minutes without activity on the ticket, the timer pauses. The next interaction resumes it as a new entry.
  • Confirm Timeout (minutes): after this many minutes, the operator is prompted to confirm they're still working on the ticket. Without a confirmation the current entry stops.
  • Rounding (minutes, 0 = exact): the increment the Rounded Duration snaps to.

The page has no export; aggregate figures are on the Statistics page.

10.9 Statistics

Requires permission: tickets_view_statistics.

Route: /tickets/statistics. The page is a tabbed dashboard covering activity over a chosen time window.

Ticket Statistics with the Overview tab showing totals, per-status counts, SLA compliance, and the priority distribution chart

A filter row at the top controls scope for every tab: a date-range picker (defaulting to the last 30 days), plus Department, Customer, and Operator dropdowns, and an Apply button that re-runs the query.

Five tabs group the metrics by category:

  • Overview: volume and quality indicators across the whole scope: totals, per-status counts, average resolution and first-response times, SLA compliance, priority and source breakdowns, busiest day and hour, reopens, and so on.
  • Departments: one row per department with the key volume and SLA figures.
  • Customers: one row per customer with volumes, hours, and SLA compliance.
  • Operators: one row per operator with workload and outcome figures, plus an operator-by-customer hours matrix.
  • Trends: distributions across labels and types.

Each metric is labelled on the page.

10.10 Departments

Requires permission: tickets_manage_departments.

Route: /tickets/departments. Departments are the organisational and technical unit of the ticket system. They carry their own mailbox, their own notification recipients, their own time-tracking behaviour, their own webhooks, and their own membership list.

Ticket Departments admin list with columns for Name, Description, IMAP Server, SMTP Server, Members, and Enabled

The list columns are Name, Description, IMAP Server, SMTP Server, Members, Last poll, Enabled, and row-level actions. Last poll shows the result (Success, Partial or Error) and the time of the latest mailbox poll; for a failed poll, hovering over it shows the cause, for example a refused certificate or a failed sign-in.

The create and edit dialogs share the same field set, grouped into sections:

  • General: Name, Description, IMAP Server, IMAP Port, IMAP Username, IMAP Password, SMTP Server, SMTP Port, SMTP Username, SMTP Password, From Address, From Name, Enabled, and Auto-assign on open.

  • TLS certificate validation (in the General block, below the SMTP fields): the setting applies to both the IMAP and the SMTP connection of the department, for polling, replies, automatic replies, follow-up reminders and the mailbox search alike:

    • Full validation (recommended): the server certificate must be issued by a trusted authority, be valid and carry the server name entered in the dialog.
    • Encrypt, but ignore a host name mismatch: as full validation, but the certificate does not have to carry the server name. Use it when the server is reached under an internal name.
    • Encrypt, accept any certificate: the connection is encrypted, the certificate is not checked.

    In the first two modes the web console also checks whether the certification authority has revoked the certificate. For that it downloads the authority's revocation list over HTTP (port 80) from the address named in the certificate. If that address cannot be reached, the connection is still made and a warning is written to the web console log, at most once per server and hour. A certificate the authority has revoked is always refused.

    Test connection signs in to the IMAP and the SMTP server with the values currently in the dialog, saved or not, and opens the inbox read-only; no mail is read or sent. Both servers are tested, also when the first one fails. The result for each server stays below the button until the next test and names the cause of a failure, for example an untrusted, expired or revoked certificate, a failed sign-in or a server that cannot be reached. A success with a warning means the revocation list could not be downloaded (see X.3.6).

  • Auto-Reply Email: Subject, Body (HTML), and an enabled toggle. Two placeholders resolve at send time: {{ticket_number}} and {{subject}}. Fires once per new ticket created from an inbound mail or from the tray icon of a device (tickets created in the console use Notify contact by email in the New Ticket dialog instead); sent through the department's SMTP settings and marked as an automatic reply (Auto-Submitted) so out-of-office and other automatic responders do not answer it.

  • Follow-Up Reminder Email: Send after X days without reply, Subject, Body (HTML), and an enabled toggle. Fires once per ticket when the customer has not replied for the configured number of days.

  • Time Tracking: Idle Timeout (minutes), Confirm Timeout (minutes), Rounding (minutes, 0 = exact), and an enabled toggle. Drives the auto-timer described in 10.8.

  • Cleanup: Close tickets inactive for (days), Auto-close tickets with these statuses (checkboxes for Open, In Progress, and Waiting), Internal note added to auto-closed tickets, Delete closed tickets older than (days), and Also delete attachment files from disk.

  • Notifications: Notification Recipients (comma-separated email addresses) plus an event-checkbox list: Ticket Created, Ticket Updated, Ticket Closed, Ticket Assigned, Comment Added, SLA Warning, SLA Breached, and Auto-Closed. Each selected event sends a plain-text email to every listed recipient.

    These mails are sent through the global e-mail settings under Settings > Notifications > E-Mail, not through the department's mailbox. Without global e-mail settings nothing is sent, and a ticket without a department sends nothing. The sender name is Tickets | NetLock with the global From address. Events raised through the public API are notified as well.

    Each notification mail carries the headers Auto-Submitted: auto-generated and X-NetLock-Ticket-Notification: <event>. A department mailbox that receives such a mail leaves it unread and does not turn it into a ticket or a comment. A recipient may therefore be the department's own mailbox, though a separate address is the cleaner setup.

  • Webhooks: a Manage Webhooks button opens the webhook dialog scoped to this department. See 10.16.

  • Members: a multi-select of the operators in this department. Membership combines with tickets_view_all_departments to determine who sees which tickets.

Email ingestion is per department. Each department polls its own IMAP mailbox; inbound messages create tickets in that department, and outbound replies are sent through that department's SMTP. To accept mail for several addresses, set up several departments. Deletions are hard deletes.

How an inbound mail is matched to an existing ticket

Every mail NetLock RMM sends carries the ticket number in square brackets in the subject, for example Re: Printer offline [ACME-000123]. With that number, an incoming mail becomes a comment on the existing ticket instead of a new ticket. These rules apply:

  • The number has to be in square brackets. The part before the last hyphen is the prefix, the part after it has to be at least six digits, the length of every generated number. Numbers of the built-in default numbering (TKT-…) are recognised with or without brackets.
  • A prefix that belongs to a customer is tried before one that does not, and within each group the number closest to the end of the subject comes first. A prefix a customer has since renamed therefore still resolves, as long as the ticket itself is still there.
  • The ticket has to be reachable from the mailbox that received the mail: it belongs to the polling department, or the sender is the ticket's contact address, or the sender is a contact of the ticket's customer.
  • If the ticket was merged into another one, the mail is added to the ticket the conversation was merged into.

In all other cases, for example with a rewritten subject, a deleted number or a number that matches no ticket, the mail creates a new ticket. Replies stay on their ticket as long as the subject is left intact, as common mail clients do when replying. With logging enabled, each mail that does not match writes one line to debug.log naming the reason. NetLock RMM's own notification mails, recognised by their X-NetLock-Ticket-Notification header, are the only messages the poll leaves untouched; every other unread mail is imported.

10.11 Customers

Requires permission: tickets_manage_customers.

Route: /tickets/customers. Customers are the company records of the ticket system. The detail page at /tickets/customers/details edits one customer in depth.

List columns: Company, Tenant, SLA, Prefix, and a contacts count. Creating a customer uses the Add Company dialog with these fields:

  • Company Name.
  • Address.
  • Linked Tenant: the RMM tenant this customer maps to. The linkage scopes which devices can later be attached to the customer's contacts.
  • SLA: picks an entry from the SLA library; see 10.15.
  • Ticket Number Prefix: gives this customer's tickets their own numbering, PREFIX-000123. If it is empty, the customer's tickets use the default TKT- numbering. Use something short and recognisable, such as ACME.
  • Notes.

The customer detail page lets an admin edit the same fields and also shows the company's departments, contacts, and tickets in one place, with device links attached to each contact visible inline.

Warning: Deleting a customer is a hard delete with cascade. All departments tied to that customer, all its contacts, and the device links on those contacts are removed permanently. Remove customers only when you are sure they are gone for good.

10.12 Contacts

Requires permission: tickets_manage_customers.

Route: /tickets/contacts. Contacts are the individual people tickets are tied to. Every ticket references a contact; the contact in turn belongs to a customer, which is how the customer's SLA and prefix reach the ticket.

List columns: Last Name, First Name, Email, Phone, Position, Company, Department, and a linked-devices count. Create and edit fields are First Name, Last Name, Email, Phone, Position / Role, Company, Department, Notes, and Linked Devices. Device linking is a multi-select that is available only after a company is chosen. The device list is limited to the devices of the company's linked tenant.

Contacts are also maintained inside the customer detail page. The flat /tickets/contacts page is an alternative view of the same records, convenient when you are looking for one person without knowing which customer they belong to. Deletions are hard deletes.

10.13 Templates

Requires permission: tickets_manage_templates.

Route: /tickets/templates. Templates are saved responses reusable across tickets. List columns: Name, Type (Email or Ticket), Subject, Author, Date, and an actions column.

Create and edit fields are Name, Type, Subject, and Body. The body editor offers the same three modes as the ticket composer (Rich Text, HTML and Plain Text). Both a rich-text rendering and a plain-text fallback are stored, so the message displays correctly in any mail client.

The Type field reflects where the template is meant to be used: Email templates for outbound replies, Ticket templates for internal notes and descriptions on newly created tickets. Both types appear in the Template Picker; the type only helps to organise templates.

The Template Picker is available from the ticket composer and from the new-ticket dialog. Picking a template populates the subject and body of the composer and leaves both fully editable. Deletions are hard deletes.

10.14 Labels and Types

Requires permission: tickets_manage_labels_types.

Labels and Types are managed in two places: a Labels & Types dialog reachable from the ticket detail dialog and from the Settings area, and a Labels & Types tab on Settings → Ticket System. Both edit the same data.

Labels are colour-coded tags. Each label has a Label Name and a Color chosen from a hex picker. A ticket can have several labels; the label picker on the Details tab is multi-select. Labels do not affect routing or SLA behaviour. They help you filter and categorise the list.

Types are single-value categorisations. Each type has a Type Name and a Description. A ticket has at most one type.

Note: Types are user-defined. NetLock RMM does not ship a pre-configured list, and in particular does not provide the ITIL set (Incident, Service Request, Change, Problem) out of the box. Define whatever set fits your workflow.

Deleting a label or type is permanent and has no confirmation prompt.

10.15 SLA

Requires permission: tickets_manage_sla.

SLAs are managed from an SLA Management dialog and from the SLA tab on Settings → Ticket System. Both edit the same records.

List columns: Name, Response (h), Resolution (h), Priority Override, Description, and an actions column.

Each SLA carries:

  • Name.
  • Response Time (hours): the deadline for the first outbound response to the customer.
  • Resolution Time (hours): the deadline to reach a resolved status.
  • Priority Override: one of None, Low, Medium, High, or Critical. Acts as a minimum priority: tickets under this SLA cannot drop below the override.
  • Description: free text.

SLAs attach to customers on the Customers page (see 10.11). When a ticket is created from a contact of that customer, the SLA's response and resolution deadlines are computed from the creation time and stored on the ticket. The SLA chip in the list changes through ok, warning, critical, and breached colours as the deadline approaches.

Note: SLA timers are wall-clock hours. Business hours are not taken into account: a 4-hour response time means four real hours, including nights and weekends. Set the thresholds accordingly.

SLA timer changes trigger notifications and webhooks through the sla_warning and sla_breached events. Deletions are hard deletes.

10.16 Webhooks

Requires permission: tickets_manage_departments to reach the department form, and tickets_manage_webhooks for the webhook dialog and everything in it.

Webhooks are configured per department, not globally. From the department edit form, Manage Webhooks opens the webhook dialog, which lists the department's webhooks and offers create, edit, test, and delete actions.

Ticket Webhook dialog with Monaco editors for the JSON request body and headers

Each webhook has the following fields:

  • Name: shown in the list.
  • Description: free text.
  • URL: required; the endpoint the request is sent to.
  • Method: one of GET, POST, PUT, DELETE, or PATCH.
  • Request Body: a JSON document edited in an embedded Monaco editor, with placeholder substitution at send time.
  • Request Headers: a JSON object edited in Monaco. Defaults to {"Content-Type": "application/json"}.
  • Events: zero or more trigger events. Selecting none means the webhook fires for every event.
  • Enabled: toggle.
  • Sign requests: off by default. When on, every request carries the header X-NetLock-Signature, computed over exactly the body it sends after the placeholders were replaced. Switching it on generates a secret and shows it once; Rotate secret on a saved webhook replaces it at once. The header name is reserved and cannot be set under Request Headers. Slack, Microsoft Teams, Discord and ntfy ignore signatures. X.10 shows how a receiver verifies them.

The eight event triggers are ticket_created, ticket_updated, ticket_closed, ticket_assigned, comment_added, sla_warning, sla_breached, and auto_closed.

Ten placeholder tokens are substituted in the request body: {{ticket_number}}, {{subject}}, {{status}}, {{priority}}, {{assigned_to}}, {{customer}}, {{department}}, {{event}}, {{timestamp}}, and {{url}}.

{{url}} is the link to the ticket in the web console. It is built from the Public console URL under Settings → Overview. While that setting is empty, {{url}} is replaced by nothing and the webhook is sent without a link; the dialog shows a notice in that case.

The dialog pre-populates new webhooks with the following default body. Adjust it to the shape your integration expects.

{
  "event": "{{event}}",
  "ticket_number": "{{ticket_number}}",
  "subject": "{{subject}}",
  "status": "{{status}}",
  "priority": "{{priority}}",
  "assigned_to": "{{assigned_to}}",
  "customer": "{{customer}}",
  "department": "{{department}}",
  "timestamp": "{{timestamp}}",
  "url": "{{url}}"
}

A Test action sends a single request filled with sample placeholder values; {{url}} behaves as in a real delivery, so it stays empty without a public console URL. Before sending, the dialog validates that the URL is well-formed and that the body and headers parse as JSON, so a misconfigured webhook fails at save time rather than at the next real event.

10.17 Notifications and Events integration

Tickets use these notification channels:

  • Email: per department. The Notification Recipients list and the Notify on these events checkboxes decide who is emailed and for which events. Notifications go to staff recipients through the global e-mail settings (Settings > Notifications > E-Mail) and require a department on the ticket.

    The auto reply and the follow-up reminder go to the contact through the department's own SMTP settings, and only for tickets raised by mail or from the tray icon of a device, not for tickets created in the console or through the API. A ticket created in the console reaches its contact only through Notify contact by email in the New Ticket dialog and through public replies; the API never mails the contact. Replies to customers also use the department's SMTP and require a department with an SMTP server and a contact email on the ticket.

  • In-app toasts: a live notification service pushes toasts to the Console on new tickets, replies, and updates. Tickets and replies that arrive from the tray icon of a device are announced the same way as an inbound mail.

  • Device notice: for a ticket opened from the tray icon, a public reply or a change to Resolved or Closed is announced on the device within seconds while it is online (a small notice for the Windows user who filed it, if the policy allows it); otherwise the tray icon picks it up at its next check. Internal notes are never sent to the device.

  • Unread counter: the Tickets entry in the navigation carries a badge showing unread ticket activity for the current user.

Webhook delivery is a separate channel, covered in 10.16.

Notification mails carry an Open ticket line with the link to the ticket while a Public console URL is set; without one the line is left out and the rest of the mail stays the same.

A link opened without a session leads to the sign-in page and, once the sign-in is complete including a second factor or a forced password change, to the ticket. An account without access to the ticket system ends on its usual start page. The ticket itself opens only for an account that may see it: its department has to be visible to the account, and a ticket of a tenant has to belong to one of the account's tenants; otherwise the page says the ticket does not exist or is not visible.

Where the e-mail channel logs: Logging → Web Console Logs, files error.log and debug.log, module Tickets.NotificationMailDispatcher; every skipped or failed send writes one line naming the reason. Events raised through the public API log on the server instead, module Public_Api.Ticket_Notification_Mail_Dispatcher. See A.9 — Logging & protocols for the log files.

Note: Ticket changes do not appear in /events. The ticket's History tab records every change field by field; the Audit log records ticket actions under entity type ticket.

For wider context on how each notification channel is configured (SMTP, Teams, Telegram, Ntfy, webhooks), see Appendix A.8.

10.18 Permissions

The ticket module has its own set of permission flags. The global Settings → Ticket System page is gated by a Settings flag.

FlagWhat it gates
tickets_enabledAccess to the Tickets menu and the /tickets page. Required for any other ticket permission to take effect.
tickets_createThe New Ticket button on the list and the create dialog.
tickets_editEditing the fields on the ticket detail dialog's Details tab (except the assignee).
tickets_deleteDeleting tickets from the list and from the detail dialog.
tickets_assignChanging Assigned To Operator in the detail dialog.
tickets_view_time_trackingThe Time Tracking page at /tickets/time-tracking.
tickets_view_statisticsThe Statistics page at /tickets/statistics.
tickets_view_all_departmentsVisibility of tickets outside the user's own department. Without it, the list filters down to the user's department only.
tickets_manage_departmentsThe /tickets/departments admin page.
tickets_manage_templatesThe /tickets/templates admin page.
tickets_manage_labels_typesThe Labels & Types dialog and tab.
tickets_manage_customersThe Customers and Contacts admin pages.
tickets_manage_slaThe SLA Management dialog and tab.
tickets_manage_webhooksThe webhook dialog inside a department. The UI reaches it from the department edit form, so tickets_manage_departments is a practical prerequisite.
settings_system_enabledThe Settings → Ticket System page, including the master toggle and the blocked-extensions list.

See Appendix X.2 for the full permission catalogue across the product.