AI Playbook
Ticket response preparation
Prepare an accurate customer-facing ticket update from current evidence without sending it.
Copy this prompt
Replace the bracketed values, then paste it into an AI client connected to Stackyapper.
Run the "Ticket response preparation" playbook using Stackyapper.
Inputs
- ticket id: [Ticket identifier]
- message type: [Optional update type such as acknowledgement, progress, or resolution] (optional)
Objective
Prepare an accurate customer-facing ticket update from current evidence without sending it.
Required evidence
- Service tickets
Use when available
- Ticket history
- Managed devices
- Device alerts
- User directory
- Documentation
Procedure
1. Review the request, audience, current status, and technician notes.
2. Verify relevant history, device, alert, identity, and runbook evidence.
3. Draft a concise response that separates confirmed progress from pending work; do not send it.
Return
- Draft response
- Facts included
- Claims requiring verification
- Internal-only context
- Suggested follow-up time
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)message type: Optional update type such as acknowledgement, progress, or resolution. (optional)
What Stackyapper will use
The exact tools depend on the Apps connected to your workspace and the current user's permissions.
- Service tickets (required)
- Ticket history (used when available)
- Managed devices (used when available)
- Device alerts (used when available)
- User directory (used when available)
- Documentation (used when available)
What you'll get
- Draft response
- Facts included
- Claims requiring verification
- Internal-only context
- Suggested follow-up time
How it works
- Review the request, audience, current status, and technician notes.
- Verify relevant history, device, alert, identity, and runbook evidence.
- Draft a concise response that separates confirmed progress from pending work; do not send it.