# Caisey

Caisey is a remote troubleshooting console for MSPs, technical organizations, and trusted personal helpers.
Caisey helps MSPs and technical helpers troubleshoot enrolled client devices from a browser with machine context, approvals, audit history, and AI-assisted fixes.

Canonical site: https://helpforsupport.com
Short index: https://helpforsupport.com/llms.txt
Agents welcome: https://helpforsupport.com/agents
Sitemap: https://helpforsupport.com/sitemap.xml

## Pricing

Caisey plans are Free at $0 forever, Basic at $5 per month, Family IT at $10 per month, and Business at $20 per technician per month.

- Free: $0 forever. One personal device with lower usage limits.
- Basic: $5 per month. Up to 3 personal devices, higher usage limits, and a 30-day trial.
- Family IT: $10 per month. Up to 10 personal devices, the highest personal usage limits, and a 30-day trial.
- Business: $20 per technician per month. Unlimited devices and usage subject to abuse guardrails, an organization workspace, pay-per-technician seats, priority support, and a 30-day trial.

Caisey does not use per-device pricing. Business is $20 per technician per month and includes unlimited devices. Device count does not change the price.
Current pricing is introductory and may change.
Pricing page: https://helpforsupport.com/pricing

## Agents

# Agents welcome

AI agents can read Caisey public product, docs, and pricing today. Agent ID sign-in, a personal agent plan, and an MCP server are still on the way.

## How agents can use Caisey today

Agents can read the public product, documentation, and pricing without an account. The console still requires a person to sign in. There is no agent account yet.

- llms.txt: https://helpforsupport.com/llms.txt. Short index of public pages, pricing, and Markdown mirrors.
- llms-full.txt: https://helpforsupport.com/llms-full.txt. Full product, docs, and pricing text, generated from the same sources as the public pages.
- Canonical site: Public pages stay on https://helpforsupport.com.

## Agent ID sign-in (coming soon)

Agent ID sign-in is coming soon. Agents cannot sign in on their own today.

## Agent Personal plan (coming soon)

A $5 per month Agent Personal plan is coming soon. It is not billed today. Caisey plans are Free at $0 forever, Basic at $5 per month, Family IT at $10 per month, and Business at $20 per technician per month. Agent Personal is separate from Basic.

## MCP server (coming soon)

An MCP server is coming soon, behind Clerk OAuth.

## Business seats

On Business plans, an agent counts as a regular seat. Business is $20 per technician per month. Unlimited devices and usage subject to abuse guardrails, an organization workspace, pay-per-technician seats, priority support, and a 30-day trial. Caisey does not use per-device pricing. Business is $20 per technician per month and includes unlimited devices. Device count does not change the price.

Agents welcome page: https://helpforsupport.com/agents
llms.txt: https://helpforsupport.com/llms.txt
llms-full.txt: https://helpforsupport.com/llms-full.txt

## Documentation

These are the same public user guides served at /docs.

### Getting Started with Caisey

User-focused walkthrough for signing in, enabling your workspace, and starting remote troubleshooting sessions.

- Updated: 2026-05-20
- Canonical: https://helpforsupport.com/docs/getting-started
- Markdown: https://helpforsupport.com/docs/getting-started.md

# Caisey Getting Started

Caisey lets you troubleshoot a remote computer from the browser while keeping the session, approvals, and audit trail in one place. Use this guide when you are signing in for the first time or trying to start your first remote session.

## Before you start

Make sure you have:

- a Caisey account,
- access to the correct workspace or organization,
- at least one endpoint installed or an installer command ready to run,
- and permission from the device owner or customer to troubleshoot the machine.

If you are helping a family member, use the personal connection flow instead of an MSP/client installer.

## First login checklist

1. Sign in.
2. Choose the right workspace from the account controls.
3. Open **Machines**.
4. Check whether the target computer is already listed.
5. If it is not listed, add the device using the setup path that matches your workspace.
6. Wait for the machine to show **ready**.
7. Open the machine and start a chat.

## Start your first session

Choose a ready machine from **Machines**, then open **Chat**. Ask for the outcome you want, not just the command you think should run. For example:

- "Find out why QuickBooks will not open for the front desk user."
- "Check why this Mac is running out of disk space."
- "Review recent Windows update errors and summarize the likely cause."

Caisey may ask you to approve tool actions before it continues. Review those prompts carefully. If an action looks broader than the task requires, deny it and ask for a narrower approach.

## What Caisey records

Caisey keeps operational records for accountability:

- machine and session context,
- chat messages and tool activity captured through the control plane,
- permission decisions,
- share-link activity,
- and workspace audit events.

Live display and future audit records use common PII and secret redaction, but you should still avoid pasting passwords, private keys, customer secrets, or unrelated personal data into chat.

## Good first-session habits

- Confirm the device name before sending a prompt.
- Ask Caisey to explain what it found before making changes.
- Approve only the tool actions needed for the current task.
- Use a shared snapshot only after reviewing the transcript.
- Check the audit log when you need a record of what happened.

### Caisey Console Navigation

Where to find Machines, Chat, Shared links, Permissions, and Audit logs in the Caisey console.

- Updated: 2026-05-20
- Canonical: https://helpforsupport.com/docs/console-navigation
- Markdown: https://helpforsupport.com/docs/console-navigation.md

# Caisey Console Navigation

The Caisey console is organized around the troubleshooting job: find the right device, start or resume a session, approve actions, then review or share the result.

## Main areas

- **Machines**: device inventory, client grouping, install state, and setup commands.
- **Chat**: active and historical troubleshooting conversations.
- **Shared links**: public transcript snapshots you can copy, refresh, revoke, and label as passcode-protected or legacy unprotected.
- **Permissions**: default rules and machine-specific approvals.
- **Audit log**: workspace activity for review and support follow-up.

