AI Playbook

Ticket assignment and prioritization

Recommend the queue, priority, and technician profile for a service ticket.

Copy this prompt

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

Run the "Ticket assignment and prioritization" playbook using Stackyapper.

Inputs
- ticket id: [Ticket identifier]

Objective
Recommend the queue, priority, and technician profile for a service ticket.

Required evidence
- Service tickets

Use when available
- Customer records
- Customer contacts
- Ticket history
- Device alerts
- Documentation

Procedure
1. Assess reported impact, urgency, affected scope, customer, and SLA evidence.
2. Use customer, contact, history, alert, and runbook context to refine the recommendation.
3. Recommend assignment and priority with rationale; do not update the ticket.

Return
- Recommended priority
- Recommended queue
- Required technician skills
- Rationale
- Missing routing evidence

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.

  • ticket id: Ticket identifier. (required)

What Stackyapper will use

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

  • Service tickets (required)
  • Customer records (used when available)
  • Customer contacts (used when available)
  • Ticket history (used when available)
  • Device alerts (used when available)
  • Documentation (used when available)

What you'll get

  • Recommended priority
  • Recommended queue
  • Required technician skills
  • Rationale
  • Missing routing evidence

How it works

  1. Assess reported impact, urgency, affected scope, customer, and SLA evidence.
  2. Use customer, contact, history, alert, and runbook context to refine the recommendation.
  3. Recommend assignment and priority with rationale; do not update the ticket.