AI Playbook

Device health investigation

Assess the current health and operational risk of one managed device.

Copy this prompt

Replace the bracketed values, then paste it into an AI client connected to Stackyapper.

Run the "Device health investigation" playbook using Stackyapper.

Inputs
- device: [Device name or identifier]
- symptom: [Optional reported symptom or concern] (optional)

Objective
Assess the current health and operational risk of one managed device.

Required evidence
- Managed devices

Use when available
- Device alerts
- Device activity
- Device policies
- Directory devices
- Asset lifecycle
- Service tickets

Procedure
1. Collect current device state, health, check-in, and resource evidence.
2. Review alerts, recent activity, and assigned policy.
3. Correlate identity enrollment, lifecycle, and ticket history.
4. Explain likely causes, operational risk, missing telemetry, and the safest next diagnostic action.

Return
- Current health
- Alerts and recent changes
- Policy and lifecycle context
- Likely cause
- Recommended next action

Use only evidence available through the Stackyapper Apps and permissions connected to this AI client. If required evidence is unavailable, say what is missing before continuing. Do not guess or make changes in connected systems.

Before you paste

Replace every bracketed value in the prompt. Delete an optional input line if it does not apply.

  • device: Device name or identifier. (required)
  • symptom: Optional reported symptom or concern. (optional)

What Stackyapper will use

The exact tools depend on the Apps connected to your workspace and the current user's permissions.

  • Managed devices (required)
  • Device alerts (used when available)
  • Device activity (used when available)
  • Device policies (used when available)
  • Directory devices (used when available)
  • Asset lifecycle (used when available)
  • Service tickets (used when available)

What you'll get

  • Current health
  • Alerts and recent changes
  • Policy and lifecycle context
  • Likely cause
  • Recommended next action

How it works

  1. Collect current device state, health, check-in, and resource evidence.
  2. Review alerts, recent activity, and assigned policy.
  3. Correlate identity enrollment, lifecycle, and ticket history.
  4. Explain likely causes, operational risk, missing telemetry, and the safest next diagnostic action.