Nanoheal is included in the 2026 Gartner® Magic Quadrant™ for Digital Employee Experience Management Tools.In the 2026 Gartner® Magic Quadrant™ for DEX tools. See it on Gartner ↗

NanohealNanoheal

Popular

↑↓ to moveEnter to open/ to search from any page

 Schedule a demo
Automate Issues

Fix a problem once. Nanoheal runs that fix every time it comes back.

Scripting a fix usually takes weeks, so most problems never get one. A laptop that is filling up will soon stop saving work. The device reports it, and the approved fix runs on it before anyone notices. You choose who acts: nobody, the employee, the service desk or the calendar.

Schedule a demo See the four delivery modes
Endpoint · LT-3318 · live
  1. 00.00 Free space on C: falls below 10%
  2. 00.04 Matched to a library entry: disk-space-reclaim
  3. 00.20 Checked: user files untouched, no install running
  4. 00.70 Actions run: clear temp folder · purge update cache · empty recycle bin
  5. 04.10 C: back to 31% free. Ticket never raised.
Ticket avoided

What normally happens

Files stop saving, so someone calls the desk.

The laptop runs out of disk space halfway through the afternoon. A technician connects and clears temp files by hand. Next week the same thing happens on another hundred machines.

Service desk · new ticket “Laptop won’t save files” LT-3318 · raised by the employeeWaiting for a technician

What Nanoheal does

The fix runs before the disk fills, every time.

Free space dropping below 10% starts the fix. It clears the temp files, checks the space came back and logs the run, and nobody calls. When the next hundred laptops fill up, the same fix runs on each of them, and nobody has to write it again.

Nanoheal · run log disk-space-reclaim · LT-3318 C: 10% → 31% free · 4.1 s · no ticketSuccess
What a fix is

Each fix says what to do. The agent already knows how.

Every fix has the same four parts: when it starts, what it checks, what it changes and how it proves the problem cleared.

  1. 01 · When

    The trigger. A service stops, an event is logged, a threshold is crossed or latency climbs.

  2. 02 · Check

    The facts. Is the service really down, is there enough disk, is the application installed?

  3. 03 · Act

    The repair. Steps call the agent’s built-in actions on files, registry, services, settings, software and network.

  4. 04 · Verify

    The proof. A final check that the condition cleared. If it didn’t hold, a person gets the case with the evidence attached.

Library entry · disk-space-reclaim Run · LT-3318
  1. 00.00

    C: below 10% free

    The threshold set in the entry is crossed

    Measured by the agent

  2. 00.20
    • Free space6%
    • Temp and update cache14 GB
    • User filesuntouched
  3. 00.70
    1. clear temp folder
    2. purge update cache
    3. empty recycle bin

    Built-in actions · nothing installed

  4. 04.10

    C: at 31% free

    Condition cleared. Ticket never raised.

    Logged as success · or handed to a person

Resolution is triggered by the condition the OS reports: an event, a stopped service or a threshold like this one. Laid out in the automation builder, so the approver reads steps, not PowerShell.

The agent works from a fixed set of signed actions, so a new fix is a set of parameters for actions the agent already has. A person approves it, and it is staged and versioned before it runs anywhere, with every run logged. How governance works.

From the libraryThe whole library

Fixes

Stopped services, application crashes and hangs, print faults, disk pressure, network and driver repair.

Starts on a problem the device reports.

  1. Print spooler recovery
  2. Outlook profile repair
  3. Teams cache clear
  4. VPN adapter reset
  5. Disk space reclaim
  6. Wi-Fi profile reset
  7. Stopped service restart
  8. Application hang recovery
  9. Driver rollback
  10. Browser cache cleanup
Delivery

You choose who runs each fix.

One approved fix runs four ways. Set the mode per device group, and move it along as the fix earns trust. The same nearly full disk on LT-3318, four ways:

  1. 1Start here

    The service desk

    Assisted IT

    A technician runs the fix from the ticket, on one device, a group or a site.

    Use it when a person should judge the situation first.

  2. 2Once it has proved itself

    The employee

    Self-service

    The fix is offered on the device. One click runs it, when it suits them.

    Use it when the fix interrupts work, like a restart.

    Employee self-service

  3. 3When no judgement is needed

    Nobody

    Autoheal

    The fix runs on its own the moment the device reports the problem.

    Use it when it is safe to run unannounced.

  4. Or, for housekeeping

    The calendar

    Scheduled

    The fix runs off-peak, on the cadence you set.

    Use it when the work is routine, like a weekly purge.

13

Conditions an automation can check on the device before it acts.

CPU, memory, free disk, service status, whether a process responds, network latency, and whether a file, folder, process, app or registry key is there. A fix moves up the ladder only when your team has seen it hold.

Where fixes run

One fix runs wherever it makes sense.

One agent on every device. A fix runs where it makes sense, on the device, from the service desk or on a schedule, and a person is in the loop exactly where judgement is needed and nowhere else.

Where fixes runOne fix, five places

Ask any vendor about automated fixes

How many fixes run on day one?
1,200+ tested automations, from the automation library.
Who writes the next one, and who maintains it?
Your team, in the visual automation builder. It is settings for actions the agent already has, so there is no script to maintain.
Can the employee or the desk run the same fix?
Yes. One approved fix runs on its own, is offered to the employee or is run by the desk, set per device group.
Who approves a fix, and where is each run recorded?
An approver signs it off before it runs, publishing is staged and versioned, and every run is logged as success, failed or pending, per device.
How do you know it worked?
Each run checks that the problem cleared, and the experience score shows whether people noticed.
Read next