## Where to find things

### Machine list

On desktop, open **Machines** from the top navigation. On a phone, use **Chat / Machines / More**; open sessions and Plan from the chat header.

- Use search to filter by machine name or client name.
- Use client groups to narrow an MSP customer environment.
- Check status before opening a chat.
- Use **Add machine** when the endpoint is not enrolled yet.

### Chat header

The chat header shows the active session title when you are in a chat. On a phone it is the thin bar above the transcript: sessions, title, machine (opens Machines), and Plan when a checklist exists. It may also include:

- connection status,
- fast mode controls,
- token allowance usage,
- share controls,
- feedback,
- and account controls.

### Operational pages

On a phone, **More** holds Install, Links, Permissions, Audit log, Settings, Docs, Feedback, and account controls. On desktop, use the top navigation. Use these pages when you are not focused on one prompt:

- **Audit log** shows what happened across the workspace.
- **Shared links** shows what is currently public.
- **Permissions** controls what Caisey can do automatically.

## Status meanings

- **Pending**: setup or verification is not complete. Chat is disabled.
- **Ready**: the endpoint can be selected for troubleshooting.
- **Offline**: Caisey knows the device, but it is not currently reachable.
- **Removing**: endpoint cleanup or control-plane deletion is in progress.

When in doubt, confirm the client group, machine name, and platform before starting work.

### Work Accounts vs Personal Accounts

Set up workflows for MSP/client orgs and personal or family-use accounts, including connection code flow.

- Updated: 2026-05-20
- Canonical: https://helpforsupport.com/docs/work-vs-personal-setup
- Markdown: https://helpforsupport.com/docs/work-vs-personal-setup.md

# Work Accounts vs Personal Accounts

Caisey supports both managed workspaces and personal/family support. Pick the setup path based on who owns the device and who needs the audit trail.

## Work account / MSP setup

A work account is best for MSPs, IT teams, and customer environments.

- Group machines by client.
- Use organization-wide, client-specific, or machine-specific installers.
- Keep technician activity in the workspace audit log.
- Rotate installer commands if one is exposed.

### Recommended work flow

1. Open **Install**.
2. Choose platform (Windows or Mac).
3. Assign the machine to a client when appropriate.
4. Copy the installer command.
5. Run it through RMM, GPO, or a trusted admin shell on the endpoint.
6. Return to **Machines** and wait for **ready**.

### Support desk / SOS flow

Use this for ad-hoc phone support when you do not already have an RMM or installer command on the endpoint.

1. Open **Install**.
2. Optionally choose a client scope.
3. Click **Activate support desk**.
4. Read the rotating 8-character code to the person on the phone and send them to `/sos`, or click **Copy SOS link**. Copying the link shows the next step: send it and have them open it in their browser.
5. They download the setup package and complete the consent prompt.
6. Click **Deactivate support desk** when the call ends.

The code rotates every five minutes while the desk is active.

## Personal account setup

A personal account is best for helping your own devices or trusted family devices.

- Client groups are hidden.
- Device limits depend on your plan.
- Family setup uses a temporary connection code and public setup page.

### Family / personal connection flow

1. Open **Install** in your personal workspace.
2. Click **Connect family member**. Caisey copies a setup link.
3. Send that link and have them open it in their browser. The screen states this next step in large type.
4. They review the page and download the installer for their platform.
5. The endpoint registers and appears under **Machines**.

Treat connection codes like temporary secrets. Share them only with the person who should install Caisey.

## Which path should I use?

- Use **work/MSP setup** for customer machines, shared technician teams, compliance review, and client grouping.
- Use **support desk / SOS setup** when you need a phone-friendly rotating code instead of a long installer command.
- Use **personal setup** for family IT or devices you personally administer.
- Do not use a personal connection code for a customer endpoint that belongs in an MSP workspace.

### Install and Onboard Devices

Generate, rotate, and deploy installer commands for Windows and macOS machines.

- Updated: 2026-05-20
- Canonical: https://helpforsupport.com/docs/install-and-connection
- Markdown: https://helpforsupport.com/docs/install-and-connection.md

# Installers, Rotation, and Device Onboarding

Use this guide when you need to enroll a computer, rotate an exposed installer command, or understand why a device is not ready yet.

## Installer types

- **Organization installer** enrolls work devices without assigning a client.
- **Client installer** enrolls devices directly into a selected client group.
- **Machine-specific installer** installs one named endpoint created by an admin.
- **Personal installer** is delivered through the family or personal connection flow.

## Supported platforms

Caisey currently supports:

- Windows x64
- Apple Silicon Mac

Intel macOS and Linux installers are not currently shown in the console.

## Enroll a device

1. Open **Install**.
2. Select Windows or Mac.
3. Choose the correct enrollment scope.
4. Copy the generated command.
5. Run it on the endpoint with the required local privileges.
6. Return to Caisey and watch for the machine to become **ready**.

Do not send a work installer command to a personal device or a different customer. If you copied the wrong command, rotate it.

## Rotate installer commands

Rotate an installer when a command may have leaked, was sent to the wrong person, or should no longer be usable.

1. Return to the **Install** tab for that organization or client.
2. Click **Rotate**.
3. Use the new command for future installs.

The previous command stops working after rotation completes.

## Deployment visibility

## If a device stays pending

- Confirm the installer finished without errors.
- Check that the endpoint platform is supported.
- Make sure the device has network access.
- Use **Verify machine** if manual verification is available.
- Retry after a short delay if the endpoint just finished installing.

If the installer failed, copy the visible error text before closing the terminal. That output is usually the fastest way to diagnose setup problems.

### Permissions and Settings

Configure permission policies, fast mode defaults, token visibility, and share-link lifecycle.

