Triage a backlog of support tickets
Sorts a batch of tickets by what they actually need, groups the duplicates, and pulls out anything urgent that is hiding in the queue.
Turns a messy customer thread into an escalation an engineer can act on: steps to reproduce, impact, and what is known versus assumed.
Works with Claude, ChatGPTUpdated 2026-09-27
Use this when a support thread needs to go to engineering. Escalations bounce back when they arrive as a forwarded conversation, and each round trip costs the customer another day.
Write the escalation in five sections.
1. SUMMARY
One sentence: what is broken, for whom.
2. STEPS TO REPRODUCETell us who you are and all 50 prompts open up, with a PDF of the whole library sent to your inbox.
This opens all 50 prompts, emails you the PDF, and lets us follow up once. No newsletter signup, and we do not share your details.
Sorts a batch of tickets by what they actually need, groups the duplicates, and pulls out anything urgent that is hiding in the queue.
Builds a timeline from the record, separates the trigger from the conditions that let it matter, and proposes fixes at the right level.
New prompts as they go up, plus founder essays on shipping AI systems. ~2 emails / month.
Prompts get you started. If you want this wired into how your team actually works, see what we do.