From Ticket to Closure: A Step-by-Step Caisey Workflow for Recurring Application Crashes

You've seen it a hundred times: a ticket comes in for an application crash. The user says "Outlook keeps closing unexpectedly." In the traditional remote support world, you'd connect via ScreenConnect, ask the user to reproduce the issue, poke around Event Viewer manually, try a few fixes, and then scribble notes into your PSA. The whole process is messy, undocumented, and hard to repeat.

With Caisey, that workflow becomes clean, auditable, and efficient. Every step is logged, every command is approved, and the entire session history is ready to attach to your ticket. Let's walk through a real-world scenario: a recurring Outlook crash caused by a faulty add-in.

The Problem: Recurring Outlook Crashes

Your MSP supports a mid-size law firm. One user, Sarah, has been complaining for weeks that Outlook crashes every time she tries to open a calendar invitation. Previous technicians tried reinstalling Office, clearing the cache, and even creating a new Outlook profile. Nothing stuck. The crashes keep coming back.

Sarah's ticket has been reopened three times. You need to get to the root cause and close it for good. Caisey gives you the tools to do that without guesswork.

Step 1: Ticket Arrives and Device Selection

The ticket lands in your PSA. You open Caisey's dashboard, find Sarah's enrolled device (a Windows 11 laptop), and click to connect. Because Caisey maintains persistent enrollment, you don't need to ask Sarah to download anything or share a code. The device is already there, ready for remote troubleshooting.

From the dashboard, you can see the device's last check-in time, OS version, and installed applications. You select the device and initiate a session.

Step 2: Remote Inspection via Event Logs

Instead of asking Sarah to open Event Viewer (and waiting while she searches for it), you use Caisey's runtime to pull the Application event logs directly. With a single command, you filter for Outlook-related errors from the last 24 hours.

Get-WinEvent -LogName Application | Where-Object { $_.ProviderName -like "*Outlook*" } | Select-Object TimeCreated, Id, Level, Message | Format-Table -AutoSize

Caisey executes this on Sarah's machine and returns the results in seconds. You spot multiple Event ID 1000 errors referencing outlook.exe and a module named AddinExpressOL.dll. That's your smoking gun.

This kind of remote endpoint diagnostics is far faster than walking a user through manual steps. And because Caisey records every command and output, you have a perfect audit trail.

Step 3: Identifying the Faulty Add-In

Now you know a DLL is involved. You dig deeper. You run a command to list all COM add-ins registered in Outlook:

Get-ChildItem "HKCU:\Software\Microsoft\Office\16.0\Outlook\Addins" | Get-ItemProperty

The output shows an add-in called "MeetingHelper" from a third-party vendor. The DLL path matches AddinExpressOL.dll. This add-in is likely crashing Outlook when calendar invitations are processed.

You've identified the root cause without ever touching Sarah's mouse. Caisey's headless runtime gives you full PowerShell access to the endpoint, even while the user continues working.

Step 4: Getting User Approval

Before you disable the add-in, you need Sarah's consent. Caisey's approval-based remote support model ensures that the user is always in control. You send an approval request to Sarah's screen:

"Caisey is requesting permission to disable the Outlook add-in 'MeetingHelper' to resolve recurring crashes. Do you approve?"

Sarah clicks "Approve" and Caisey logs the timestamp and her response. This isn't just polite—it's a compliance requirement for many MSPs. The approval becomes part of the session record.

Step 5: Disabling the Add-In and Verifying Fix

With approval granted, you disable the add-in. You could do it via PowerShell, but Caisey also supports running registry edits or even using a script. You run:

Set-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Outlook\Addins\MeetingHelper" -Name "LoadBehavior" -Value 2

This sets the add-in to load but not connect (effectively disabling it). You then ask Caisey to restart Outlook. The runtime launches Outlook, and you monitor the process exit codes. No crash.

To be thorough, you simulate opening a calendar invitation by running a quick test via Outlook's object model (or simply asking Sarah to try). Sarah confirms the invitation opens without issue. The fix is verified.

Step 6: Closing the Ticket with Full Session Record

You end the Caisey session. The entire interaction—commands, outputs, approvals, user confirmations—is saved as a transcript. You can generate a public, reviewed share link and attach it to the ticket in your PSA.

Your ticket notes become trivial: "Identified faulty add-in MeetingHelper via event log analysis. Disabled with user approval. Verified fix. See Caisey session transcript for full details."

Compare this to the old way: you'd have to manually type every step, remember the exact event IDs, and hope your notes are accurate. With Caisey, the audit trail is automatic and tamper-proof.

Why Caisey Beats Traditional Remote Support

Traditional tools like ScreenConnect require you to take control of the user's screen, ask them to navigate menus, and manually document everything. Caisey's headless runtime lets you work directly with the endpoint's internals without interrupting the user. Every action is logged, every approval is recorded, and the session record is ready for compliance or billing.

For recurring issues like application crashes, Caisey gives you a repeatable process. You can even save the diagnostic steps as a script for future use. And because Caisey maintains device history, you can see if the same add-in has caused problems on other machines.

Conclusion

From ticket to closure, Caisey transforms how MSPs handle recurring application crashes. You start with a device in your dashboard, inspect event logs remotely, identify the faulty component, get user approval, apply the fix, and close the ticket with a complete audit trail. No more guesswork, no more manual notes, no more reopened tickets.

The next time you see an Outlook crash ticket, you know exactly what to do. And Caisey will log every step along the way.