- Updated: 2026-05-20
- Canonical: https://helpforsupport.com/docs/permissions-and-settings
- Markdown: https://helpforsupport.com/docs/permissions-and-settings.md

# Permissions, Session Controls, and Settings

Caisey is designed so remote actions are visible and controlled. Permissions decide what can run automatically and what needs review during a session.

## Where permissions live

Permissions appear in two places:

- **Permissions** for workspace defaults and machine-level rules.
- **Chat prompts** when Caisey requests approval for a specific action.

## Permissions page controls

## Organization defaults

Admins can allow selected low-risk actions across the workspace. Current defaults can allow:

- read-only PowerShell `Get-*` commands,
- external folder access,
- and cloud research web search/fetch tools.

Deny rules still take precedence. Use defaults for actions you are comfortable allowing broadly. Organization defaults, memory, and approval scopes are on the Settings tab. Toggles there save immediately.

## Machine rules

Machine rules are useful when one endpoint needs different behavior from the rest of the workspace. Use them for servers, sensitive customer devices, incident response, or temporary lockdowns.

## Approval prompts

When Caisey pauses for approval:

1. Read the requested action.
2. Check whether it matches the task.
3. Approve only if the scope is reasonable.
4. Deny and ask for a narrower action when it is too broad.

For example, a read-only diagnostic command is different from a command that changes services, deletes files, or sends data outside the endpoint.

## Chat settings

A small settings menu beside the session header exposes:

- fast mode defaults,
- ticket notes defaults for new chats,
- per-chat fast mode override,
- theme controls,
- and token allowance visibility.

## Shared links settings and lifecycle

Public share links are frozen transcript snapshots. New and refreshed transcript shares require a six-digit passcode by default. The passcode is shown once after create or refresh, so copy it before closing the share controls. Existing older links without passcodes keep working until they expire, are revoked, or are refreshed. Before creating or refreshing one, review the transcript for customer data, credentials, hostnames, logs, file paths, and tool output.

In **Shared links**, you can:

- View active links,
- Copy share URLs,
- Copy the one-time passcode shown after create or refresh,
- Refresh snapshots,
- Revoke access when a share is no longer needed.

### How is Caisey safe?

Understand data handling, model usage, and how command execution stays controlled and reviewable.

- Updated: 2026-06-05
- Canonical: https://helpforsupport.com/docs/how-is-caisey-safe
- Markdown: https://helpforsupport.com/docs/how-is-caisey-safe.md

# How is Caisey safe?

You are wondering how it could possibly be safe to turn an AI agent loose on your clients' devices. We come from the MSP world, so it is exactly the question we would ask. Here is the honest answer: no one is turning anything loose.

Let's walk through the concerns data-conscious teams raise most often.

## Data security and sovereignty

Every conversation with Caisey is handled with care. Cloudflare is our non-AI compute and storage partner, held to strong security standards. Data is encrypted with TLS 1.2+ in transit and AES-256 at rest.

We combine deterministic and non-deterministic sanitization to scrub sensitive details before they are rendered in a chat.

When you delete your data, Caisey schedules deletion after seven days. Once that purge runs, it is gone for good.

All data is transmitted, processed, and stored in the United States, and we never sell, trade, or exchange it in any way.

## AI models

No, ChatGPT is not training on your clients' data.

We run open-weight models on a third-party American inference provider. We pay with dollars, not data.

We may leverage your data to improve the experience, but it is never sold, traded, or exchanged in any way.

## How a Caisey action works

How does a Caisey action work? It helps to understand what Caisey is.

Caisey is a runtime on the endpoint with a set of tools. The primary one is the ability to run a PowerShell or CMD command, and every command runs the same gauntlet.

When Caisey wants to pull logs, flush DNS, run `sfc /scannow`, or run `dism`, it names the exact command and the reason it needs to run it.

If the command is not pre-approved by your policy, we run an independent analysis with a separate AI model given different context to defeat prompt injection. That review judges whether the command is dangerous on that platform and explains why.

We then render the command and that analysis in the UI so you can approve the action explicitly.

## Human-in-the-loop control

Every action is either pre-approved by your policy or approved by you. There is no third path.

You stay in control.

If you have concerns or want to chat with our dev team for any reason, use the contact form on this page. We'd love to chat.

### Support and Contact

Audit logs, troubleshooting checks, and support contact details for Caisey workspace issues.

- Updated: 2026-05-20
- Canonical: https://helpforsupport.com/docs/support-and-contacts
- Markdown: https://helpforsupport.com/docs/support-and-contacts.md

# Support, Audits, and Where to Get Help

Caisey includes audit and support tools so you can reconstruct what happened and report issues with useful detail.

## Audit log

The **Audit log** records major workspace activity:

- machine lifecycle events,
- permission changes,
- installer actions,
- session activity,
- share-link activity,
- and other control-plane events.

Use the log when you need to confirm who changed a setting, rotated an installer, created a share link, or worked on a machine.

## Before you contact support

Collect the details that identify the affected workspace and endpoint:

- page path, such as `/console`, `/docs`, or `/connect/<code>`,
- workspace or organization name,
- client name if this is an MSP device,
- machine name and platform,
- approximate browser date and time,
- and any relevant audit-log timestamp.

## When to contact us

Contact support when you run into:

- command-rotation problems,
- permission prompts that do not clear,
- shared link access issues,
- install or verification delays,
- unexpected token allowance errors,
- or endpoint connection behavior that does not match the machine state.

Use the in-product feedback link or the contact form on the Caisey safety page. Include the workspace type, such as MSP, work, or personal, when possible.

## What not to send

Do not email passwords, private keys, customer secrets, full logs with unrelated personal data, or raw connection codes. If a support request needs sensitive details, ask for the safest way to provide them.

## Product pages

