Caisey Blog

MSP Owners / Dispatchers · June 26, 2026

How to Onboard a New Technician to Caisey in 10 Minutes: A Training Workflow

Learn how to get a new technician up and running with Caisey in under 10 minutes. Step-by-step training workflow for MSPs using Caisey's intuitive UI and approval system.
MSP trainingtechnician onboardingremote troubleshootingCaisey workflowapproval-based support

When a new technician joins your MSP, the last thing you want is a multi-day training grind before they can help clients. Traditional remote support tools like ScreenConnect or TeamViewer pack in dozens of features, but that complexity becomes a bottleneck. Every new hire needs to learn session management, file transfer, chat, reboot options, and a maze of settings—all before they can take their first ticket.

Caisey was built differently. It strips away the unnecessary layers and puts the essential workflow front and center. In this guide, we'll walk through a training workflow that gets a new technician productive in under 10 minutes. No fluff. No confusing menus. Just a clear path from login to troubleshooting.

Why Traditional Remote Support Tools Slow Down Onboarding

Most remote support platforms are designed for power users. They assume you'll spend hours learning the interface. But for MSPs, technician turnover is real. Every hour spent on training is an hour not billing. With tools like ScreenConnect, you have to teach:

  • How to set up session types (attended vs. unattended)
  • Where to find the file transfer panel
  • How to configure two-factor authentication
  • The difference between host and client installers
  • How to manage access codes and permissions

New technicians often feel overwhelmed. They end up clicking around, hoping to find the right button. And if they accidentally run a destructive command without proper approval? That's a support nightmare.

Caisey solves this by designing the UI around a single, repeatable workflow: select a device, request approval, then troubleshoot. Everything else is optional or automatic.

The Caisey Difference: Simplicity by Design

Caisey is a cloud-based remote troubleshooting console that runs entirely in your browser. There's no software to install for the technician. The only requirement is that client devices have the Caisey AI runtime enrolled. Once that's done, every device appears in your dashboard with a clear status.

The key design principle is progressive disclosure. New technicians see only what they need: a device list, a request button, and a command input. Advanced features like session history, audit trails, and group management are one click away but don't clutter the initial view.

This means you can hand a new hire the URL and say, "Log in, pick a test device, and click 'Request Access'." They'll figure out the rest because the UI guides them.

Step 1: Get the Technician Logged In

Caisey uses browser-based authentication. You can invite a new technician via email from the organization settings. They click the link, set a password, and they're in. No VPN, no client download, no license key to enter.

Time spent: 2 minutes.

Step 2: Show How to Select a Device

Once logged in, the dashboard shows a list of enrolled endpoints. Each device displays its hostname, OS, last seen time, and group membership. New technicians can use the search bar to filter by name or tag.

Practical example: Ask your trainee to find the device named "Sales-Laptop-07" in the "Sales Team" group. They can click the device name to see more details, including recent session history and installed software.

Time spent: 1 minute.

Step 3: Request Approval and Start a Session

This is where Caisey's approval-based remote support shines. Instead of jumping straight into a session, the technician clicks "Request Access." The end user sees a permission prompt on their screen with details about who is requesting access and what actions are allowed.

The user must explicitly approve the session. If they deny it, the technician cannot proceed. This built-in safety net means you don't have to train new hires on when to ask for permission—the tool enforces it.

Practical example: Have your trainee request access to a test device that you control. Show them how the prompt appears on the client machine and how to accept it. Then explain that any destructive actions (like running a script that modifies the registry) will trigger another approval prompt.

Time spent: 2 minutes.

Step 4: Run Commands and Diagnose

Once the session is active, the technician sees a command-line interface. They can type standard commands (like ipconfig, ping, chkdsk) or use Caisey's built-in diagnostic tools. For more advanced troubleshooting, Caisey supports remote PowerShell troubleshooting with full approval tracking.

New technicians don't need to learn a proprietary scripting language. They can use the same commands they already know. Caisey logs every command and its output, so you can review later.

Practical example: Ask your trainee to run systeminfo on the test device. Show them how the output appears in real time. Then run a simple PowerShell command like Get-Process | Where-Object {$_.CPU -gt 100} to find high-CPU processes. The trainee will see that the workflow is identical to running commands locally—just with a remote target.

Time spent: 3 minutes.

Step 5: Review Session History and Audit Trail

After the session ends, Caisey automatically saves a full transcript. This includes the commands run, outputs, approval timestamps, and any file transfers. New technicians can view their own session history to learn from mistakes. Managers can use the IT support audit trail to verify compliance and review technician performance.

Practical example: Show your trainee how to navigate to the "History" tab. They can see every session they've conducted, filter by date or device, and even share a public link to the session transcript with the client for transparency.

Time spent: 2 minutes.

Conclusion: From Login to Productive Troubleshooting in Minutes

By following these five steps, a new technician can go from zero to troubleshooting in under 10 minutes. No manual reading. No complex configuration. Just a clean, approval-driven workflow that keeps both the technician and the end user safe.

Caisey's design philosophy is to reduce cognitive load for MSP teams. When you onboard a new hire, you don't want to teach them a tool—you want them to solve problems. Caisey gets out of the way and lets them focus on the issue at hand.

If you're tired of spending days training technicians on bloated remote support software, give Caisey a try. Your next new hire will thank you.

Caisey
loading...