Triage service ticket

When to use

Use this guide when you need to investigate a service ticket, identify likely cause and impact, and recommend the next action using current evidence.

What you need

Replace these bracketed values before you copy the prompt.

• ticket idRequired

  Ticket identifier in the connected PSA.

• objectiveOptional

  Optional focus or question from the operator.

Information used

Stackyapper uses only the Apps and permissions available to the current user.

• Service ticketsRequired
• Customer recordsIf available
• Managed devicesIf available
• Device alertsIf available
• User directoryIf available
• DocumentationIf available

Expected output

• Evidence consulted
• Missing or unavailable sources
• Likely cause and impact
• Confidence
• Recommended next action

Steps

1. Load the ticket, notes, customer, affected entities, and stated impact.
2. When a device is implicated, collect its current state and relevant alerts.
3. When a user or Microsoft 365 service is implicated, collect only relevant user evidence.
4. Search approved documentation for a matching runbook or known issue.
5. Stop when evidence is sufficient; distinguish facts, inference, missing evidence, and recommended next action.