Caisey Blog

Dispatchers · June 30, 2026

Caisey for Help Desk: Reducing Mean Time to Resolution with Pre-Approved Actions for Common Fixes

Learn how Caisey's pre-approved action templates let help desk dispatchers speed up common fixes like restarting services or clearing caches, while maintaining full audit logs and control.
help deskMTTRpre-approved actionsremote troubleshootingapproval workflowMSP

Every help desk dispatcher knows the frustration: a technician spots a simple fix—restart the print spooler, clear a temp folder, reset a network adapter—but has to wait for approval before executing. That delay adds minutes, sometimes hours, to resolution time. Multiply that across dozens of tickets, and mean time to resolution (MTTR) climbs, SLAs slip, and end users get restless.

Caisey offers a different approach: pre-approved action templates that let technicians execute common fixes immediately, without waiting for a dispatcher or manager to green-light each individual request. The approval gate is still there—it just moves from "per-action" to "per-policy." The result? Faster resolutions, lower MTTR, and happier customers.

The Problem: Every Action Needs a Nod

In most remote support tools, every remote action—whether it's running a script, restarting a service, or changing a setting—requires explicit approval. This is by design: security demands that someone with authority confirms the action before it touches a live endpoint. But the reality is that many fixes are routine. A technician who has seen the "print spooler stopped" error a hundred times doesn't need a fresh approval every time.

Without pre-approval, the workflow looks like this:

  1. Technician diagnoses the issue.
  2. Technician requests approval for a specific action.
  3. Dispatcher reviews the request (often interrupting their own work).
  4. Dispatcher approves.
  5. Technician executes.

Even if the dispatcher responds in 30 seconds, the cumulative delay across a day's tickets is significant. And if the dispatcher is busy or away, the ticket stalls.

Caisey's Solution: Pre-Approved Action Templates

Caisey flips the model. Instead of approving each action, dispatchers define pre-approved action templates—sets of common fixes that technicians can run without additional approval. These templates are configured per client, per group, or globally, giving you granular control without sacrificing speed.

A pre-approved action template is simply a saved command or script that Caisey knows is safe and routine. When a technician connects to an endpoint and sees the print spooler is down, they can select the "Restart Print Spooler" template from a menu, click execute, and the action runs immediately. No pop-up, no waiting, no interruption.

Because Caisey runs on enrolled endpoints with a persistent agent, the template execution is fast and reliable. The technician doesn't need to type commands or navigate menus—they just pick the fix and go.

Practical Example: Restart Print Spooler

Let's walk through a real scenario. A user calls in because they can't print. The technician connects via Caisey's remote troubleshooting console and quickly identifies that the Print Spooler service has stopped.

With a traditional tool, the technician would need to request approval to restart the service. They'd type a message, wait for a dispatcher to see it, wait for approval, and then run the command. Total elapsed time: 2–5 minutes for a 10-second fix.

With Caisey, the dispatcher has already created a pre-approved action template called "Restart Print Spooler." The technician selects it from a dropdown, clicks "Execute," and the service restarts in seconds. The ticket is resolved in under a minute. The technician moves on to the next call.

This isn't just faster—it's also more consistent. The template ensures the exact same command is used every time, reducing the risk of typos or variations that could cause side effects.

Audit Trails: Still Fully Logged

One concern with pre-approval is losing visibility. If actions run without explicit per-action approval, how do you track what happened? Caisey solves this by logging every execution in the session history and audit trail. Even though the action was pre-approved, the system records:

  • Which technician executed the action
  • Which endpoint it ran on
  • The exact command or script used
  • The timestamp
  • The outcome (success/failure)

This means dispatchers and managers can review all actions after the fact. The IT support audit trail remains complete and searchable. Pre-approval doesn't mean no oversight—it means smarter oversight.

Workflow: How Dispatchers Configure Policies

Setting up pre-approved actions is straightforward. In the Caisey dashboard, dispatchers navigate to the permissions and settings area for a client or group. They can create new action templates by specifying:

  • Name: e.g., "Clear DNS Cache"
  • Command: ipconfig /flushdns
  • Scope: Which endpoints or groups this applies to
  • Approval mode: Pre-approved (no additional approval needed) or approval required (default)

Once saved, the template appears in the technician's action menu for any endpoint in that scope. Dispatchers can also set expiration dates or require re-approval after a certain number of uses, adding another layer of control.

For more complex scenarios, Caisey's approval-based remote support still allows you to require per-action approval for sensitive operations like registry edits or user account changes. The system is flexible: you decide which actions are routine and which need a human check.

Comparison to ScreenConnect

ScreenConnect (now ConnectWise Control) is a popular remote support tool, but it lacks a built-in pre-approval mechanism for actions. In ScreenConnect, every command or script execution typically requires the technician to have elevated permissions or to request approval through a separate system. There's no concept of "this action is safe, run it without asking."

Caisey's approach is different because it treats approval as a configurable gate, not a binary on/off switch. You can set different policies for different clients, groups, or even individual endpoints. This granularity is especially valuable for MSPs who manage a mix of environments—some clients may trust routine fixes, while others require strict oversight.

Additionally, Caisey's action templates are tied to the endpoint's enrolled agent, not just a live session. This means the templates are available even if the technician reconnects later, and they're consistent across sessions.

Reducing MTTR Across the Board

Pre-approved actions directly reduce MTTR by eliminating the approval wait for common fixes. But the benefits go beyond speed:

  • Technician productivity: Less time waiting means more tickets closed per shift.
  • Dispatcher focus: Dispatchers can concentrate on complex issues instead of approving routine restarts.
  • User satisfaction: Faster fixes mean fewer frustrated end users.
  • Consistency: Standardized templates reduce errors and ensure best practices.

For help desks that handle high volumes of repetitive issues—password resets, service restarts, cache clears—pre-approved actions can shave minutes off every ticket. Over a month, that adds up to hours of saved time.

Getting Started

If you're a dispatcher looking to streamline your help desk, start by identifying the top five most common fixes your technicians perform. Create pre-approved action templates for each one in Caisey. Then monitor the impact on MTTR over the next week. You'll likely see a noticeable drop.

Caisey's remote endpoint diagnostics also help you identify recurring issues, so you can build templates for problems you haven't even seen yet. The combination of proactive diagnostics and pre-approved actions creates a powerful feedback loop for continuous improvement.

Pre-approval isn't about cutting corners—it's about removing unnecessary friction from routine work. With Caisey, you keep the security you need and gain the speed your help desk deserves.

Caisey
loading...