These are the same public product and troubleshooting pages served as HTML.

### Remote troubleshooting that starts with the machine context

Caisey helps technical teams troubleshoot enrolled endpoints from a browser with machine context, approvals, and session history.

Caisey is for support work where the technician needs more than a temporary screen view. Enrolled endpoints connect to the Caisey control plane, so a browser session can inspect machine state, request guarded actions, and keep the work attached to the device.

#### What remote troubleshooting means in Caisey

Caisey coordinates headless endpoint runtimes through a cloud console. The technician works from the selected machine, client grouping, prior sessions, and live approval boundaries instead of asking the user to recreate every symptom.

- Open the console from a browser and choose an enrolled endpoint.
- Use AI-assisted troubleshooting with machine-aware context.
- Keep session records, approvals, and audit history tied to the device.

#### Where it fits

The model is strongest for recurring endpoint issues, after-hours checks, distributed client environments, and support queues where one technician may need to hand off work to another.

#### What it does not replace

Caisey is not positioned as a full visual remote desktop replacement for every workflow. It complements or replaces screen sharing when the core job is diagnosis, repair, verification, and durable support history.

**Is Caisey a remote desktop tool?**

Caisey is a remote troubleshooting console. It focuses on enrolled endpoint context, AI-assisted diagnosis, approvals, and session history rather than a general-purpose visual remote desktop session.

**Do technicians need to be on the client device?**

No. Technicians work from the browser console while the enrolled endpoint runtime performs the troubleshooting work on the selected machine.

**How does Caisey preserve troubleshooting history?**

Runtime chat traffic is proxied through the Worker so Caisey can keep forward-only conversation and audit records tied to the organization, machine, and session.

- Canonical: https://helpforsupport.com/remote-troubleshooting
- Markdown: https://helpforsupport.com/remote-troubleshooting.md

### Remote support for MSPs managing enrolled client endpoints

Caisey gives MSPs browser-based remote troubleshooting for enrolled client devices with client grouping, approvals, and audit history.

MSP support work is rarely a one-off screen share. Caisey keeps machines grouped by organization and client, gives technicians a browser console for selected endpoints, and records the troubleshooting context that matters during handoffs.

#### Built around client machines

Caisey supports admin-created machine deployments, org-wide installers, and client-specific enrollment flows. That lets MSPs keep support work attached to the right customer and endpoint.

- Group machines by MSP client.
- Deploy Windows x64 and Apple Silicon macOS endpoints.
- Use machine readiness and bridge status before starting work.

#### Guarded execution for support teams

Approvals, permission defaults, and audit records help keep powerful actions accountable. Caisey is designed for technical teams that need speed without losing control of what happened.

#### Useful during handoffs

Conversation replay, tool-call records, machine metadata, and session history give the next technician a structured starting point instead of a loose ticket note.

**Can Caisey separate machines by client?**

Yes. MSPs can group devices by client, copy client-specific installers, or enroll devices generically and assign them to a client later.

**Can non-admin technicians use Caisey?**

Caisey currently distinguishes admin and non-admin access. Granular role types are deferred, but the console already separates deployment and support surfaces.

**Does Caisey keep an audit trail?**

Yes. Runtime chat traffic, approvals, tool-call context, and session metadata are persisted through Caisey control-plane records.

- Canonical: https://helpforsupport.com/msp-remote-support
- Markdown: https://helpforsupport.com/msp-remote-support.md

### An AI remote troubleshooting console with endpoint context

Caisey uses AI-assisted troubleshooting with endpoint context, approvals, and durable session records for remote support teams.

Caisey applies AI to support work that already has a selected machine, organization, and session. The goal is practical diagnosis and verified repair, not generic advice disconnected from the endpoint.

#### AI grounded in the selected endpoint

The browser console coordinates a Caisey runtime on the enrolled device. That runtime can help inspect state, run diagnostics, and report results back into a session record.

#### Approvals stay part of the workflow

Caisey can hold risky actions for review and apply organization permission defaults for common support tasks. That keeps AI-assisted work inside technician-controlled boundaries.

#### Records outlive the chat window

Sessions, messages, machine context, approvals, and response metrics are stored in the control plane so support teams can inspect what happened later.

**Does Caisey pick a machine before using AI?**

Yes. In the live console, technicians select an enrolled and ready machine before starting endpoint troubleshooting work.

**Can AI actions be reviewed?**

Yes. Caisey supports approval and permission-policy flows so powerful actions can be reviewed before they run.

**Is Caisey only for MSPs?**

No. MSPs are a core audience, but Caisey also supports technical organizations and trusted personal helpers that need remote troubleshooting with consent and context.

- Canonical: https://helpforsupport.com/ai-remote-troubleshooting-console
- Markdown: https://helpforsupport.com/ai-remote-troubleshooting-console.md

### Endpoint troubleshooting agents controlled from the browser

Caisey coordinates headless endpoint runtimes so technicians can troubleshoot enrolled Windows and macOS machines from a browser.

Caisey uses enrolled endpoint runtimes to make remote troubleshooting durable. The runtime lives on the device, connects back through Caisey bridge infrastructure, and lets the cloud console coordinate support work.

#### Persistent enrollment

Instead of starting with a one-time support link for every incident, an organization can enroll devices and return to them when troubleshooting is needed.

#### Bridge-first connectivity

Endpoint bridge connectivity keeps RPC as the always-on sendability channel. Live runtime events can attach while browser subscribers are active.

#### Control-plane records

Caisey keeps machine records, session metadata, and conversation history in Cloudflare Worker and Durable Object infrastructure rather than treating the browser as the source of truth.

**Which endpoint platforms does Caisey support today?**

Caisey has installer flows for Windows x64 and Apple Silicon macOS endpoints. Intel macOS and Linux endpoints remain deferred.

