RemediateDesk in short videos

Short screen recordings of the real product doing real jobs: installing the agent, working a ticket, approving a step and undoing one. Every video has the steps written out beneath it.

All of these are on our YouTube channel. The recordings were made on test machines, not customer machines.

Start here

  • Getting startedReal run

    A real first run: add a company, install the agent, ask the machine about itself

    A real first run: add a company, install the agent, ask the machine about itself. 2:51
    Transcript
    1. Sign in to the app on a test environment, using a code from an authenticator app.
    2. Add a company. Its install page shows an install command that already contains the company's key, which is masked in the recording.
    3. Run the command as Administrator on the Windows machine. Waiting while it installs is sped up, with a real clock on screen.
    4. The agent checks in by itself and the machine appears online, with its operating system, last check-in and agent version.
    5. Ask the machine about itself. This machine uses the default approval mode, so every command waits for a technician.
    6. The technician reviews the read-only commands and approves them. The real output comes back and the AI summarises it.

    Create a company, run the install command on a Windows test machine, watch it appear online by itself, and ask the AI about it, with every command waiting for a technician's approval.

Fixing problems

  • Fixing problemsReal run

    Broken DNS on a Windows test machine: a real AI run with approval clicks

    Broken DNS on a Windows test machine: a real AI run with approval clicks. 2:06
    Transcript
    1. Before recording, DNS on the test machine was pointed at a server that cannot be reached.
    2. The technician describes the problem in plain English and the AI investigates the machine.
    3. Each change is proposed on an approval card. Nothing runs until the technician reviews the exact commands and approves.
    4. After the fix, the machine is checked separately, outside the app, and name lookups work again.

    Websites stop loading because DNS points at an unreachable server, so the AI investigates, proposes a fix, waits for approval, and the result is checked from outside the app.

  • Fixing problemsReal run

    A stuck Print Spooler on a Windows test machine: a real AI run

    A stuck Print Spooler on a Windows test machine: a real AI run. 1:59
    Transcript
    1. Before recording, the Print Spooler service on the test machine was stopped and junk files were left in the spool folder.
    2. The technician says that printing is stuck, and the AI looks at the service, the queue and the printers.
    3. It proposes clearing the queue and starting the service. The technician reviews the exact commands and approves.
    4. The machine is checked separately, outside the app, and the Print Spooler service is running again.

    Printing is stuck, so the AI checks the service, the queue and the printers, proposes the recovery steps, and a technician approves them before anything runs.

Approvals and safety

  • Approvals and safetyReal run

    A restart after patching: the technician chooses when it happens (real AI run)

    A restart after patching: the technician chooses when it happens (real AI run). 1:47
    Transcript
    1. Before recording, the restart-required flag that Windows Update leaves after patching was set on the test machine.
    2. The technician asks the AI to take care of it. The AI checks whether a restart is pending and who is signed in, and asks when the restart should happen.
    3. The approval card lets the technician choose the time, and shows the exact time chosen. A restart asks for a further, deliberate click.
    4. Waiting for the restart is sped up with a real clock on screen. The machine comes back online and the pending restart is cleared.

    A restart is pending after patching, so the AI checks whether anyone is signed in and the approval card lets the technician choose when the machine restarts.

Ready to stop context-switching on printer tickets?

Start with 30 days free on up to 250 endpoints - no card required. Then $99/mo including 15 endpoints, $599/mo flat past 181, plus $2 for each ticket RemediateDesk actually resolves.

Get started