NetLock RMMNetLock RMM Docs
III — How-To Guides

Handle a ticket from open to resolved

Create a ticket, triage and assign it, reply to the customer, log time, and close it out.

Handle a ticket from open to resolved

Optional module: This guide assumes the Ticket System is enabled. See Chapter 10 to enable it.

This guide walks through the full loop for a single ticket: create it, triage and assign it, post an internal note, reply to the customer, log time, and close it out. The same steps apply to tickets that arrived via inbound email; only the starting point differs.

Ticket detail view with the Conversation tab open and a composer at the bottom

Before you start

  • The Ticket System is enabled in Settings → Ticket System.
  • At least one support department exists, with outbound SMTP configured if you want to reply to the customer by email. A ticket without a department, or with a department without SMTP, cannot mail the contact.
  • Required permissions: tickets_enabled, tickets_create, tickets_edit, tickets_assign. Time-tracking entries additionally require tickets_view_time_tracking on the entry-creator.

Steps

1. Open the Tickets page

Navigate to Tickets (route /tickets). Use the status tabs at the top (All, Open, In Progress, Waiting, Resolved, Closed) to narrow the view.

2. Create the ticket

  1. Click New Ticket. The New Ticket dialog opens.
  2. Fill in Title (required), Department (preselected with your own department), Priority (defaults to Medium), Contact Email (the autocomplete searches existing contacts; new addresses are accepted), and an optional Description. If entered, the description is stored as an internal note in the Conversation tab; it is not sent to the contact.
  3. To inform the contact right away, check Notify contact by email and write the Message to the contact. Only this message is mailed, with the ticket title and number as subject; the contact's answer is added to the ticket. The checkbox is disabled, with the reason below it, when the department has no SMTP server or the contact email is missing or invalid.
  4. Save. The ticket appears in the list with a generated ticket number and Status = Open.

3. Open the ticket detail view

In the list, click the new row. The detail dialog opens with six tabs: Conversation, Details, Time Tracking, History, Attachments, and, when AI is configured, AI.

4. Triage on the Details tab

  1. Switch to the Details tab.
  2. Set Assigned To Operator to yourself or the owning operator. This field is gated by tickets_assign.
  3. Optionally set a Type (for example Incident, Request) and add colour-coded Labels for reporting. Edits save in place and are logged in the History tab.

5. Post an internal triage note

  1. Switch back to the Conversation tab.
  2. On the composer at the bottom, toggle the direction to internal (the lock icon). Internal notes are never sent to the customer and render in orange.
  3. Write the note and send.

6. Reply to the customer

  1. Toggle the composer direction to outbound (the globe icon). Outbound messages are emailed to the contact using the department's SMTP settings. If a hint above the editor says that no email will be sent, fix the named cause (department, SMTP, contact email) on the Details tab and save before replying.
  2. Optionally click the template-picker button to insert a saved response template.
  3. Optionally attach files with Attach; they are mailed with the reply (up to 20 MB in total, otherwise the reply goes out without them and a warning says so).
  4. Pick Rich Text, HTML, or Plain Text mode and send. The toast and the History tab say whether the reply was mailed.

7. Log your time

  1. Switch to the Time Tracking tab.
  2. If the department has automatic time tracking enabled, the banner at the top shows the running timer. No action is needed unless it has paused on idle.
  3. Otherwise, expand Add Entry and fill in Date, Start Time, End Time, and optional Notes. Duration is computed. Save.

8. Close the ticket

  1. Return to the Details tab.
  2. Change Status to Resolved if you are waiting on customer confirmation, or Closed if no further reply is expected.
  3. Setting Status to Closed opens the Close Ticket dialog; enter an optional Closing Comment, which is stored as an internal note.

Verify it worked

  • The History tab lists entries for the status change and the assignee change, each with old and new values.
  • The ticket now appears under the Closed tab (or Resolved). Closed rows render at reduced opacity.
  • The customer received the outbound reply at the Contact Email address. The internal note is not visible to them.
  • The Time Tracking tab shows at least one entry and the summary footer reflects its duration.

Troubleshooting

  • The customer never received the reply. Outbound replies use the department's SMTP settings, not the global notification SMTP. Check the History tab: Reply saved, not mailed: no department (or no contact email, invalid contact email, department has no SMTP server) means the reply was never sent. Set the department and contact email on the Details tab, save, and reply again. Reply saved, mail to <address> failed means the SMTP server refused the mail; verify the department's outbound SMTP configuration and check the error log (module Tickets.EmailService); see Chapter 10.
  • The reply arrived without its attachments. The attachments of one reply exceeded 20 MB together. They are on the Attachments tab; send them in smaller replies or share them another way.
  • The ticket is stuck in Waiting. Every status can be changed to any other status. Open the Details tab and change Status directly.