<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Nilear Changelog</title>
<subtitle>New features, updates and fixes in Nilear.</subtitle>
<link href="https://changelog.nilear.com/feed.xml" rel="self"/>
<link href="https://changelog.nilear.com/"/>
<id>https://changelog.nilear.com/</id>
<updated>2026-10-20T00:00:00Z</updated>
<author><name>Nilear</name><uri>https://nilear.com</uri></author>
<entry>
<title>Close Open Tasks Without Leaving Wrap-up</title>
<link href="https://changelog.nilear.com/2026/close-open-tasks-when-completing/"/>
<id>https://changelog.nilear.com/2026/close-open-tasks-when-completing/</id>
<published>2026-10-20T00:00:00Z</published>
<updated>2026-10-20T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>When open tasks hold up Completed or a resolved status, the Open Tasks warning now lists them so you can mark each one and carry on.</summary>
<content type="html">&lt;p&gt;Where your administrator requires tasks to be closed before a ticket is resolved, the &lt;strong&gt;Open Tasks&lt;/strong&gt; warning no longer just counts them.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/CloseOpenTasksOnComplete.png&quot; alt=&quot;The Open Tasks warning with both tasks marked and the Continue to &amp;quot;Completed&amp;quot; button&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The tasks are listed.&lt;/strong&gt; Each task still open under Working Notes is shown with its &lt;strong&gt;Done&lt;/strong&gt;, &lt;strong&gt;N/A&lt;/strong&gt; and &lt;strong&gt;Failed&lt;/strong&gt; marks. A mark made here is the same as one made under Working Notes, and your colleagues see it straight away.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Undo a mis-click.&lt;/strong&gt; A marked task stays in the list, so clicking its mark again opens it again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Carry on.&lt;/strong&gt; Once no task is open, &lt;strong&gt;Continue to &amp;quot;Completed&amp;quot;&lt;/strong&gt; finishes the wrap-up you started. If you had chosen another resolved status, such as &lt;strong&gt;Closed&lt;/strong&gt;, &lt;strong&gt;Use &amp;quot;Closed&amp;quot;&lt;/strong&gt; selects it for you.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
<entry>
<title>Let a Client Approve ConnectActive in Microsoft 365</title>
<link href="https://changelog.nilear.com/2026/let-a-client-approve-connectactive-in-microsoft-365/"/>
<id>https://changelog.nilear.com/2026/let-a-client-approve-connectactive-in-microsoft-365/</id>
<published>2026-10-20T00:00:00Z</published>
<updated>2026-10-20T00:00:00Z</updated>
<category term="ConnectActive"/>
<summary>Get a consent link and instructions to pass to a client&apos;s Global Administrator, so they can approve ConnectActive&apos;s Microsoft 365 access themselves.</summary>
<content type="html">&lt;p&gt;Microsoft lets only a &lt;strong&gt;Global Administrator&lt;/strong&gt; or a &lt;strong&gt;Privileged Role Administrator&lt;/strong&gt; approve the Microsoft Graph permissions ConnectActive needs. Other admin roles, such as Cloud Application Administrator, are refused. When nobody on your team has one of those roles in the client&amp;#39;s tenant, the client can now approve ConnectActive themselves.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/ConnectActiveClientConsent.png&quot; alt=&quot;The approval link for a client&apos;s administrator, with the Application ID and instructions&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Get Client Approval Link.&lt;/strong&gt; In a company&amp;#39;s Microsoft 365 / Entra ID source, enter the client&amp;#39;s domain and choose &lt;strong&gt;Get Client Approval Link&lt;/strong&gt;. ConnectActive shows the ConnectActive &lt;strong&gt;Application (client) ID&lt;/strong&gt;, a consent link for that tenant, and instructions that include the link, ready to paste into your own email or ticket. Copy the link on its own or the whole instructions. Nothing is sent from Nilear.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The client approves.&lt;/strong&gt; Their Global Administrator or Privileged Role Administrator opens the link, reviews the permissions and accepts. A Nilear page confirms the result; they do not need a Nilear sign-in.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You finish.&lt;/strong&gt; When the client tells you they have approved, choose &lt;strong&gt;Verify&lt;/strong&gt;, then sync as usual.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The &lt;strong&gt;Grant Authorization&lt;/strong&gt; step now names the roles that can approve and lists the permissions requested: &lt;strong&gt;Directory.Read.All&lt;/strong&gt;, &lt;strong&gt;Group.Read.All&lt;/strong&gt;, &lt;strong&gt;Member.Read.Hidden&lt;/strong&gt; and &lt;strong&gt;AuditLog.Read.All&lt;/strong&gt;, all read-only. ConnectActive syncs with its own application credentials and never uses the account that approved. A declined or failed approval now shows Microsoft&amp;#39;s reason instead of an error page.&lt;/p&gt;
&lt;p&gt;The option can be found under ConnectActive -&amp;gt; Companies -&amp;gt; select a company -&amp;gt; the Microsoft 365 / Entra ID source.&lt;/p&gt;</content>
</entry>
<entry>
<title>See Ticket Work Before ConnectWise Catches Up</title>
<link href="https://changelog.nilear.com/2026/see-ticket-work-before-connectwise-catches-up/"/>
<id>https://changelog.nilear.com/2026/see-ticket-work-before-connectwise-catches-up/</id>
<published>2026-10-20T00:00:00Z</published>
<updated>2026-10-20T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>MTX shows a ticket&apos;s new status and who is working it as soon as you act, and asks before you start a ticket a colleague is already working.</summary>
<content type="html">&lt;p&gt;When ConnectWise is slow to take updates, MTX no longer waits for it to show what you and your colleagues are doing.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/PendingTicketStatus.png&quot; alt=&quot;A ticket shown In Progress with the hourglass mark while ConnectWise has not confirmed it&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The new status shows at once.&lt;/strong&gt; After &lt;strong&gt;Work on Ticket&lt;/strong&gt;, wrap-up, PSR, travel or an abort, the ticket shows the status MTX is setting, in every member&amp;#39;s Tickets and Queue tabs and in the ticket&amp;#39;s summary, with an hourglass until ConnectWise confirms it. Filters and counts follow it. A status chosen from the Tickets tab afterwards takes its place.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The Availability Board keeps up.&lt;/strong&gt; You are shown &lt;strong&gt;In Progress&lt;/strong&gt; on a ticket, or no longer on it, as soon as you start, pause, resume, travel or finish, instead of when ConnectWise has caught up. Choosing an In Progress status from the Tickets tab updates the board the same way.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A check before doubling up.&lt;/strong&gt; &lt;strong&gt;Work on Ticket&lt;/strong&gt; on a ticket another member is already working asks you to confirm first and names them. It does not ask when you are scheduled on the ticket around now, such as a meeting or an on-site booked for several technicians; you see the usual notice that a colleague is working it.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
<entry>
<title>Choose Whether Auto PSR Tickets Resume on Their Own</title>
<link href="https://changelog.nilear.com/2026/choose-whether-auto-psr-tickets-resume-on-their-own/"/>
<id>https://changelog.nilear.com/2026/choose-whether-auto-psr-tickets-resume-on-their-own/</id>
<published>2026-10-19T00:00:00Z</published>
<updated>2026-10-19T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Under the One Ticket Method you can now keep Auto PSR tickets in *PSR when you finish a ticket, and resume them yourself from their tab.</summary>
<content type="html">&lt;p&gt;Under the One Ticket Method, starting work on a new ticket puts the ticket you were working on into Auto PSR, shown as &lt;strong&gt;*PSR&lt;/strong&gt;. When you wrap up, abort or PSR the new ticket, MTX resumes the ticket it put into Auto PSR most recently and starts its timer again.&lt;/p&gt;
&lt;p&gt;If you would rather decide what to work on next yourself, open &lt;strong&gt;MTX Preferences&lt;/strong&gt;, go to &lt;strong&gt;Working Ticket Method&lt;/strong&gt;, and turn off &lt;strong&gt;Resume Auto PSR tickets automatically&lt;/strong&gt; in the &lt;strong&gt;Auto *PSR&lt;/strong&gt; section. Your Auto PSR tickets then stay in *PSR when you finish a ticket. Click a ticket&amp;#39;s tab to resume it.&lt;/p&gt;
&lt;p&gt;The setting is yours alone and doesn&amp;#39;t change how MTX works for anyone else on your team. It is on by default, so nothing changes until you turn it off.&lt;/p&gt;</content>
</entry>
<entry>
<title>Rename and Delete Project Phases</title>
<link href="https://changelog.nilear.com/2026/rename-and-delete-phases/"/>
<id>https://changelog.nilear.com/2026/rename-and-delete-phases/</id>
<published>2026-10-19T00:00:00Z</published>
<updated>2026-10-19T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>Rename a phase or delete an empty one from a project&apos;s Work Plan.</summary>
<content type="html">&lt;p&gt;You can now rename a phase from a project&amp;#39;s &lt;strong&gt;Work Plan&lt;/strong&gt;, and delete a phase that is empty. Phases that contain sub-phases or tickets can&amp;#39;t be deleted, so nothing is removed along with them. Move the tickets or delete the sub-phases first. Renaming and deleting follow your ConnectWise permissions for the project, and ConnectWise will tell you if you don&amp;#39;t have access.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/WorkPlanRenameDeletePhase.png&quot; alt=&quot;Rename and Delete Project Phases&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Filter the Availability Board by Status, and Find a Member</title>
<link href="https://changelog.nilear.com/2026/filter-the-availability-board-by-status/"/>
<id>https://changelog.nilear.com/2026/filter-the-availability-board-by-status/</id>
<published>2026-10-18T00:00:00Z</published>
<updated>2026-10-18T00:00:00Z</updated>
<category term="MTX: Availability"/>
<summary>The Availability Board now counts members by status, filters to the statuses you pick, and has a Find a member search.</summary>
<content type="html">&lt;p&gt;A row of status chips now sits above the Availability Board. Each chip shows how many members are in that status: &lt;strong&gt;Working&lt;/strong&gt;, &lt;strong&gt;Waiting&lt;/strong&gt;, &lt;strong&gt;Inactive&lt;/strong&gt;, &lt;strong&gt;Missing&lt;/strong&gt;, &lt;strong&gt;On-site / Travel&lt;/strong&gt;, &lt;strong&gt;Away&lt;/strong&gt;, &lt;strong&gt;Off&lt;/strong&gt; and &lt;strong&gt;Other&lt;/strong&gt;. Hover over a chip to see what its colour means.&lt;/p&gt;
&lt;p&gt;Click a chip to show only the members in that status. Click more chips to add their statuses, click a selected chip again to remove it, or press &lt;strong&gt;Show all&lt;/strong&gt; to see everyone again. Selecting chips doesn&amp;#39;t change the counts, so you can still see how many members are in each status.&lt;/p&gt;
&lt;p&gt;A status nobody is in is left out of the row. To filter by it anyway, for example to watch who goes &lt;strong&gt;Off&lt;/strong&gt;, press &lt;strong&gt;⋯&lt;/strong&gt; after the chips to show every status, then click the one you want. Members appear as soon as they reach that status.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/AvailabilityStatusFilter.png&quot; alt=&quot;Status chips with Working, Missing and Away selected, beside the Find a member search&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;To find someone quickly, type part of their name in &lt;strong&gt;Find a member&lt;/strong&gt;. Press Esc or the &lt;strong&gt;×&lt;/strong&gt; to clear the search.&lt;/p&gt;</content>
</entry>
<entry>
<title>Save a Working Note as a Standard Note</title>
<link href="https://changelog.nilear.com/2026/save-a-working-note-as-a-standard-note/"/>
<id>https://changelog.nilear.com/2026/save-a-working-note-as-a-standard-note/</id>
<published>2026-10-17T00:00:00Z</published>
<updated>2026-10-17T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Write a note you will want again? Open the ... menu to the right of the note in Working Notes and choose Save as Standard Note.</summary>
<content type="html">&lt;p&gt;Write a note you will want again? Open the &lt;strong&gt;...&lt;/strong&gt; menu to the right of the note in Working Notes and choose &lt;strong&gt;Save as Standard Note&lt;/strong&gt;. Give it a name and it is added to the &lt;strong&gt;Add Note&lt;/strong&gt; list straight away, ready to use on your next ticket.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/SaveStandardNote.png&quot; alt=&quot;Save a Working Note as a Standard Note&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;Standard notes are kept in ConnectWise and are shared: everyone in your company sees them in their Add Note list. By default a saved note is offered only on tickets of the same board; tick &lt;strong&gt;Show on all boards&lt;/strong&gt; to offer it everywhere. Notes with images cannot be saved.&lt;/p&gt;</content>
</entry>
<entry>
<title>Add Phases to a Project</title>
<link href="https://changelog.nilear.com/2026/add-phases-to-a-project/"/>
<id>https://changelog.nilear.com/2026/add-phases-to-a-project/</id>
<published>2026-10-17T00:00:00Z</published>
<updated>2026-10-17T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>A project&apos;s Work Plan now has an Add Phase button. Use the button beside a phase&apos;s + to add a sub-phase under it.</summary>
<content type="html">&lt;p&gt;A project&amp;#39;s &lt;strong&gt;Work Plan&lt;/strong&gt; now has an &lt;strong&gt;Add Phase&lt;/strong&gt; button. Use the button beside a phase&amp;#39;s &lt;strong&gt;+&lt;/strong&gt; to add a sub-phase under it. Phases are created in ConnectWise as you, so your ConnectWise role decides who may add one.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/WorkPlanAddPhase.png&quot; alt=&quot;Add Phases to a Project&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>See and Edit Your Custom Rules Behind a Nilear AI Result</title>
<link href="https://changelog.nilear.com/2026/see-and-edit-your-custom-rules-behind-a-nilear-ai-change/"/>
<id>https://changelog.nilear.com/2026/see-and-edit-your-custom-rules-behind-a-nilear-ai-change/</id>
<published>2026-10-17T00:00:00Z</published>
<updated>2026-10-17T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Nilear AI results on a ticket now link to your company&apos;s custom rules for that tool, for the ticket&apos;s board and for all boards. Administrators can edit them there.</summary>
<content type="html">&lt;p&gt;The results of the Nilear AI tools on a ticket now link to the rules your company added for that tool. After &lt;strong&gt;Polish Summary&lt;/strong&gt;, for example, the suggested summaries offer &lt;strong&gt;Summary Rules&lt;/strong&gt; at the bottom left.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/AiRulesSummaryLink.png&quot; alt=&quot;Summary Rules at the bottom of the Polish Summary suggestions&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;The link shows the rules for the ticket&amp;#39;s board, and the global rules that apply on every board. Nilear AI follows them on top of its own built-in instructions.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/AiRulesModal.png&quot; alt=&quot;The custom board and global rules for Polish Summary&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Suggest TSI&lt;/strong&gt;, &lt;strong&gt;Create Ticket Goals&lt;/strong&gt;, &lt;strong&gt;Split Ticket&lt;/strong&gt; and &lt;strong&gt;Suggest Company / Contact&lt;/strong&gt; link to their rules the same way. &lt;strong&gt;Polish Notes&lt;/strong&gt; and &lt;strong&gt;Polish Email&lt;/strong&gt; do too, and so does a &lt;strong&gt;New Company&lt;/strong&gt; form filled in from the company&amp;#39;s website (&lt;strong&gt;Company Profile Rules&lt;/strong&gt;, at the top). These three tools have only global rules, as they do not run per board.&lt;/p&gt;
&lt;p&gt;Everyone can read the rules. Administrators also get an &lt;strong&gt;Edit&lt;/strong&gt; button on each section; a saved change is used by the next Nilear AI run, and saving an empty box removes those rules.&lt;/p&gt;</content>
</entry>
<entry>
<title>Your Own Polish Notes and Polish Email Rules</title>
<link href="https://changelog.nilear.com/2026/your-own-polish-notes-and-polish-email-rules/"/>
<id>https://changelog.nilear.com/2026/your-own-polish-notes-and-polish-email-rules/</id>
<published>2026-10-17T00:00:00Z</published>
<updated>2026-10-17T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Each member can now keep personal rules for Polish Notes and Polish Email, which Nilear AI adds to the company&apos;s global rules for that member&apos;s own requests.</summary>
<content type="html">&lt;p&gt;You can now give &lt;strong&gt;Polish Notes&lt;/strong&gt; and &lt;strong&gt;Polish Email&lt;/strong&gt; your own rules, such as how to sign off or how long a reply should be. Nilear AI adds them to your company&amp;#39;s global rules each time you polish. They apply only to your own requests.&lt;/p&gt;
&lt;p&gt;Open them from &lt;strong&gt;My Polish Email rules…&lt;/strong&gt; at the bottom of the tone menu beside &lt;strong&gt;Polish&lt;/strong&gt;, from &lt;strong&gt;My Polish Notes rules…&lt;/strong&gt; in the notes&amp;#39; AI menu, or from the &lt;strong&gt;Polish Email Rules&lt;/strong&gt; and &lt;strong&gt;Polish Notes Rules&lt;/strong&gt; links on a polished result. Under &lt;strong&gt;Your personal rules&lt;/strong&gt;, press &lt;strong&gt;Edit&lt;/strong&gt;, write your rules and press &lt;strong&gt;Save&lt;/strong&gt;. Saving an empty box removes them.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/AiPersonalPolishRules.png&quot; alt=&quot;Your company&apos;s global rules and your personal rules for Polish Email&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;Every member can edit their own rules, and only they can change them; administrators can read them on NilearX&amp;#39;s Global Instructions page. They never replace your company&amp;#39;s rules: where the two disagree, your company&amp;#39;s rules win. Personal rules can be up to 4,000 characters long.&lt;/p&gt;</content>
</entry>
<entry>
<title>Mark Working Notes Internal or Resolution</title>
<link href="https://changelog.nilear.com/2026/mark-working-notes-internal-or-resolution/"/>
<id>https://changelog.nilear.com/2026/mark-working-notes-internal-or-resolution/</id>
<published>2026-10-16T00:00:00Z</published>
<updated>2026-10-16T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>The three-dot menu of a working note in Work on Ticket now offers Mark as Internal Note and Mark as Resolution Note in place of Mark as Internal Time Note.</summary>
<content type="html">&lt;p&gt;The three-dot menu of a working note in Work on Ticket now offers &lt;strong&gt;Mark as Internal Note&lt;/strong&gt; and &lt;strong&gt;Mark as Resolution Note&lt;/strong&gt; in place of Mark as Internal Time Note. A marked note is labelled &lt;strong&gt;INTERNAL&lt;/strong&gt; or &lt;strong&gt;RESOLUTION&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/WorkingNoteMarks.png&quot; alt=&quot;Mark Working Notes Internal or Resolution&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;When the session&amp;#39;s time entry is saved, the Internal notes become one &lt;strong&gt;Internal Analysis&lt;/strong&gt; ticket note and the Resolution notes one &lt;strong&gt;Resolution&lt;/strong&gt; ticket note, in the order the notes appear, while the unmarked notes go on the time entry as before. When every note carries the same mark, the time entry itself is flagged Internal Analysis or Resolution and no separate ticket note is written. With &lt;strong&gt;Don&amp;#39;t Record Time&lt;/strong&gt;, each kind is saved as a ticket note of its own.&lt;/p&gt;</content>
</entry>
<entry>
<title>Queued Statuses with a Reason</title>
<link href="https://changelog.nilear.com/2026/queued-statuses-with-a-reason/"/>
<id>https://changelog.nilear.com/2026/queued-statuses-with-a-reason/</id>
<published>2026-10-14T00:00:00Z</published>
<updated>2026-10-14T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Besides Queued, a ticket status named Queued - reason, for example Queued - Follow up, now adds the ticket to MTX&apos;s Queue when a ticket is moved into it, in MTX or in ConnectWise.</summary>
<content type="html">&lt;p&gt;Besides &lt;strong&gt;Queued&lt;/strong&gt;, a ticket status named &lt;strong&gt;Queued -&lt;/strong&gt; &lt;em&gt;reason&lt;/em&gt;, for example &lt;strong&gt;Queued - Follow up&lt;/strong&gt;, now adds the ticket to MTX&amp;#39;s &lt;strong&gt;Queue&lt;/strong&gt; when a ticket is moved into it, in MTX or in ConnectWise. Capitalisation does not matter. Give such a status the &lt;strong&gt;Responded&lt;/strong&gt; SLA escalation: a Waiting or Resolved escalation takes the ticket off the Queue again. Names without the &amp;quot; - &amp;quot; separator, such as &lt;strong&gt;Queued for Support&lt;/strong&gt;, work as before.&lt;/p&gt;</content>
</entry>
<entry>
<title>Contact Details from Ticket Notes</title>
<link href="https://changelog.nilear.com/2026/contact-details-from-ticket-notes/"/>
<id>https://changelog.nilear.com/2026/contact-details-from-ticket-notes/</id>
<published>2026-10-13T00:00:00Z</published>
<updated>2026-10-13T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Hover over the name or picture of a contact on a ticket note to see their email addresses and phone numbers.</summary>
<content type="html">&lt;p&gt;Hover over the name or picture of a contact on a ticket note to see their email addresses and phone numbers. Click one to email or call, or copy it to the clipboard. On touch screens, tap the name.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/NoteAuthorContactCard.png&quot; alt=&quot;Contact Details from Ticket Notes&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Enter Hours on New Time Entries</title>
<link href="https://changelog.nilear.com/2026/enter-hours-on-new-time-entries/"/>
<id>https://changelog.nilear.com/2026/enter-hours-on-new-time-entries/</id>
<published>2026-10-12T00:00:00Z</published>
<updated>2026-10-12T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>The End Time step of the New Time Entry form has a new Hours field, so you can say how long the work took if the current time as the end time is not sufficient.</summary>
<content type="html">&lt;p&gt;The End Time step of the &lt;strong&gt;New Time Entry&lt;/strong&gt; form has a new &lt;strong&gt;Hours&lt;/strong&gt; field, so you can say how long the work took if the current time as the end time is not sufficient. Type a decimal such as 0.25 or 0.5 and the Time End is set to the Time Start plus that many hours, rounded to the nearest minute. Change the Time End instead and the Hours follow it, so you can use whichever is easier.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/NewTimeEntryHours.png&quot; alt=&quot;Enter Hours on New Time Entries&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;Hours is measured from the Time Start to the Time End, before any Deduct Hours, as in the Work on Ticket &lt;strong&gt;Manually Set Time&lt;/strong&gt; window. A time entry cannot run past midnight, so Hours that would end the entry the next day are refused. A Time End set from Hours is kept when you finish the time entry, rather than being moved to the current time.&lt;/p&gt;</content>
</entry>
<entry>
<title>Always Ask for Status on New Tickets</title>
<link href="https://changelog.nilear.com/2026/always-ask-for-status-on-new-tickets/"/>
<id>https://changelog.nilear.com/2026/always-ask-for-status-on-new-tickets/</id>
<published>2026-10-12T00:00:00Z</published>
<updated>2026-10-12T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>When a Board is chosen for a new ticket, MTX sets the Board&apos;s Default New Status and skips the Status step.</summary>
<content type="html">&lt;p&gt;When a Board is chosen for a new ticket, MTX sets the Board&amp;#39;s Default New Status and skips the Status step. Accounts that want every new ticket&amp;#39;s status chosen on purpose can now turn on &lt;strong&gt;Always Ask for Status&lt;/strong&gt; in Settings → My Tickets → MTX Interface. The new ticket then always stops at the Status step, and the Board&amp;#39;s Default New Status is offered as a one-click &lt;strong&gt;Default&lt;/strong&gt; button above the list of statuses instead of being set automatically.&lt;/p&gt;
&lt;p&gt;The setting is off by default, so new tickets work as before until an administrator turns it on.&lt;/p&gt;</content>
</entry>
<entry>
<title>Exclude Product Description from Invoice Descriptions</title>
<link href="https://changelog.nilear.com/2026/exclude-product-description-from-invoice-descriptions/"/>
<id>https://changelog.nilear.com/2026/exclude-product-description-from-invoice-descriptions/</id>
<published>2026-10-11T00:00:00Z</published>
<updated>2026-10-11T00:00:00Z</updated>
<category term="ConnectActive"/>
<summary>Leave the product description out of the invoice descriptions ConnectActive builds for Agreement Additions.</summary>
<content type="html">&lt;p&gt;ConnectActive builds an Agreement Addition&amp;#39;s invoice description from the product&amp;#39;s description in the ConnectWise product catalog, the optional &lt;strong&gt;Top Comment&lt;/strong&gt; and, when selected, the list of covered users. A new &lt;strong&gt;Exclude Product Description&lt;/strong&gt; option, under the Top Comment of each agreement mapping, leaves the product description out, so the Top Comment alone starts the invoice description. Use it to keep a description that is specific to that addition.&lt;/p&gt;
&lt;p&gt;With the option on, the addition&amp;#39;s own description is not used either when the product catalog cannot be read, and ConnectActive no longer reads the product catalog for that addition. If the Top Comment is left empty, the invoice description starts with the user list. The option is off by default, so existing invoice descriptions are unchanged. The setting can be found under ConnectActive -&amp;gt; Companies -&amp;gt; select a company -&amp;gt; Agreements -&amp;gt; the agreement mapping -&amp;gt; Top Comment.&lt;/p&gt;</content>
</entry>
<entry>
<title>Set Configuration Contacts from Last Login</title>
<link href="https://changelog.nilear.com/2026/set-configuration-contacts-from-last-login/"/>
<id>https://changelog.nilear.com/2026/set-configuration-contacts-from-last-login/</id>
<published>2026-10-10T00:00:00Z</published>
<updated>2026-10-10T00:00:00Z</updated>
<category term="ConnectActive"/>
<summary>A new Configuration Contacts option has been added to ConnectActive&apos;s Overwrite Options.</summary>
<content type="html">&lt;p&gt;A new &lt;strong&gt;Configuration Contacts&lt;/strong&gt; option has been added to ConnectActive&amp;#39;s &lt;strong&gt;Overwrite Options&lt;/strong&gt;. ConnectActive can set the Contact on a ConnectWise Configuration to the synced contact of the user who last logged in to it.&lt;/p&gt;
&lt;p&gt;By default this option is &lt;strong&gt;off&lt;/strong&gt;, and configuration contacts are left alone. The other choices are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Set Configuration Contact from last login when empty or inactive&lt;/strong&gt;: fills a configuration that has no contact, or whose contact is inactive in ConnectWise. A contact chosen by hand is kept, and a departed user&amp;#39;s machine passes to its new user once their contact has been deactivated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Always set Configuration Contact from last login&lt;/strong&gt;: replaces any contact that differs from the last login.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Only active Workstation, Desktop and Laptop configurations are affected, at most 50 are updated per sync, and a contact that is inactive in ConnectWise is never assigned. The setting can be found under ConnectActive -&amp;gt; Companies -&amp;gt; select a company -&amp;gt; Overwrite Options.&lt;/p&gt;</content>
</entry>
<entry>
<title>Keep Agreement on Contact/Site Change</title>
<link href="https://changelog.nilear.com/2026/keep-agreement-on-contact-site-change/"/>
<id>https://changelog.nilear.com/2026/keep-agreement-on-contact-site-change/</id>
<published>2026-10-06T00:00:00Z</published>
<updated>2026-10-06T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Changing a ticket&apos;s Contact or Site checks the ticket&apos;s agreement against ConnectWise&apos;s default agreement, and either sets it or asks which agreement to use.</summary>
<content type="html">&lt;p&gt;Changing a ticket&amp;#39;s Contact or Site checks the ticket&amp;#39;s agreement against ConnectWise&amp;#39;s default agreement, and either sets it or asks which agreement to use. Accounts that choose the agreement themselves can now turn on &lt;strong&gt;Keep Agreement on Contact/Site Change&lt;/strong&gt; in Settings → My Tickets → MTX Interface, and the agreement is kept when only the Contact or Site changes. Changing the Company always checks the agreement again, because the old agreement belongs to the old Company.&lt;/p&gt;</content>
</entry>
<entry>
<title>Email Notes: Email View and Text View</title>
<link href="https://changelog.nilear.com/2026/email-notes-email-view-and-text-view/"/>
<id>https://changelog.nilear.com/2026/email-notes-email-view-and-text-view/</id>
<published>2026-10-06T00:00:00Z</published>
<updated>2026-10-06T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>A ticket note that arrived by email is shown the way the sender wrote it, with its formatting, tables and inline images.</summary>
<content type="html">&lt;p&gt;A ticket note that arrived by email is shown the way the sender wrote it, with its formatting, tables and inline images. A new &lt;strong&gt;Text View&lt;/strong&gt; link at the top right of the note switches it to the plain note text as ConnectWise stores it, for the emails that read better that way, and &lt;strong&gt;Email View&lt;/strong&gt; switches it back.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/EmailNoteEmailView.png&quot; alt=&quot;Email Notes: Email View and Text View&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;Click an inline image in the Email View to open it full size. &lt;strong&gt;Edit Note&lt;/strong&gt; now always opens with the note text rather than the email&amp;#39;s HTML; once a note has been edited it opens in the Text View, with the original email one click away. Nilear Live receives the note text for new email notes.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/EmailNoteTextView.png&quot; alt=&quot;Email Notes: Email View and Text View&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Ticket List Column Widths</title>
<link href="https://changelog.nilear.com/2026/ticket-list-column-widths/"/>
<id>https://changelog.nilear.com/2026/ticket-list-column-widths/</id>
<published>2026-09-30T00:00:00Z</published>
<updated>2026-09-30T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>You can now set the width of the columns in the ticket list. Turn off Responsive Web Design Columns in the Customize Columns dialog, then drag the right edge of a column heading.</summary>
<content type="html">&lt;p&gt;You can now set the width of the columns in the ticket list. Turn off &lt;strong&gt;Responsive Web Design Columns&lt;/strong&gt; in the &lt;strong&gt;Customize Columns&lt;/strong&gt; dialog, then drag the right edge of a column heading. Only that edge moves; the other columns keep their widths and the list scrolls sideways when it needs more room.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Double-click&lt;/strong&gt; an edge to return that column to its automatic width. Your widths are remembered with your column choice, follow you to the Ticket Queue and Configuration Review lists, and are cleared by &lt;strong&gt;Reset to MTX Defaults&lt;/strong&gt;, which now also turns Responsive Web Design Columns back on.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/ColumnWidths.png&quot; alt=&quot;Ticket List Column Widths&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Link an Activity to a Ticket</title>
<link href="https://changelog.nilear.com/2026/link-an-activity-to-a-ticket/"/>
<id>https://changelog.nilear.com/2026/link-an-activity-to-a-ticket/</id>
<published>2026-09-30T00:00:00Z</published>
<updated>2026-09-30T00:00:00Z</updated>
<category term="MTX: My Schedule"/>
<summary>An activity now has a Ticket field next to Company and Contact, like the Ticket picker on ConnectWise&apos;s Activity screen.</summary>
<content type="html">&lt;p&gt;An activity now has a &lt;strong&gt;Ticket&lt;/strong&gt; field next to Company and Contact, like the Ticket picker on ConnectWise&amp;#39;s Activity screen. Click it to pick a service ticket from the ticket search list: when the activity has a company only that company&amp;#39;s tickets are offered, otherwise every company is searched. Once linked, the activity moves under the ticket and appears on its &lt;strong&gt;Scheduling&lt;/strong&gt; tab, and the ConnectWise activity is updated to reference the ticket.&lt;/p&gt;
&lt;p&gt;To detach an activity, open the ticket&amp;#39;s Scheduling tab and click the &lt;strong&gt;x&lt;/strong&gt; beside the Ticket on the activity&amp;#39;s card. The activity keeps its type, status, notes, members and time entries either way. As with activities linked in ConnectWise, a linked activity&amp;#39;s member counts as a resource on the ticket.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/LinkActivityTicket.png&quot; alt=&quot;Link an Activity to a Ticket&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Configuration Search Columns</title>
<link href="https://changelog.nilear.com/2026/configuration-search-columns/"/>
<id>https://changelog.nilear.com/2026/configuration-search-columns/</id>
<published>2026-09-30T00:00:00Z</published>
<updated>2026-09-30T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>The configuration search list - on the Configurations tab, under a company&apos;s Configurations and on a ticket&apos;s Configurations tab - now has an Edit Columns button () next to Create.</summary>
<content type="html">&lt;p&gt;The configuration search list - on the Configurations tab, under a company&amp;#39;s Configurations and on a ticket&amp;#39;s Configurations tab - now has an &lt;strong&gt;Edit Columns&lt;/strong&gt; button (&lt;i class=&quot;fa fa-columns&quot;&gt;&lt;/i&gt;) next to Create. Tick the columns you want, drag them into the order you want, and the list remembers your choice wherever you sign in. &lt;strong&gt;Reset&lt;/strong&gt; returns the standard columns.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/ConfigSearchEditColumns.png&quot; alt=&quot;Configuration Search Columns&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;p&gt;Every ConnectWise &lt;strong&gt;configuration custom field&lt;/strong&gt; is offered as a column too. Custom-field columns display the value only; sorting and filtering stay on the standard columns.&lt;/p&gt;</content>
</entry>
<entry>
<title>Skip Schedule &amp; Commit at Wrap-up</title>
<link href="https://changelog.nilear.com/2026/skip-schedule-and-commit-at-wrap-up/"/>
<id>https://changelog.nilear.com/2026/skip-schedule-and-commit-at-wrap-up/</id>
<published>2026-09-29T00:00:00Z</published>
<updated>2026-09-29T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Skip Schedule &amp; Commit now asks what to do when the ticket still has schedule records that have not yet taken place.</summary>
<content type="html">&lt;p&gt;&lt;strong&gt;Skip Schedule &amp;amp; Commit&lt;/strong&gt; now asks what to do when the ticket still has schedule records that have not yet taken place. You can &lt;strong&gt;Keep All&lt;/strong&gt;, &lt;strong&gt;Remove All&lt;/strong&gt;, remove individual records, or cancel and return to Wrap-up.&lt;/p&gt;
&lt;p&gt;The &lt;strong&gt;Keep Schedule &amp;amp; Commit&lt;/strong&gt; button will now also appear for any schedule record of yours on the ticket that has not started yet. When you have none, it offers the earliest schedule record of another member, showing their name. Keeping a schedule record leaves it exactly as it is.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/KeepRemoveFutureSchedules.png&quot; alt=&quot;Skip Schedule &amp;amp; Commit at Wrap-up&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Non-Ticket Users on the Availability Board</title>
<link href="https://changelog.nilear.com/2026/non-ticket-users-on-the-availability-board/"/>
<id>https://changelog.nilear.com/2026/non-ticket-users-on-the-availability-board/</id>
<published>2026-09-20T00:00:00Z</published>
<updated>2026-09-20T00:00:00Z</updated>
<category term="MTX: Availability"/>
<summary>Settings -&gt; Member Management -&gt; Users now has a Non-Ticket User checkbox beside Availability Board.</summary>
<content type="html">&lt;p&gt;Settings -&amp;gt; Member Management -&amp;gt; Users now has a &lt;strong&gt;Non-Ticket User&lt;/strong&gt; checkbox beside Availability Board. A flagged member shows as &lt;strong&gt;In&lt;/strong&gt; during working hours with neutral styling and no idle time, and is not asked &amp;quot;Are you working on anything right now?&amp;quot;. Meetings, PTO, Lunch, work location and every other status work exactly as before, and a flagged member who does pick up a ticket still shows &lt;strong&gt;In Progress&lt;/strong&gt; with the running time.&lt;/p&gt;</content>
</entry>
<entry>
<title>Notes Filter</title>
<link href="https://changelog.nilear.com/2026/notes-filter/"/>
<id>https://changelog.nilear.com/2026/notes-filter/</id>
<published>2026-09-20T00:00:00Z</published>
<updated>2026-09-20T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>The Notes tab of a ticket now has a Filter icon beside the Classic/Modern and sort toggles.</summary>
<content type="html">&lt;p&gt;The &lt;strong&gt;Notes&lt;/strong&gt; tab of a ticket now has a &lt;strong&gt;Filter&lt;/strong&gt; icon beside the Classic/Modern and sort toggles. Use it to hide &lt;strong&gt;Contact&lt;/strong&gt;, &lt;strong&gt;Member&lt;/strong&gt;, &lt;strong&gt;Internal&lt;/strong&gt;, &lt;strong&gt;Discussion&lt;/strong&gt; or &lt;strong&gt;Resolution&lt;/strong&gt; notes, or to show only the notes containing a search string.&lt;/p&gt;
&lt;p&gt;The filter is remembered for that ticket.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/NotesFilter.png&quot; alt=&quot;Notes Filter&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Contact Title</title>
<link href="https://changelog.nilear.com/2026/contact-title/"/>
<id>https://changelog.nilear.com/2026/contact-title/</id>
<published>2026-09-10T00:00:00Z</published>
<updated>2026-09-10T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>The Contact selector on tickets and schedule records now shows the contact&apos;s ConnectWise Title.</summary>
<content type="html">&lt;p&gt;The &lt;strong&gt;Contact&lt;/strong&gt; selector on a ticket and on a schedule record now shows the contact&amp;#39;s ConnectWise &lt;strong&gt;Title&lt;/strong&gt; beside their name, after the phone number and separated by a ◆, so you can see who you are dealing with without opening the contact.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/ContactTitle.png&quot; alt=&quot;Contact Title&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Exclude Boards from SLA Warnings</title>
<link href="https://changelog.nilear.com/2026/exclude-boards-from-sla-warnings/"/>
<id>https://changelog.nilear.com/2026/exclude-boards-from-sla-warnings/</id>
<published>2026-08-29T00:00:00Z</published>
<updated>2026-08-29T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>The SLA Warning window now has a Boards control, letting you exclude boards you do not want SLA warnings for.</summary>
<content type="html">&lt;p&gt;The &lt;strong&gt;SLA Warning&lt;/strong&gt; window now has a &lt;strong&gt;Boards&lt;/strong&gt; control, letting you exclude boards you do not want SLA warnings for. Tickets on an excluded board no longer appear in the SLA Warning window and no longer trigger the automatic popup.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/SlaExcludeBoard.png&quot; alt=&quot;Exclude Boards from SLA Warnings&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Spectator Control</title>
<link href="https://changelog.nilear.com/2026/spectator-control/"/>
<id>https://changelog.nilear.com/2026/spectator-control/</id>
<published>2026-08-27T00:00:00Z</published>
<updated>2026-08-27T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>Allowing the creation of Spectators, schedule records with no date or time, are now controlled on their own, by Allow Spectators under Settings -&gt; My Tickets -&gt; Interface.</summary>
<content type="html">&lt;p&gt;Allowing the creation of Spectators, schedule records with no date or time, are now controlled on their own, by &lt;strong&gt;Allow Spectators&lt;/strong&gt; under Settings -&amp;gt; My Tickets -&amp;gt; Interface. It is on by default (Spectators allowed).&lt;/p&gt;
&lt;p&gt;Spectator records already on your tickets are unaffected either way, and continue to show and filter as before.&lt;/p&gt;</content>
</entry>
<entry>
<title>Contact Mappings</title>
<link href="https://changelog.nilear.com/2026/contact-mappings/"/>
<id>https://changelog.nilear.com/2026/contact-mappings/</id>
<published>2026-08-14T00:00:00Z</published>
<updated>2026-08-14T00:00:00Z</updated>
<category term="ConnectActive"/>
<summary>Introducing Contact Mappings – keep ConnectWise Contact Types and Contact Custom Fields in step with your directory automatically, instead of setting them by hand and watching them drift.</summary>
<content type="html">&lt;p&gt;Introducing &lt;strong&gt;Contact Mappings&lt;/strong&gt; – keep ConnectWise &lt;strong&gt;Contact Types&lt;/strong&gt; and &lt;strong&gt;Contact Custom Fields&lt;/strong&gt; in step with your directory automatically, instead of setting them by hand and watching them drift.&lt;/p&gt;
&lt;p&gt;A new &lt;strong&gt;Contact Mappings&lt;/strong&gt; tab has been added under ConnectActive -&amp;gt; Companies -&amp;gt; select a company. Map any Group, Microsoft 365 License or OU – the same list Site Mapping offers – and ConnectActive brings every contact in it into line on each sync:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Assign Contact Types&lt;/strong&gt;: everyone in the group is given the Contact Types you pick&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Remove Contact Types&lt;/strong&gt;: or take a Contact Type away from everyone in the group&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Remove all other existing Contact Types&lt;/strong&gt;: on by default, so a contact ends up with exactly the Contact Types the mapping assigns and nothing else&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Custom Fields&lt;/strong&gt;: set a Contact Custom Field for the whole group – drop-down fields offer their ConnectWise values – or clear whatever value is already there&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For example, everyone in &lt;strong&gt;Microsoft 365 E3&lt;/strong&gt; can be assigned &lt;strong&gt;Managed User&lt;/strong&gt;, removed from &lt;strong&gt;Unmanaged User&lt;/strong&gt;, and have their &lt;strong&gt;Level&lt;/strong&gt; custom field set to &lt;strong&gt;Gold&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Default Mapping for New Contacts.&lt;/strong&gt; Set the Contact Types and Custom Field values every contact ConnectActive creates should start with. When it assigns Contact Types they take the place of the ones ConnectWise flags as default, so new contacts arrive classified the way you want them rather than needing to be corrected afterwards.&lt;/p&gt;
&lt;p&gt;Where mappings overlap, a group mapping wins over the Default Mapping – so a Default Mapping that assigns &lt;strong&gt;Unmanaged User&lt;/strong&gt; together with a group that removes it leaves the contact without it. If two group mappings disagree, the one added most recently wins.&lt;/p&gt;
&lt;p&gt;The &lt;strong&gt;Review&lt;/strong&gt; page badges every Contact Type and Custom Field it intends to change before anything is written to ConnectWise. Hover a badge and it tells you what caused it – for example &lt;em&gt;&amp;quot;Setting custom field Level to Gold as the user is a member of group &amp;#39;Microsoft 365 E3&amp;#39;&amp;quot;&lt;/em&gt;. Contacts flagged &lt;strong&gt;Not Sync&lt;/strong&gt; are left alone.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/ContactMapping.png&quot; alt=&quot;Contact Mappings&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Companies: Create &amp; Edit</title>
<link href="https://changelog.nilear.com/2026/companies-create-and-edit/"/>
<id>https://changelog.nilear.com/2026/companies-create-and-edit/</id>
<published>2026-08-10T00:00:00Z</published>
<updated>2026-08-10T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>A new Companies option has been added to the View Additional Options menu.</summary>
<content type="html">&lt;div class=&quot;mt-2 mb-2&quot;&gt;&lt;img src=&quot;https://media.nilear.com/changelog/CompaniesOption.png&quot; class=&quot;border&quot; alt=&quot;Companies: Create &amp;amp; Edit&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/div&gt;&lt;p&gt;A new &lt;strong&gt;Companies&lt;/strong&gt; option has been added to the &lt;strong&gt;View Additional Options&lt;/strong&gt; menu. It opens full screen with the Company Lookup you already know - search and Quick Picks - alongside a &lt;strong&gt;NEW COMPANY&lt;/strong&gt; button, so a company can be created without leaving MTX.&lt;/p&gt;
&lt;p&gt;Selecting a company opens it full screen with everything about it in one place:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Company&lt;/strong&gt;: edit the company itself - name, phone, web site, social links, address, Company ID, status, territory, market, Company Types and ConnectWise Custom Fields&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Contacts&lt;/strong&gt;: the company&amp;#39;s address book&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tickets&lt;/strong&gt;: its open and closed tickets&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Configs&lt;/strong&gt;: its configurations&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sites&lt;/strong&gt;: create and edit sites, including the address, tax code, time zone and calendar&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Teams&lt;/strong&gt;: add, change and remove team members, choosing either a Member or one of the company&amp;#39;s Contacts for each role&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Creating from a domain.&lt;/strong&gt; Creating a company starts by asking for its domain. The company&amp;#39;s public website is then read to fill in the form for you - name, Company ID, phone, web site, Facebook, LinkedIn and Twitter/X, the address and the market - so most of a new company is entered before you type anything. You can also add its first Contact at the same time, either as the Primary Contact or as a contact only.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Catches duplicates first&lt;/strong&gt;: before the form opens you are shown any company that might already be this one, matched on website, on name, or on a similar name - inactive companies included - so a second copy is not created by accident&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Never in the way&lt;/strong&gt;: skip the domain for a blank form, and a site that cannot be read still opens the form rather than stopping you&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Editing works a little differently to the rest of MTX: changes are collected and written together when you press &lt;strong&gt;SAVE CHANGES&lt;/strong&gt;, and the bar at the bottom of the form keeps a running count of what is still unsaved.&lt;/p&gt;
&lt;div class=&quot;alert alert-info mb-0&quot;&gt;&lt;strong&gt;Privacy &amp;amp; Security:&lt;/strong&gt; Only the domain name you enter is sent for the website lookup - no ticket, company or customer data leaves ConnectWise. Each request is stateless, and your data is not used to train AI models.&lt;/div&gt;</content>
</entry>
<entry>
<title>Suggest Company &amp; Contact with AI</title>
<link href="https://changelog.nilear.com/2026/suggest-company-and-contact-with-ai/"/>
<id>https://changelog.nilear.com/2026/suggest-company-and-contact-with-ai/</id>
<published>2026-08-06T00:00:00Z</published>
<updated>2026-08-06T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>AI reads the ticket, works out which company and contact it belongs to, and matches them in ConnectWise.</summary>
<content type="html">&lt;div class=&quot;polish-email-title polish-email-title--contact&quot; aria-label=&quot;Suggest Contact with AI&quot;&gt;&lt;div class=&quot;polish-email-title__icon&quot;&gt;&lt;i class=&quot;fa-solid fa-building-user base-icon&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-1&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-2&quot;&gt;&lt;/i&gt;&lt;/div&gt;&lt;div class=&quot;polish-email-title__content&quot;&gt;&lt;div class=&quot;polish-email-title__eyebrow d-none&quot;&gt;New Feature&lt;/div&gt;&lt;div class=&quot;polish-email-title__headline-wrap&quot;&gt;&lt;div class=&quot;polish-email-title__ghost&quot;&gt;suggest contact with ai&lt;/div&gt;&lt;h2 class=&quot;polish-email-title__headline&quot;&gt;&lt;span class=&quot;word&quot;&gt;Suggest&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;Contact&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;with&lt;/span&gt; &lt;span class=&quot;word ai&quot;&gt;AI&lt;/span&gt;&lt;/h2&gt;&lt;span class=&quot;shimmer&quot;&gt;&lt;/span&gt;&lt;/div&gt;&lt;div class=&quot;polish-email-title__subtitle&quot;&gt;Catchall &lt;span class=&quot;arrow&quot;&gt;→&lt;/span&gt; Company &amp;amp; Contact&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;p&gt;Introducing &lt;strong&gt;AI-Powered Company &amp;amp; Contact Suggestions&lt;/strong&gt; – let AI read the ticket and work out who it actually belongs to, then match that against ConnectWise so a mis-routed ticket can be corrected in a single click:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One-Click Suggestion&lt;/strong&gt;: Click the sparkle button next to the Company field to look up who the ticket belongs to&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reads the Original Request&lt;/strong&gt;: The AI works from the ticket&amp;#39;s initial description, where the sender, signature and any &amp;quot;on behalf of&amp;quot; wording live&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Instant on Catchall&lt;/strong&gt;: On a Catchall ticket with a single high-confidence match, the Company and Contact are set straight away without a dialog&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Available from the Company field on any ticket. Simply click the &lt;i class=&quot;far fa-sparkles&quot;&gt;&lt;/i&gt; button to get started:&lt;/p&gt;
&lt;div class=&quot;alert alert-info mb-0&quot;&gt;&lt;strong&gt;Privacy &amp;amp; Security:&lt;/strong&gt; The AI processes the ticket summary and the ticket&apos;s initial description to identify the Company and Contact. Each request is stateless, and your data is not used to train AI models.&lt;/div&gt;</content>
</entry>
<entry>
<title>Required Custom Fields on New Tickets</title>
<link href="https://changelog.nilear.com/2026/required-custom-fields-on-new-tickets/"/>
<id>https://changelog.nilear.com/2026/required-custom-fields-on-new-tickets/</id>
<published>2026-08-06T00:00:00Z</published>
<updated>2026-08-06T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>New Ticket now asks for required ConnectWise Custom Fields as the last question in the Category step, right after Urgency, Source and Type.</summary>
<content type="html">&lt;p&gt;&lt;strong&gt;New Ticket&lt;/strong&gt; now asks for required ConnectWise Custom Fields as the last question in the &lt;strong&gt;Category&lt;/strong&gt; step, right after Urgency, Source and Type. Fill them in and the ticket is created complete, so it will not be held up later when someone tries to resolve it.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The question is skipped entirely when the ticket&amp;#39;s board has no required Custom Fields&lt;/li&gt;
&lt;li&gt;Custom Fields ConnectWise marks read-only, hides from the screen, or scopes to another business unit or location are never asked for&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
<entry>
<title>Required Custom Fields Before Resolving</title>
<link href="https://changelog.nilear.com/2026/required-custom-fields-before-resolving/"/>
<id>https://changelog.nilear.com/2026/required-custom-fields-before-resolving/</id>
<published>2026-08-06T00:00:00Z</published>
<updated>2026-08-06T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Custom Fields marked Required in ConnectWise are now enforced when a ticket is resolved.</summary>
<content type="html">&lt;p&gt;Custom Fields marked &lt;strong&gt;Required&lt;/strong&gt; in ConnectWise are now enforced when a ticket is resolved.&lt;/p&gt;
&lt;p&gt;Choosing a resolved status - from &lt;strong&gt;Wrap-up&lt;/strong&gt; or from the status dropdown on a ticket - now opens a dialog listing any required Custom Field that is still empty. Fill them in and the status change goes through; cancel and the ticket stays where it was. The status dropdown also marks those statuses &lt;strong&gt;(Missing Custom Fields)&lt;/strong&gt; ahead of time.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Custom Fields ConnectWise marks read-only, hides from the screen, or scopes to another business unit or location are never enforced - they could never be completed&lt;/li&gt;
&lt;li&gt;Spam, cancelled and pending statuses are unaffected&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
<entry>
<title>Configuration Manage &amp; Remote Links</title>
<link href="https://changelog.nilear.com/2026/configuration-manage-and-remote-links/"/>
<id>https://changelog.nilear.com/2026/configuration-manage-and-remote-links/</id>
<published>2026-08-05T00:00:00Z</published>
<updated>2026-08-05T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>Server and Workstation configurations now offer Manage and Remote buttons that launch the device&apos;s management console (RMM) and remote session (such as ScreenConnect) in a new browser tab.</summary>
<content type="html">&lt;p&gt;Server and Workstation configurations now offer &lt;strong&gt;Manage&lt;/strong&gt; &lt;i class=&quot;fa fa-cog&quot;&gt;&lt;/i&gt; and &lt;strong&gt;Remote&lt;/strong&gt; &lt;i class=&quot;fas fa-desktop-alt&quot;&gt;&lt;/i&gt; buttons that launch the device&amp;#39;s management console (RMM) and remote session (such as ScreenConnect) in a new browser tab. They appear at the top of an open configuration.&lt;/p&gt;
&lt;p&gt;The links are read-only and must already be populated for the configuration in ConnectWise by its associated RMM.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Shown only for configurations whose type name contains &lt;strong&gt;Server&lt;/strong&gt; or &lt;strong&gt;Workstation&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;A button is greyed out when its link has not been filled in by its RMM&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/RemoteLink.png&quot; alt=&quot;Configuration Manage &amp;amp; Remote Links&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Required Custom Fields on Configurations</title>
<link href="https://changelog.nilear.com/2026/required-custom-fields-on-configurations/"/>
<id>https://changelog.nilear.com/2026/required-custom-fields-on-configurations/</id>
<published>2026-08-05T00:00:00Z</published>
<updated>2026-08-05T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>Custom Fields marked Required in ConnectWise are now enforced on configurations.</summary>
<content type="html">&lt;p&gt;Custom Fields marked &lt;strong&gt;Required&lt;/strong&gt; in ConnectWise are now enforced on configurations.&lt;/p&gt;
&lt;p&gt;The &lt;strong&gt;Create Configuration&lt;/strong&gt; form asks for them up front. Pick a configuration type and any required Custom Field appears alongside the configuration questions, so the configuration is complete the moment it is created.&lt;/p&gt;
&lt;p&gt;Opening an existing configuration now warns you when a required Custom Field has no value, and highlights each one in the Custom Fields section. The rest of the configuration stays editable, and the warning clears as you fill them in.&lt;/p&gt;</content>
</entry>
<entry>
<title>Customer Responded Column</title>
<link href="https://changelog.nilear.com/2026/customer-responded-column/"/>
<id>https://changelog.nilear.com/2026/customer-responded-column/</id>
<published>2026-08-04T00:00:00Z</published>
<updated>2026-08-04T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>A new Responded column is now available in the Tickets table, flagging the tickets a customer has replied to.</summary>
<content type="html">&lt;p&gt;A new &lt;strong&gt;Responded&lt;/strong&gt; column is now available in the Tickets table, flagging &lt;i class=&quot;fa fa-flag-alt text-danger&quot;&gt;&lt;/i&gt; the tickets a customer has replied to. The column is off by default and can be enabled through the &lt;strong&gt;Customize Columns&lt;/strong&gt; menu, where it is listed as &lt;strong&gt;Customer Responded&lt;/strong&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Filter to &lt;strong&gt;Yes&lt;/strong&gt; or &lt;strong&gt;No&lt;/strong&gt;, and use the exclude toggle to flip it - for example, to hide everything a customer has already replied to&lt;/li&gt;
&lt;li&gt;Sort on the column to group the flagged tickets together&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The &lt;i class=&quot;fa fa-flag-alt&quot;&gt;&lt;/i&gt; button in the toolbar still switches to a dedicated view of every flagged ticket. The new column filter is different: it narrows the list you are already looking at, so it combines with your board, status and other column filters.&lt;/p&gt;</content>
</entry>
<entry>
<title>Overwrite Contact First Names</title>
<link href="https://changelog.nilear.com/2026/overwrite-contact-first-names/"/>
<id>https://changelog.nilear.com/2026/overwrite-contact-first-names/</id>
<published>2026-08-03T00:00:00Z</published>
<updated>2026-08-03T00:00:00Z</updated>
<category term="ConnectActive"/>
<summary>A new Overwrite CW First Name with AD Values option has been added to ConnectActive&apos;s Overwrite Options.</summary>
<content type="html">&lt;p&gt;A new &lt;strong&gt;Overwrite CW First Name with AD Values&lt;/strong&gt; option has been added to ConnectActive&amp;#39;s &lt;strong&gt;Overwrite Options&lt;/strong&gt;. When enabled, ConnectActive will replace a ConnectWise Contact&amp;#39;s first name whenever it differs from the value found in Microsoft 365, Active Directory or Google Workspace.&lt;/p&gt;
&lt;p&gt;By default this option is &lt;strong&gt;off&lt;/strong&gt;. ConnectActive normally leaves first names alone because ConnectWise often holds the nickname a contact goes by (&lt;strong&gt;Bob&lt;/strong&gt;) while the directory holds the legal first name (&lt;strong&gt;Robert&lt;/strong&gt;). Last names are always kept in sync.&lt;/p&gt;
&lt;p&gt;Turn this on for companies whose directory data is clean and should always take precedence. The setting can be found under ConnectActive -&amp;gt; Companies -&amp;gt; select a company -&amp;gt; Overwrite Options.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/OverwriteFirstName.png&quot; alt=&quot;Overwrite Contact First Names&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Multi-Value Column Filters</title>
<link href="https://changelog.nilear.com/2026/multi-value-column-filters/"/>
<id>https://changelog.nilear.com/2026/multi-value-column-filters/</id>
<published>2026-07-27T00:00:00Z</published>
<updated>2026-07-27T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>Column filters in the Tickets, My Queue and My Schedule tables can now match more than one value at a time.</summary>
<content type="html">&lt;p&gt;Column filters in the &lt;strong&gt;Tickets&lt;/strong&gt;, &lt;strong&gt;My Queue&lt;/strong&gt; and &lt;strong&gt;My Schedule&lt;/strong&gt; tables can now match more than one value at a time. Open any filter drop-down, switch it from &lt;strong&gt;Single&lt;/strong&gt; to &lt;strong&gt;Multiple&lt;/strong&gt;, then click each value you want. The menu stays open and a check mark marks every value you have selected.&lt;/p&gt;
&lt;p&gt;For example, the Board/Project filter can now show the &lt;strong&gt;Help Desk&lt;/strong&gt; and &lt;strong&gt;Sales&lt;/strong&gt; boards together instead of making you choose just one.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The column header shows &lt;strong&gt;&amp;quot;2 selected&amp;quot;&lt;/strong&gt; - hover over it to see the full list&lt;/li&gt;
&lt;li&gt;The exclude toggle applies to the whole selection, so excluding two boards hides tickets from both&lt;/li&gt;
&lt;li&gt;Switching back to &lt;strong&gt;Single&lt;/strong&gt; keeps the first value you selected&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Filters left on &lt;strong&gt;Single&lt;/strong&gt; behave exactly as they did before.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/MultiSelect.png&quot; alt=&quot;Multi-Value Column Filters&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Queue Targeting: Active Role</title>
<link href="https://changelog.nilear.com/2026/queue-targeting-active-role/"/>
<id>https://changelog.nilear.com/2026/queue-targeting-active-role/</id>
<published>2026-07-07T00:00:00Z</published>
<updated>2026-07-07T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>A new Active Role targeting option is now available in Queue Targeting rules. When enabled, only users whose Availability Active Role matches the specified value will be targeted.</summary>
<content type="html">&lt;p&gt;A new &lt;strong&gt;Active Role&lt;/strong&gt; targeting option is now available in Queue Targeting rules. When enabled, only users whose Availability Active Role matches the specified value will be targeted. Matching is case-insensitive and supports comma-separated roles. For example, a user with Active Role &lt;strong&gt;&amp;quot;dispatcher, on-call&amp;quot;&lt;/strong&gt; will match a targeting rule set to &lt;strong&gt;&amp;quot;Dispatcher&amp;quot;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Targeting on Active Role is helpful when roles and queue targeting need to be more fluid. For example, when the dispatcher is out on PTO, another member can take over Dispatcher duties for the day by setting their Active Role to &lt;strong&gt;&amp;quot;Dispatcher&amp;quot;&lt;/strong&gt; without needing to change the targeting rules.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/QueueActiveRole.png&quot; alt=&quot;Queue Targeting: Active Role&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Budget Hours Column</title>
<link href="https://changelog.nilear.com/2026/budget-hours-column/"/>
<id>https://changelog.nilear.com/2026/budget-hours-column/</id>
<published>2026-07-02T00:00:00Z</published>
<updated>2026-07-02T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>A new Budget column is now available in the Tickets table. The column can be enabled through the Customize Columns menu.</summary>
<content type="html">&lt;p&gt;A new &lt;strong&gt;Budget&lt;/strong&gt; column is now available in the Tickets table. The column can be enabled through the &lt;strong&gt;Customize Columns&lt;/strong&gt; menu.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/BudgetHours.png&quot; alt=&quot;Budget Hours Column&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Batch Schedule Actions</title>
<link href="https://changelog.nilear.com/2026/batch-schedule-actions/"/>
<id>https://changelog.nilear.com/2026/batch-schedule-actions/</id>
<published>2026-06-12T00:00:00Z</published>
<updated>2026-06-12T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>Select several schedule records in My Schedule and act on them at once, such as marking them all done.</summary>
<content type="html">&lt;p&gt;You can now select multiple schedule records in &lt;strong&gt;My Schedule&lt;/strong&gt; and perform bulk actions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mark as Done&lt;/strong&gt;: Bulk-complete selected records&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bulk Move&lt;/strong&gt;: Move selected records to a new date&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Toggle individual records with checkboxes, or select all visible rows at once.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/BulkScheduleUpdate.png&quot; alt=&quot;Batch Schedule Actions&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
<entry>
<title>Fixed Working On Schedule</title>
<link href="https://changelog.nilear.com/2026/fixed-working-on-schedule/"/>
<id>https://changelog.nilear.com/2026/fixed-working-on-schedule/</id>
<published>2026-06-09T00:00:00Z</published>
<updated>2026-06-09T00:00:00Z</updated>
<category term="MTX: General"/>
<summary>A new Fixed/Floating Working On Schedules setting has been added to MTX&apos;s Schedules settings.</summary>
<content type="html">&lt;p&gt;A new &lt;strong&gt;Fixed/Floating Working On Schedules&lt;/strong&gt; setting has been added to MTX&amp;#39;s Schedules settings. When MTX creates a real-time schedule record during a &amp;quot;Work on Ticket&amp;quot; session, it can now be created as either a &lt;strong&gt;Fixed&lt;/strong&gt; or &lt;strong&gt;Floating&lt;/strong&gt; schedule record.&lt;/p&gt;
&lt;p&gt;Enabling &lt;strong&gt;Create Fixed schedules for &amp;quot;Work on Ticket&amp;quot; sessions&lt;/strong&gt; instructs MTX to mark these schedule records as Fixed, which causes Microsoft Teams and other integrated calendar systems to show the member as &lt;strong&gt;Busy&lt;/strong&gt; during that time. This setting is enabled by default. It can be found under Settings → My Tickets → Schedules.&lt;/p&gt;</content>
</entry>
<entry>
<title>End-of-Month Invoice Date</title>
<link href="https://changelog.nilear.com/2026/end-of-month-invoice-date/"/>
<id>https://changelog.nilear.com/2026/end-of-month-invoice-date/</id>
<published>2026-04-23T00:00:00Z</published>
<updated>2026-04-23T00:00:00Z</updated>
<category term="ConnectActive"/>
<summary>A new End-of-Month Invoice Date setting has been added to ConnectActive&apos;s Prorating settings.</summary>
<content type="html">&lt;p&gt;A new &lt;strong&gt;End-of-Month Invoice Date&lt;/strong&gt; setting has been added to ConnectActive&amp;#39;s Prorating settings. When enabled, ConnectActive will use the final day of the Agreement&amp;#39;s Next Invoice Date month as the invoice date, rather than the first day of the month. This is recommended for agreements billed in arrears.&lt;/p&gt;
&lt;p&gt;For example, if an Agreement&amp;#39;s Next Invoice Date is &lt;strong&gt;April 1&lt;/strong&gt; and you invoice in &lt;strong&gt;May&lt;/strong&gt; for &lt;strong&gt;April&lt;/strong&gt;, ConnectActive will use &lt;strong&gt;April 30&lt;/strong&gt; as the invoice date instead. This setting can be found under ConnectActive -&amp;gt; Prorating tab.&lt;/p&gt;</content>
</entry>
<entry>
<title>Create Ticket Goals with AI</title>
<link href="https://changelog.nilear.com/2026/create-ticket-goals-with-ai/"/>
<id>https://changelog.nilear.com/2026/create-ticket-goals-with-ai/</id>
<published>2026-04-13T00:00:00Z</published>
<updated>2026-04-13T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>AI identifies every request in a ticket and turns them into ticket tasks.</summary>
<content type="html">&lt;div class=&quot;polish-email-title polish-email-title--goals&quot; aria-label=&quot;Create Ticket Goals with AI&quot;&gt;&lt;div class=&quot;polish-email-title__icon&quot;&gt;&lt;i class=&quot;fa-solid fa-list-check base-icon&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-1&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-2&quot;&gt;&lt;/i&gt;&lt;/div&gt;&lt;div class=&quot;polish-email-title__content&quot;&gt;&lt;div class=&quot;polish-email-title__eyebrow d-none&quot;&gt;New Feature&lt;/div&gt;&lt;div class=&quot;polish-email-title__headline-wrap&quot;&gt;&lt;div class=&quot;polish-email-title__ghost&quot;&gt;create ticket goals with ai&lt;/div&gt;&lt;h2 class=&quot;polish-email-title__headline&quot;&gt;&lt;span class=&quot;word&quot;&gt;Create&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;Ticket&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;Goals&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;with&lt;/span&gt; &lt;span class=&quot;word ai&quot;&gt;AI&lt;/span&gt;&lt;/h2&gt;&lt;span class=&quot;shimmer&quot;&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;p&gt;Introducing &lt;strong&gt;AI-Powered Ticket Goals&lt;/strong&gt; – automatically identify every request in a ticket and convert them into discrete ticket tasks, giving your technicians a clear, structured to-do list of exactly what the customer asked for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Request Detection&lt;/strong&gt;: AI reads the ticket summary and full conversation to identify all distinct, unresolved requests made by the customer&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Goal-Oriented Tasks&lt;/strong&gt;: Each request is converted into a focused ticket task that represents a concrete deliverable — not a troubleshooting step&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clear Accountability&lt;/strong&gt;: Goals are created as ticket tasks so every technician working the ticket knows exactly what work is expected and what still needs to be done&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Completion Gate&lt;/strong&gt;: Because goals are ticket tasks, all requested work must be completed before the ticket can be successfully moved to resolved&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Full Review&lt;/strong&gt;: Preview every suggested goal before anything is created — edit the text of any task or exclude individual goals you don&amp;#39;t want&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resolved Work Excluded&lt;/strong&gt;: AI only surfaces unresolved requests — work already confirmed as completed in the conversation is automatically omitted&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Available from the Working Notes view and the Ticket Tasks tab. Click the &lt;i class=&quot;far fa-sparkles&quot;&gt;&lt;/i&gt; button and select &lt;strong&gt;Create Ticket Goals&lt;/strong&gt; to get started:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/TicketGoals.png&quot; alt=&quot;Working notes toolbar showing the AI dropdown with Create Ticket Goals option&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;div class=&quot;alert alert-info mb-0&quot;&gt;&lt;strong&gt;Privacy &amp;amp; Security:&lt;/strong&gt; The AI processes the ticket summary and conversation to identify requested work. Each request is stateless, and your data is not used to train AI models.&lt;/div&gt;</content>
</entry>
<entry>
<title>Split Ticket with AI</title>
<link href="https://changelog.nilear.com/2026/split-ticket-with-ai/"/>
<id>https://changelog.nilear.com/2026/split-ticket-with-ai/</id>
<published>2026-04-03T00:00:00Z</published>
<updated>2026-04-03T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>AI splits a ticket with several unrelated requests into separate, focused tickets.</summary>
<content type="html">&lt;div class=&quot;polish-email-title polish-email-title--split&quot; aria-label=&quot;Split Ticket with AI&quot;&gt;&lt;div class=&quot;polish-email-title__icon&quot;&gt;&lt;i class=&quot;fa-solid fa-scissors base-icon&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-1&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-2&quot;&gt;&lt;/i&gt;&lt;/div&gt;&lt;div class=&quot;polish-email-title__content&quot;&gt;&lt;div class=&quot;polish-email-title__eyebrow d-none&quot;&gt;New Feature&lt;/div&gt;&lt;div class=&quot;polish-email-title__headline-wrap&quot;&gt;&lt;div class=&quot;polish-email-title__ghost&quot;&gt;split ticket with ai&lt;/div&gt;&lt;h2 class=&quot;polish-email-title__headline&quot;&gt;&lt;span class=&quot;word&quot;&gt;Split&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;Ticket&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;with&lt;/span&gt; &lt;span class=&quot;word ai&quot;&gt;AI&lt;/span&gt;&lt;/h2&gt;&lt;span class=&quot;shimmer&quot;&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;p&gt;Introducing &lt;strong&gt;AI-Powered Ticket Splitting&lt;/strong&gt; – when a single ticket contains multiple unrelated requests, let AI automatically break it into separate, focused tickets so each issue gets the attention it deserves:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Intelligent Detection&lt;/strong&gt;: AI analyzes the ticket conversation and identifies distinct requests that should be tracked separately&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Summary Refinement&lt;/strong&gt;: When the original summary no longer fits the remaining work, AI suggests an updated summary for the existing ticket&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Full Review&lt;/strong&gt;: Preview every new ticket — summary, initial description, and work already performed — before anything is created&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Inline Editing&lt;/strong&gt;: Edit any field in the review directly to adjust AI suggestions to your liking&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Selective Splitting&lt;/strong&gt;: Ignore individual suggested tickets you don&amp;#39;t want to create&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bulk TSI Assignment&lt;/strong&gt;: Assign Type, SubType, and Item across all new tickets in one click using AI suggestions&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AI Summary Note&lt;/strong&gt;: After tickets are created, AI drafts a summary of what was split off and what remains — save it as a note on the original ticket or use it to draft a client email, directly from the success screen&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Available from the ticket toolbar. Click the &lt;i class=&quot;far fa-scissors&quot;&gt;&lt;/i&gt; &lt;strong&gt;Split&lt;/strong&gt; &lt;i class=&quot;fa-regular fa-sparkles&quot;&gt;&lt;/i&gt; button to get started:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/SplitTicket.png&quot; alt=&quot;Ticket toolbar showing the Split button&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;div class=&quot;mt-3 fw-bold small text-uppercase text-muted&quot;&gt;&lt;i class=&quot;fas fa-copy me-1&quot;&gt;&lt;/i&gt; Step 1 — Review the AI-Suggested Split&lt;/div&gt;&lt;p&gt;After clicking Split, the AI analyses the ticket conversation and presents a &lt;strong&gt;Split Ticket Review&lt;/strong&gt; showing the suggested summary for the existing ticket and each new ticket to be created. You can edit any field or ignore tickets you don&amp;#39;t need:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/SplitTicketReview.png&quot; alt=&quot;Split Ticket Review modal&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;div class=&quot;mt-3 fw-bold small text-uppercase text-muted&quot;&gt;&lt;i class=&quot;fas fa-sliders me-1&quot;&gt;&lt;/i&gt; Step 2 — Assign Ticket Properties&lt;/div&gt;&lt;p&gt;Walk through each new ticket to assign its properties — board, status, contact, site, and more. Use &lt;strong&gt;Suggest TSI (All Tickets)&lt;/strong&gt; to let AI classify the Type, SubType, and Item for every new ticket simultaneously:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/SplitTicketProperties.png&quot; alt=&quot;Assign Ticket Properties step modal&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;div class=&quot;mt-3 fw-bold small text-uppercase text-muted&quot;&gt;&lt;i class=&quot;fas fa-check-circle me-1&quot;&gt;&lt;/i&gt;&lt;i class=&quot;fa-regular fa-sparkles me-1&quot;&gt;&lt;/i&gt; Step 3 — Tickets Created &amp;amp; AI Summary Note&lt;/div&gt;&lt;p&gt;Once committed, all new tickets are created in ConnectWise. The success screen lists every ticket created — open any one directly with a click. At the same time, AI drafts an &lt;strong&gt;AI Summary Note&lt;/strong&gt; for the original ticket, capturing what work was moved to new tickets and what remains. Save it as a note on the ticket or use it to draft a client email — without leaving the screen:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/SplitTicketSuccess.png&quot; alt=&quot;Tickets Created success modal with AI Summary Note&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;div class=&quot;alert alert-info&quot;&gt;&lt;strong&gt;Not the same as Unbundle&lt;/strong&gt;: ConnectWise&apos;s Unbundle feature detaches child tickets from a parent. Split Ticket is different — it creates brand-new standalone tickets from the conversation in a single ticket.&lt;/div&gt;&lt;div class=&quot;alert alert-info mb-0&quot;&gt;&lt;strong&gt;Privacy &amp;amp; Security:&lt;/strong&gt; The AI processes the ticket summary and the full ticket conversation to generate the split. Each request is stateless, and your data is not used to train AI models.&lt;/div&gt;</content>
</entry>
<entry>
<title>Polish Notes with AI</title>
<link href="https://changelog.nilear.com/2026/polish-notes-with-ai/"/>
<id>https://changelog.nilear.com/2026/polish-notes-with-ai/</id>
<published>2026-04-02T00:00:00Z</published>
<updated>2026-04-02T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Introducing AI-Powered Notes Polishing – refine your working notes into clear, well-structured entries in seconds.</summary>
<content type="html">&lt;div class=&quot;polish-email-title polish-email-title--notes&quot; aria-label=&quot;Polish Notes with AI&quot;&gt;&lt;div class=&quot;polish-email-title__icon&quot;&gt;&lt;i class=&quot;fa-solid fa-file-pen base-icon&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-1&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-2&quot;&gt;&lt;/i&gt;&lt;/div&gt;&lt;div class=&quot;polish-email-title__content&quot;&gt;&lt;div class=&quot;polish-email-title__eyebrow d-none&quot;&gt;New Feature&lt;/div&gt;&lt;div class=&quot;polish-email-title__headline-wrap&quot;&gt;&lt;div class=&quot;polish-email-title__ghost&quot;&gt;polish notes with ai&lt;/div&gt;&lt;h2 class=&quot;polish-email-title__headline&quot;&gt;&lt;span class=&quot;word&quot;&gt;Polish&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;Notes&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;with&lt;/span&gt; &lt;span class=&quot;word ai&quot;&gt;AI&lt;/span&gt;&lt;/h2&gt;&lt;span class=&quot;shimmer&quot;&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;p&gt;Introducing &lt;strong&gt;AI-Powered Notes Polishing&lt;/strong&gt; – refine your working notes into clear, well-structured entries in seconds. The AI polishes all of your notes at once and presents a side-by-side review so you stay in full control:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Batch Polish&lt;/strong&gt;: All working notes are polished in a single click — no need to process them one at a time&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Side-by-Side Review&lt;/strong&gt;: Compare the original and polished version of each note before committing&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Per-Note Control&lt;/strong&gt;: Accept or keep the original for each note individually&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Inline Editing&lt;/strong&gt;: Further tweak either version directly in the review dialog before saving&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bolding Toggle&lt;/strong&gt;: Optionally strip markdown bold formatting from polished notes&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Available from the working notes toolbar. Simply click the &lt;i class=&quot;far fa-sparkles&quot;&gt;&lt;/i&gt; button to polish all notes:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/PolishNotes.png&quot; alt=&quot;Polish Notes with AI&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;div class=&quot;alert alert-info mb-0&quot;&gt;&lt;strong&gt;Privacy &amp;amp; Security:&lt;/strong&gt; The AI processes your working note text and does not access other ticket data. Each request is stateless, and your data is not used to train AI models.&lt;/div&gt;</content>
</entry>
<entry>
<title>Suggest TSI with AI</title>
<link href="https://changelog.nilear.com/2026/suggest-tsi-with-ai/"/>
<id>https://changelog.nilear.com/2026/suggest-tsi-with-ai/</id>
<published>2026-04-02T00:00:00Z</published>
<updated>2026-04-02T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>AI suggests the Service Type, SubType and Item for a ticket.</summary>
<content type="html">&lt;div class=&quot;polish-email-title polish-email-title--tsi&quot; aria-label=&quot;Suggest TSI with AI&quot;&gt;&lt;div class=&quot;polish-email-title__icon&quot;&gt;&lt;i class=&quot;fa-solid fa-sitemap base-icon&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-1&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-2&quot;&gt;&lt;/i&gt;&lt;/div&gt;&lt;div class=&quot;polish-email-title__content&quot;&gt;&lt;div class=&quot;polish-email-title__eyebrow d-none&quot;&gt;New Feature&lt;/div&gt;&lt;div class=&quot;polish-email-title__headline-wrap&quot;&gt;&lt;div class=&quot;polish-email-title__ghost&quot;&gt;suggest tsi with ai&lt;/div&gt;&lt;h2 class=&quot;polish-email-title__headline&quot;&gt;&lt;span class=&quot;word&quot;&gt;Suggest&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;TSI&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;with&lt;/span&gt; &lt;span class=&quot;word ai&quot;&gt;AI&lt;/span&gt;&lt;/h2&gt;&lt;span class=&quot;shimmer&quot;&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;p&gt;Introducing &lt;strong&gt;AI-Powered TSI Suggestions&lt;/strong&gt; – let AI analyze your ticket and automatically suggest the most appropriate &lt;strong&gt;Service Type, SubType, and Item&lt;/strong&gt; so you can classify tickets faster and more consistently:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One-Click Suggestion&lt;/strong&gt;: Click the sparkle button in the TSI form to instantly generate a classification suggestion&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Context-Aware&lt;/strong&gt;: The AI reads the ticket content to recommend the best-fitting Type, SubType, and Item combination&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Visual Feedback&lt;/strong&gt;: Badges highlight exactly which fields were updated so you can review the changes at a glance&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Full Control&lt;/strong&gt;: Review the suggested values and adjust any field before saving&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Available from the TSI (Service Type, SubType &amp;amp; Item) form when working on a single ticket:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/SuggestTSI.png&quot; alt=&quot;Suggest TSI with AI&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;div class=&quot;alert alert-info mb-0&quot;&gt;&lt;strong&gt;Privacy &amp;amp; Security:&lt;/strong&gt; The AI processes the ticket summary and a subset of the ticket conversation to generate suggestions. Each request is stateless, and your data is not used to train AI models.&lt;/div&gt;</content>
</entry>
<entry>
<title>Polish Summary with AI</title>
<link href="https://changelog.nilear.com/2026/polish-summary-with-ai/"/>
<id>https://changelog.nilear.com/2026/polish-summary-with-ai/</id>
<published>2026-04-01T00:00:00Z</published>
<updated>2026-04-01T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Introducing AI-Powered Summary Polishing – instantly generate clear, concise ticket titles from your current summary.</summary>
<content type="html">&lt;div class=&quot;polish-email-title polish-email-title--summary&quot; aria-label=&quot;Polish Ticket Summary with AI&quot;&gt;&lt;div class=&quot;polish-email-title__icon&quot;&gt;&lt;i class=&quot;fa-solid fa-regular fa-lightbulb base-icon&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-1&quot;&gt;&lt;/i&gt; &lt;i class=&quot;fa-solid fa-sparkles sparkle sparkle-2&quot;&gt;&lt;/i&gt;&lt;/div&gt;&lt;div class=&quot;polish-email-title__content&quot;&gt;&lt;div class=&quot;polish-email-title__eyebrow d-none&quot;&gt;New Feature&lt;/div&gt;&lt;div class=&quot;polish-email-title__headline-wrap&quot;&gt;&lt;div class=&quot;polish-email-title__ghost&quot;&gt;polish ticket summary with ai&lt;/div&gt;&lt;h2 class=&quot;polish-email-title__headline&quot;&gt;&lt;span class=&quot;word&quot;&gt;Polish&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;Ticket&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;Summary&lt;/span&gt; &lt;span class=&quot;word&quot;&gt;with&lt;/span&gt; &lt;span class=&quot;word ai&quot;&gt;AI&lt;/span&gt;&lt;/h2&gt;&lt;span class=&quot;shimmer&quot;&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;p&gt;Introducing &lt;strong&gt;AI-Powered Summary Polishing&lt;/strong&gt; – instantly generate clear, concise ticket titles from your current summary. This feature presents you with multiple AI-suggested options so you can pick the best fit:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One-Click Polish&lt;/strong&gt;: Click the sparkle button next to the summary field to generate suggestions&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Multiple Options&lt;/strong&gt;: The AI presents several suggested summaries to choose from, ranked by quality&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Full Control&lt;/strong&gt;: Select the option you prefer or cancel to keep your original&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Available directly from the ticket summary field. Simply click the &lt;i class=&quot;far fa-sparkles&quot;&gt;&lt;/i&gt; button to get started:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/PolishSummary.png&quot; alt=&quot;Polish Summary with AI&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;
&lt;div class=&quot;alert alert-info mb-0&quot;&gt;&lt;strong&gt;Privacy &amp;amp; Security:&lt;/strong&gt; The AI processes the ticket summary and a subset of the ticket conversation to provide context-aware suggestions. Each request is stateless, and your data is not used to train AI models.&lt;/div&gt;</content>
</entry>
<entry>
<title>AI Feature Controls</title>
<link href="https://changelog.nilear.com/2026/ai-feature-controls/"/>
<id>https://changelog.nilear.com/2026/ai-feature-controls/</id>
<published>2026-04-01T00:00:00Z</published>
<updated>2026-04-01T00:00:00Z</updated>
<category term="MTX: Tickets"/>
<summary>Administrators can now enable or disable each AI feature independently. These settings are available under Nilear -&gt; Settings -&gt; My Tickets -&gt; AI Features.</summary>
<content type="html">&lt;p&gt;Administrators can now enable or disable each AI feature independently. These settings are available under Nilear -&amp;gt; Settings -&amp;gt; My Tickets -&amp;gt; AI Features.&lt;/p&gt;</content>
</entry>
<entry>
<title>Finer Control over Availability Listing</title>
<link href="https://changelog.nilear.com/2026/finer-control-over-availability-listing/"/>
<id>https://changelog.nilear.com/2026/finer-control-over-availability-listing/</id>
<published>2026-03-28T00:00:00Z</published>
<updated>2026-03-28T00:00:00Z</updated>
<category term="MTX: Availability"/>
<summary>For individual users, you can control whether they can view all users or only themselves, and whether they can update other users’ availability status or only their own.</summary>
<content type="html">&lt;p&gt;For individual users, you can control whether they can view all users or only themselves, and whether they can update other users’ availability status or only their own. This settings is available under Nilear -&amp;gt; Settings -&amp;gt; Member Management -&amp;gt; Module Rights&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://media.nilear.com/changelog/AvailabilityControl.png&quot; alt=&quot;Finer Control over Availability Listing&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot;&gt;&lt;/p&gt;</content>
</entry>
</feed>
