Hand a long ticket history to another team in one summary
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and hand a long ticket history to another team in one summary.
LLMPrompt
Prompt
Copied 0
Summarize the support thread below for {{escalation_team}}, who have not seen any of it. They should be able to act on your summary without reading the thread.
Thread:
"""
{{thread}}
"""
Use this format, with these exact labels:
Problem: one sentence on what is broken or being asked, in plain words.
Customer impact: who is affected and how badly, using only facts from the thread.
Timeline: up to 5 dated bullets of what happened, oldest first.
Already tried: each fix that was attempted, and what happened.
Promised to the customer: any commitment made, by whom and when.
Open question: the one decision or answer needed from {{escalation_team}}.
Keep it under 200 words. Copy error messages, order numbers and IDs exactly as written.
Leave out greetings, apologies and back-and-forth that does not change the facts, and do not speculate about the cause.
The summary should be usable after one read: for example, an engineer should be able to start reproducing a bug straight away.
If the thread is unclear or silent on one of the labels, write "Not stated in the thread" for it. Do not guess.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/summarize-support-thread-for-escalation - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "summarize-support-thread-for-escalation",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}