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.

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 requiretickets_view_time_trackingon 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
- Click
New Ticket. The New Ticket dialog opens. - Fill in
Title(required),Department(preselected with your own department),Priority(defaults toMedium),Contact Email(the autocomplete searches existing contacts; new addresses are accepted), and an optionalDescription. If entered, the description is stored as an internal note in the Conversation tab; it is not sent to the contact. - To inform the contact right away, check
Notify contact by emailand write theMessage 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. - 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
- Switch to the
Detailstab. - Set
Assigned To Operatorto yourself or the owning operator. This field is gated bytickets_assign. - Optionally set a
Type(for exampleIncident,Request) and add colour-codedLabelsfor reporting. Edits save in place and are logged in theHistorytab.
5. Post an internal triage note
- Switch back to the
Conversationtab. - 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.
- Write the note and send.
6. Reply to the customer
- 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
Detailstab and save before replying. - Optionally click the template-picker button to insert a saved response template.
- 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). - Pick
Rich Text,HTML, orPlain Textmode and send. The toast and theHistorytab say whether the reply was mailed.
7. Log your time
- Switch to the
Time Trackingtab. - 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.
- Otherwise, expand
Add Entryand fill inDate,Start Time,End Time, and optionalNotes.Durationis computed. Save.
8. Close the ticket
- Return to the
Detailstab. - Change
StatustoResolvedif you are waiting on customer confirmation, orClosedif no further reply is expected. - Setting
StatustoClosedopens the Close Ticket dialog; enter an optionalClosing Comment, which is stored as an internal note.
Verify it worked
- The
Historytab lists entries for the status change and the assignee change, each with old and new values. - The ticket now appears under the
Closedtab (orResolved). Closed rows render at reduced opacity. - The customer received the outbound reply at the
Contact Emailaddress. The internal note is not visible to them. - The
Time Trackingtab 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
Historytab:Reply saved, not mailed: no department(orno contact email,invalid contact email,department has no SMTP server) means the reply was never sent. Set the department and contact email on theDetailstab, save, and reply again.Reply saved, mail to <address> failedmeans the SMTP server refused the mail; verify the department's outbound SMTP configuration and check the error log (moduleTickets.EmailService); see Chapter 10. - The reply arrived without its attachments. The attachments of one reply exceeded 20 MB together. They are on the
Attachmentstab; 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 theDetailstab and changeStatusdirectly.
Related
- Chapter 10 — Tickets — full reference for the ticket list, detail dialog, statistics, and departments.
- Chapter 14 — Users & Roles — managing the
tickets_*permission flags on operators. - How-to H.10 — Configure email and Microsoft Teams notifications — setting up outbound notification channels that complement ticket email.
Reach a file share (SMB) over NetMesh
Open a Windows or Samba file share on another device through a NetMesh link or service network, why port 445 does not work on Windows client devices, and what the port conflict hints in the console mean.
Upgrade NetLock RMM
Upgrade the Web Console, Server, and agents to the latest version, with optional automatic image checks.