MSP owners and operations managers · August 13, 2026
Build a Repeatable Troubleshooting Playbook in Caisey: From Manual Steps to Preset Commands
Every MSP knows the pain: a technician spends 20 minutes manually checking disk health, startup entries, and event logs on a slow machine. Another tech handles the same issue differently, missing a step, and the ticket drags on. The fix isn't a better script – it's a better way to package and reuse the steps you already know work. Caisey's command presets let you codify your best troubleshooting sequences and run them on any enrolled device with one click, while the audit trail records exactly what happened for later review.
In this post, I'll walk through how to build a repeatable troubleshooting playbook in Caisey, using a real-world example of a malware check. You'll see how presets reduce variance, speed up support, and make your team's knowledge a shared asset.
Why a Playbook Matters More Than a Script
A script is a static file that runs the same commands every time. A playbook is a living set of steps that your team can refine, version, and apply contextually. When you rely on individual memory, you get inconsistent results. When you rely on a playbook, you get:
- Consistency: Every technician follows the same proven path, no matter their experience level.
- Speed: No more hunting for the right command or re-typing the same flags.
- Accountability: The audit trail shows which steps ran, when, and on which device.
- Knowledge capture: When a tech discovers a new diagnostic trick, it can be added to the preset and shared with the whole team.
Caisey is built for this. It's not just a remote shell – it's a coordination layer that keeps session history, approvals, and results in one place. That makes it the perfect home for your playbook.
Creating a Preset in Caisey
Presets are stored in your Caisey workspace, so they're available on any enrolled endpoint. Here's the basic workflow:
- Open the preset editor from your Caisey dashboard.
- Define the sequence of commands you want to run. Each step can be a PowerShell, Bash, or Python snippet, depending on the target OS.
- Set the execution order – Caisey runs them sequentially, stopping if a step fails (you can configure that).
- Add a description so your team knows what the preset does and when to use it.
- Save and assign a version – every change creates a new version, so you can track what's changed.
You can also set permission prompts for sensitive presets. For example, if a preset includes a command that modifies system settings, Caisey will ask the end user for approval before running it. This keeps your support process compliant with your clients' expectations.
Example: A Standard Malware Check Preset
Let's build a preset that any technician can run when a user reports a suspicious pop-up or slow performance. This is a common scenario, and having a preset saves time and ensures nothing is missed.
Here's what the preset might do:
- Step 1: List startup entries to spot suspicious auto-run programs.
- Step 2: Check running processes for known malware names (or just dump the list for later analysis).
- Step 3: Review recent event logs for errors or security warnings.
- Step 4: Run a quick disk health check to rule out hardware issues.
In Caisey, you'd write each step as a command. For a Windows endpoint, it might look like this:
# Step 1: Startup entries
Get-CimInstance Win32_StartupCommand | Select-Object Name, Command, Location
# Step 2: Running processes
Get-Process | Where-Object {$_.Path -like '*temp*'} | Select-Object Name, Path
# Step 3: Event logs
Get-WinEvent -FilterHashtable @{LogName='System'; Level=2; StartTime=(Get-Date).AddDays(-1)} | Select-Object TimeCreated, Message
# Step 4: Disk health
Get-PhysicalDisk | Select-Object DeviceId, HealthStatus, MediaTypeYou don't have to write these from scratch – your senior techs probably already have them in their notes. The point is to put them in a preset so everyone uses the same set.
Once saved, you can run this preset on any enrolled device from the Caisey console. The output is captured in the session log, and you can even share a public transcript with the client if you need to show what was checked.
Sharing and Versioning Presets Across the Team
A preset is only useful if your team actually uses it. Caisey makes sharing straightforward:
- Workspace-level presets are visible to everyone in your organization.
- You can assign permissions – some presets might be read-only for junior techs, while senior techs can edit them.
- Version history lets you see when a preset changed and who changed it. If a new step causes issues, you can roll back to a previous version.
This turns your playbook into a living document. When a technician finds a better command, they can propose an update. After a review, it becomes the new standard – and the old version stays in history for reference.
Documentation Tips for Your Playbook
Presets are great, but they're not a substitute for good documentation. Here are a few practices that work well:
- Write a clear description for each preset: what it does, when to use it, and any prerequisites.
- Use comments in the commands – even if they're just for your team, they help future readers understand the intent.
- Link presets to your ticketing system – if a preset resolves a common issue, note that in your documentation so techs know to run it first.
- Review presets quarterly – software changes, and so do threats. Make sure your playbook stays current.
Caisey's audit trail helps here too. You can see which presets are actually being used and which are collecting dust. That data tells you where to invest your documentation efforts.
Putting It All Together
A repeatable troubleshooting playbook isn't about locking everyone into a rigid process. It's about giving your team a reliable starting point so they can spend their energy on the unusual cases. With Caisey, you can turn your best manual steps into one-click presets, share them across the team, and keep a full record of every run.
Start small: pick one issue you handle every week and build a preset for it. Run it on a few devices, refine it, and then share it. You'll notice the difference immediately – fewer missed steps, faster resolutions, and happier clients.
If you're new to Caisey, check out our remote troubleshooting overview to see how the platform fits into your workflow. And if you're already using Caisey, explore how presets can complement your existing MSP remote support processes.
Your team's knowledge is your biggest asset. Put it in a playbook, and let Caisey make it repeatable.