**Does the endpoint initiate the connection?**

Yes. Caisey uses outbound bridge connectivity from enrolled machines back to the control plane.

**Can endpoint cleanup be requested from the console?**

Yes. Deleting a device requests endpoint cleanup first, then the control plane finalizes deletion after cleanup is reported.

- Canonical: https://helpforsupport.com/endpoint-troubleshooting-agent
- Markdown: https://helpforsupport.com/endpoint-troubleshooting-agent.md

### A screen sharing alternative for troubleshooting work

Caisey is a screen-sharing alternative for support teams that need endpoint context, guarded actions, and durable troubleshooting history.

Screen sharing is useful when a technician needs to watch or guide a user. Caisey is built for the cases where the support team needs to diagnose, repair, verify, and preserve the work around an enrolled endpoint.

#### Start from the device, not the meeting

Caisey lets technicians choose an enrolled endpoint and work from its machine record. That reduces repeated setup when the same client device needs support again.

#### Keep the support record

A screen share can disappear when the call ends. Caisey keeps session history, approval outcomes, and machine context available for later review.

#### Use both when needed

Caisey is not a claim that visual collaboration is never useful. It is a better fit when the issue is system state, command output, configuration, or repeatable verification.

**When is Caisey better than screen sharing?**

Caisey is better suited to support work that depends on endpoint diagnostics, guarded repair actions, audit history, or repeated access to an enrolled machine.

**Does Caisey require the end user to drive the session?**

No. The technician works from the browser console after selecting an enrolled machine, subject to the organization policy and approval model.

**Can Caisey replace every screen-share workflow?**

No. Visual remote collaboration still has valid uses. Caisey is focused on machine-aware troubleshooting rather than general visual control.

- Canonical: https://helpforsupport.com/screen-sharing-alternative
- Markdown: https://helpforsupport.com/screen-sharing-alternative.md

### Remote troubleshooting for Outlook not opening

How Caisey can help technicians investigate Outlook launch failures on enrolled endpoints with machine context and session history.

When Outlook will not open, the useful clues are usually on the endpoint: process state, Office health, profile symptoms, add-ins, updates, and event logs. Caisey helps technicians investigate from the browser while keeping the work attached to the machine record.

#### Start with the symptom and context

A technician can ask Caisey to gather structured context before trying a fix. That keeps the session focused on the specific machine and user report.

- Confirm whether Outlook fails silently, hangs, or shows an error.
- Check recent Office or Windows updates.
- Record findings in the Caisey session history.

#### Investigate likely causes

Common paths include stuck Outlook processes, problematic add-ins, profile damage, authentication prompts, or Office repair needs. Caisey can help sequence checks before changes are made.

#### Verify before closing the ticket

After a repair step, the technician can use the same session to confirm Outlook launches and note what changed for the next support handoff.

**Can Caisey fix Outlook automatically?**

Caisey can help diagnose and perform approved troubleshooting actions, but technicians remain responsible for reviewing risky steps and verifying the outcome.

**Why use an endpoint troubleshooting console for Outlook?**

Outlook failures often depend on local machine state. A console tied to the endpoint can preserve checks, results, and repair history in one session.

**Does Caisey store the troubleshooting notes?**

Yes. The session and audit history stay associated with the selected organization, machine, and Caisey session.

- Canonical: https://helpforsupport.com/remote-troubleshooting/outlook-not-opening
- Markdown: https://helpforsupport.com/remote-troubleshooting/outlook-not-opening.md

### Remote troubleshooting for VPN connection issues

Use Caisey to investigate VPN connection issues remotely with endpoint diagnostics, approvals, and durable troubleshooting records.

VPN failures can come from credentials, network reachability, client configuration, DNS, certificates, updates, or local firewall state. Caisey gives technicians a machine-aware place to gather evidence and record the path to resolution.

#### Separate user symptoms from endpoint state

The first pass should capture the VPN client, error wording, current network, and whether other services are reachable from the endpoint.

#### Run checks in a controlled session

Caisey can help inspect local network configuration, test reachability, and review client state while keeping approval boundaries around powerful changes.

#### Preserve repeatable fixes

VPN issues often recur across clients. A Caisey session gives the next technician a record of checks, outputs, and decisions instead of a one-line ticket update.

**What should a technician check first for VPN issues?**

Start with the exact error, network reachability, DNS behavior, VPN client state, recent updates, and whether the issue is isolated to one endpoint.

**Can Caisey run network diagnostics remotely?**

Caisey is designed to coordinate endpoint troubleshooting from the browser, including diagnostic commands and checks subject to policy and approvals.

**Why keep VPN troubleshooting in a session history?**

VPN fixes can involve several hypotheses. Capturing the sequence helps during escalation, handoff, and future incidents on the same machine.

- Canonical: https://helpforsupport.com/remote-troubleshooting/vpn-connection-issues
- Markdown: https://helpforsupport.com/remote-troubleshooting/vpn-connection-issues.md

### Remote troubleshooting for printer offline problems

Caisey helps support teams investigate printer offline problems from enrolled endpoints with local context and audit history.

Printer offline tickets are often a mix of queue state, driver behavior, network reachability, Windows services, and user expectations. Caisey helps the technician inspect the endpoint-side facts before trying a fix.

#### Gather the local print context

The technician can start by identifying the printer, queue status, default printer setting, recent driver changes, and whether the endpoint can reach the printer.

#### Avoid blind resets

Restarting services or removing devices can disrupt work. Caisey keeps the diagnostic trail visible so technicians can choose the least disruptive approved action.

#### Document the resolution

Whether the issue is queue state, stale configuration, network reachability, or a driver problem, the session record helps support teams recognize repeat failures.

**Why does a printer show offline from one computer?**

The cause may be local queue state, driver configuration, network reachability from that endpoint, or Windows print service behavior.

**Can Caisey help without screen sharing?**

Yes. Many printer issues can be diagnosed from endpoint state and command output without requiring the user to present their screen.

**Does Caisey track what was changed?**

Caisey records conversation and audit context so support teams can review the troubleshooting path later.

- Canonical: https://helpforsupport.com/remote-troubleshooting/printer-offline
- Markdown: https://helpforsupport.com/remote-troubleshooting/printer-offline.md

### Remote troubleshooting for Windows Update errors

Investigate Windows Update errors remotely with Caisey endpoint context, controlled actions, and session history.

Windows Update errors are easier to handle when the technician can see endpoint state, recent update history, disk and service conditions, and the exact failure code. Caisey keeps that investigation inside a durable machine session.

#### Capture the error and update state

Useful first facts include the update code, pending restart state, free disk space, Windows version, recent update attempts, and whether required services are running.

#### Use guarded repair steps

Update repair commands can be disruptive. Caisey supports approval-aware workflows so technicians can inspect and confirm before powerful actions run.

#### Verify installation state

The same Caisey session can record whether the update succeeds after remediation and what changed during the repair.

**What information helps troubleshoot Windows Update remotely?**

Collect the update error code, pending reboot state, service status, recent update history, disk space, and endpoint OS version.

**Can Caisey help with approved repair commands?**

Yes. Caisey can coordinate endpoint troubleshooting steps while preserving approvals and audit records around sensitive actions.

**Why is session history useful for update errors?**

Update issues can require multiple attempts. A durable session prevents the next technician from repeating the same failed steps.

- Canonical: https://helpforsupport.com/remote-troubleshooting/windows-update-errors
- Markdown: https://helpforsupport.com/remote-troubleshooting/windows-update-errors.md

### Remote troubleshooting for a slow computer

Caisey helps technicians investigate slow computer reports remotely using endpoint context, diagnostics, and durable session notes.

A slow computer report can mean resource pressure, startup load, background updates, failing hardware signals, browser problems, or one overloaded application. Caisey helps turn a vague complaint into a structured endpoint investigation.

#### Turn a broad complaint into measurable checks

The technician can use the Caisey session to collect CPU, memory, disk, startup, update, and application context before choosing a fix.

#### Keep the user impact visible

Support teams can record what the user experienced, what was checked, and why a repair action was or was not taken.

#### Compare future incidents

Because the work stays tied to the endpoint, repeat performance complaints can start from prior findings instead of a fresh guess.

**What should be checked first on a slow computer?**

Start with resource usage, disk pressure, startup load, pending updates, obvious failing processes, and whether the complaint affects one app or the whole machine.

**Can Caisey help diagnose performance without being onsite?**

Yes. Caisey is designed for browser-controlled troubleshooting of enrolled endpoints, including diagnostic checks that help isolate performance causes.

**Why attach performance troubleshooting to a machine record?**

Performance issues often recur. Keeping the history attached to the endpoint helps technicians compare symptoms and avoid repeating work.

- Canonical: https://helpforsupport.com/remote-troubleshooting/slow-computer
- Markdown: https://helpforsupport.com/remote-troubleshooting/slow-computer.md

### Remote endpoint diagnostics with machine context

Use Caisey to run remote endpoint diagnostics from a browser with machine context, approval-aware actions, and durable troubleshooting history.

Endpoint diagnostics are most useful when they start from the actual machine, not a generic checklist. Caisey gives technicians a browser-controlled session for gathering state, asking follow-up questions, and preserving the diagnostic path.

#### Start from the enrolled device

Caisey sessions begin with a selected endpoint, client grouping, connection state, and prior history so the technician can avoid asking the user to recreate every symptom.

- Check live readiness before acting.
- Collect system and app state in one session.
- Keep findings attached to the machine record.

#### Use diagnostics before repair

The workflow encourages technicians to inspect the issue before running a fix, especially when the next step could affect services, files, or user data.

#### Make handoffs easier

Because diagnostic results stay in the Caisey record, another technician can continue from the same context instead of rebuilding the investigation from ticket notes.

**What are remote endpoint diagnostics?**

They are checks run against an enrolled device to understand system, application, network, update, or performance state before choosing a fix.

**Does Caisey require screen sharing for diagnostics?**

No. Caisey focuses on endpoint context and controlled troubleshooting sessions rather than treating the user screen as the only source of truth.

**Why keep diagnostics in the session history?**

Stored diagnostic context helps support teams compare repeat issues, review decisions, and continue work without starting from zero.

- Canonical: https://helpforsupport.com/remote-endpoint-diagnostics
- Markdown: https://helpforsupport.com/remote-endpoint-diagnostics.md

### Remote PowerShell troubleshooting with approval boundaries

Coordinate remote PowerShell troubleshooting with explicit approvals, machine context, and audit history in Caisey.

PowerShell is useful for Windows support, but it should not disappear into an unreviewed remote session. Caisey keeps command-oriented troubleshooting tied to the endpoint, the technician, and the approval record.

#### Inspect before changing state

Read-only checks can help identify services, updates, event log clues, disk pressure, and network state before a technician asks to run a repair action.

#### Make risky actions reviewable

When a command could change the device, Caisey surfaces the request in context so the technician can approve or deny it before execution.

#### Keep command work auditable

The resulting session history gives teams a record of what was requested, what was approved, and what the endpoint returned.

**Can Caisey help with remote PowerShell checks?**

Yes. Caisey is designed to coordinate endpoint troubleshooting from a browser, including command-oriented checks and approval-aware actions.

**Are all PowerShell commands automatically allowed?**

No. Caisey supports permission prompts and organization defaults so sensitive actions can stay reviewable.

**Why is audit history important for PowerShell troubleshooting?**

Command output and approval decisions explain what changed on the endpoint and help the next technician understand the path already taken.

- Canonical: https://helpforsupport.com/remote-powershell-troubleshooting
- Markdown: https://helpforsupport.com/remote-powershell-troubleshooting.md

### An IT support audit trail built into troubleshooting

Caisey gives IT support teams an audit trail for remote troubleshooting sessions, approvals, machine context, and follow-up review.

Audit trails are more useful when they are captured during the support workflow. Caisey records remote troubleshooting context as technicians diagnose, request approvals, and verify outcomes.

#### Attach activity to the right context

Caisey ties work to the organization, technician, endpoint, client grouping, and session rather than leaving the final record as a loose ticket summary.

#### Review approvals and outcomes

Powerful endpoint actions are easier to explain later when the approval request, decision, and resulting session are preserved together.

#### Use history operationally

The record helps with escalations, repeat incidents, technician coaching, and customer conversations after the remote window would normally be gone.

**What should an IT support audit trail include?**

Useful records include who worked on the endpoint, what was requested, what was approved, relevant machine context, and the troubleshooting outcome.

**Is the audit trail only for compliance?**

No. In Caisey, audit history is also an operational surface for handoffs, review, and repeat-issue comparison.

**How does Caisey preserve troubleshooting context?**

Runtime traffic flows through the Caisey control plane so session and audit records can remain attached to the machine and organization.

- Canonical: https://helpforsupport.com/it-support-audit-trail
- Markdown: https://helpforsupport.com/it-support-audit-trail.md

### Remote support where sensitive actions stay reviewable

Use Caisey for remote support workflows where sensitive endpoint actions are reviewed, approved, and recorded in context.

Remote support gets safer when powerful endpoint actions are not invisible. Caisey keeps approvals inside the troubleshooting workflow so technicians can understand and record what they allow.

#### Hold sensitive actions for review

Caisey can surface command and file-change requests before they run, giving the technician a clear chance to approve or deny the action.

#### Pair approval with machine context

A decision is easier to make when the request appears alongside the selected device, session goal, and surrounding troubleshooting conversation.

#### Preserve the decision

The approval decision remains part of the session history so teams can review what happened after the support work is done.

**Why use approvals in remote support?**

Approvals create a checkpoint before actions that could change endpoint state, affect user files, or disrupt services.

**Does approval-based support slow down every action?**

No. Teams can configure defaults for low-risk work while keeping sensitive operations reviewable.

**Where are approval decisions stored?**

Caisey keeps approval context with the troubleshooting session and audit records for later review.

- Canonical: https://helpforsupport.com/approval-based-remote-support
- Markdown: https://helpforsupport.com/approval-based-remote-support.md

### Remote support for the family IT helper

Caisey helps trusted family helpers support enrolled personal devices with explicit setup, consent, and durable troubleshooting history.

Family computer help works best when the person receiving help understands the setup and the helper has a durable place to troubleshoot. Caisey supports that personal workflow with connection codes and machine-based sessions.

#### Make the setup explicit

A trusted helper can create a connection code so a family member can follow a visible setup flow instead of installing mystery access software.

#### Keep help tied to the device

Once enrolled, the device can be selected from the Caisey console for future troubleshooting without asking the person to recreate every detail over the phone.

#### Preserve what was fixed

Session history helps the helper remember what changed when a printer, email app, update, or slow-computer issue returns later.

**Is Caisey only for MSPs?**

No. Caisey is also designed for trusted personal helpers who support family devices with explicit setup and consent.

**How does a family member connect a device?**

A helper can create a single-use connection code that opens a public setup flow for the family member.

**Why use a machine record for family support?**

The machine record keeps support history attached to the device, which is useful when the same issue comes back.

- Canonical: https://helpforsupport.com/family-it-remote-support
- Markdown: https://helpforsupport.com/family-it-remote-support.md

### MSP device troubleshooting across enrolled client machines

Caisey helps MSPs troubleshoot client devices from a browser with client grouping, enrolled endpoints, approvals, and support history.

MSP support depends on knowing which client, device, technician, and prior session are involved. Caisey organizes remote troubleshooting around enrolled machines and client context.

#### Choose the right client device

Caisey supports client grouping so technicians can find the right machine before opening a troubleshooting session.

#### Standardize the support path

Technicians can diagnose, request approvals, repair, and verify inside a consistent workflow instead of relying on private notes or ad hoc remote windows.

#### Review recurring issues

Machine-attached session history helps teams compare repeat device problems across clients and technicians.

**How does Caisey help MSPs organize devices?**

Caisey supports enrolled machine records and client grouping so technicians can start from the right customer context.

**Can an MSP use Caisey without screen sharing?**

Yes. Caisey focuses on browser-controlled endpoint troubleshooting and can complement or replace screen sharing for diagnostic and repair work.

**Why do MSPs need device-level session history?**

Device history helps with escalations, handoffs, repeat issues, and customer explanations after the ticket closes.

- Canonical: https://helpforsupport.com/msp-device-troubleshooting
- Markdown: https://helpforsupport.com/msp-device-troubleshooting.md

### Remote troubleshooting for blue screen errors

Investigate blue screen reports remotely with Caisey machine context, diagnostic checks, approvals, and session history.

Blue screen reports need more than a screenshot of the stop code. Caisey helps technicians gather endpoint context, recent changes, update state, and follow-up evidence in one durable session.

#### Capture the failure context

Useful clues include the stop code, recent driver or update changes, disk health signals, event timing, and whether the problem repeats after restart.

#### Avoid blind repair steps

A guarded workflow helps the technician inspect the device before approving disruptive repairs or cleanup actions.

#### Preserve the investigation

If the issue returns, the next session can start from the previous findings instead of asking the user to remember what happened.

**What should be collected after a blue screen?**

Start with the stop code, recent changes, update history, driver clues, disk state, and event timing.

**Can Caisey replace onsite inspection for every crash?**

No. Hardware failures may still need physical work, but Caisey can help structure remote diagnosis and verification.

**Why does history matter for blue screen issues?**

Crash problems often recur. Session history helps compare symptoms and prior repairs across incidents.

- Canonical: https://helpforsupport.com/remote-troubleshooting/blue-screen-errors
- Markdown: https://helpforsupport.com/remote-troubleshooting/blue-screen-errors.md

### Remote troubleshooting for DNS problems

Use Caisey to investigate DNS problems remotely with endpoint network context, approval-aware actions, and audit history.

DNS complaints can look like browser issues, VPN failures, application outages, or general network problems. Caisey helps technicians inspect endpoint context before changing network settings.

#### Separate DNS from the symptom

Technicians can compare name resolution, connectivity, VPN state, adapter settings, and application-specific failures from the selected endpoint.

#### Review network changes

Flushes, adapter changes, or configuration repairs can be handled through approval-aware troubleshooting instead of opaque remote actions.

#### Keep network evidence attached

The session record helps teams understand whether the problem was local, VPN-related, client-site specific, or broader infrastructure.

**What checks help confirm a DNS problem?**

Useful checks include name resolution results, adapter DNS settings, VPN state, browser symptoms, and whether IP connectivity still works.

**Can Caisey help with DNS troubleshooting over VPN?**

Yes. Caisey can help collect endpoint and VPN context in the same troubleshooting session.

**Why record DNS troubleshooting steps?**

Network issues often affect multiple users or repeat later, so preserving evidence helps support teams recognize patterns.

- Canonical: https://helpforsupport.com/remote-troubleshooting/dns-problems
- Markdown: https://helpforsupport.com/remote-troubleshooting/dns-problems.md

### Remote troubleshooting for application crashes

Investigate app crashes remotely with Caisey endpoint context, structured checks, approval-aware fixes, and session history.

Application crashes can come from updates, profiles, plugins, dependencies, permissions, or machine state. Caisey helps technicians gather context from the endpoint and preserve the troubleshooting path.

#### Start with the failing app and machine state

A useful investigation compares the user symptom, process state, recent updates, event clues, profile context, and whether other users or apps are affected.

#### Keep repair actions deliberate

Profile resets, cache cleanup, reinstalls, or configuration changes can be reviewed before running so the technician understands the impact.

#### Verify the app after changes

Caisey sessions can keep the diagnosis, action, and verification notes together for follow-up support.

**What should be checked first when an app keeps crashing?**

Check recent updates, process behavior, profile-specific symptoms, event logs, dependencies, and whether the crash affects other users.

**Can Caisey help troubleshoot line-of-business apps?**

Caisey can help structure endpoint investigation for many application issues, while product-specific vendor fixes still depend on the app.

**Why keep app crash work in a session record?**

A durable record helps future technicians see what was tried and whether the crash pattern changed.

- Canonical: https://helpforsupport.com/remote-troubleshooting/application-crashes
- Markdown: https://helpforsupport.com/remote-troubleshooting/application-crashes.md

### Remote troubleshooting for low disk space

Use Caisey to investigate low disk space remotely with endpoint context, cautious cleanup actions, and durable support history.

Low disk space can break updates, slow applications, and hide larger endpoint problems. Caisey helps technicians inspect storage pressure before approving cleanup or repair actions.

#### Find what is consuming space

Technicians can gather high-level storage context, update cache clues, profile growth, logs, temporary files, and application data patterns.

#### Treat cleanup as a reviewed action

Deleting files or clearing caches can affect users, so Caisey keeps potentially destructive actions inside an approval-aware workflow.

#### Verify headroom after cleanup

The session can record what changed and whether enough free space remains for updates or normal application use.

**What causes low disk space on managed endpoints?**

Common causes include update caches, logs, temporary files, user profile growth, application data, downloads, and failed cleanup routines.

**Should cleanup actions be approved?**

Yes. Any action that deletes or changes user or system files should be reviewed in context before it runs.

**Why document low disk space fixes?**

Storage problems often return, and a record helps teams spot recurring causes or devices that need a larger lifecycle decision.

- Canonical: https://helpforsupport.com/remote-troubleshooting/disk-space-low
- Markdown: https://helpforsupport.com/remote-troubleshooting/disk-space-low.md

### Remote troubleshooting when a Windows service will not start

Investigate Windows services that will not start remotely with Caisey endpoint context, controlled actions, and session history.

A failed service can point to dependency, permission, configuration, update, or resource issues. Caisey helps technicians inspect the endpoint and record the path from diagnosis to verification.

#### Collect service and dependency context

Useful clues include status, startup type, dependency state, recent errors, event timing, account context, and whether related services are also affected.

#### Review restart and repair actions

Restarting or reconfiguring a service can disrupt users, so Caisey keeps sensitive actions visible for approval.

#### Confirm the service stays healthy

The same session can preserve the checks that showed whether the service started and remained available after remediation.

**What should be checked when a Windows service will not start?**

Check service status, startup type, dependencies, event logs, account context, permissions, recent updates, and resource pressure.

**Can Caisey help restart or repair services remotely?**

Caisey can coordinate troubleshooting actions from the browser while preserving approval prompts and audit context for sensitive steps.

**Why keep service troubleshooting history?**

Repeated service failures are easier to diagnose when technicians can compare prior errors, actions, and outcomes.

- Canonical: https://helpforsupport.com/remote-troubleshooting/service-not-starting
- Markdown: https://helpforsupport.com/remote-troubleshooting/service-not-starting.md