メニュー
Summarize support tickets, chats, and customer threads into issue, impact, status, owner, and next response. Use for customer service handoffs, escalation triage, and support backlog review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Analyze CSAT, NPS comments, reviews, and support feedback for sentiment, recurring themes, customer pain, and service improvement actions. Use for customer support and CX feedback reviews.
Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.
Turn business data, KPI movement, or experiment results into a clear narrative using the what-so what-now what structure, audience calibration, and action-oriented insight. Use when leaders need a data-backed brief, dashboard storyline, or metric interpretation. Do not use for raw statistical modeling with no communication deliverable.
Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents.
Draft clear, professional business emails from rough notes, context, or instructions. Handles cold outreach, internal updates, client responses, and escalation drafts. Use when the work is routine email writing with known context and audience. Do not use for sensitive legal notices, formal regulatory correspondence, or board-level communication without review.
Summarize meeting notes or transcripts into decisions, action items, owners, risks, and follow-up messages. Use after meetings when raw notes need a clean recap.
| name | codexkit-support-ticket-summarizer |
| description | Summarize support tickets, chats, and customer threads into issue, impact, status, owner, and next response. Use for customer service handoffs, escalation triage, and support backlog review. |
| version | 1.0.0 |
| category | review |
Extract the customer's stated issue, affected product or service, timeline, and expected outcome.
Classify impact:
Preserve important technical details, order IDs, screenshots mentioned, error messages, account tier, and prior troubleshooting.
Suggest the next action for support, engineering, customer success, or billing. Do not promise resolution time unless provided.
Write a customer-facing response when requested. Keep it empathetic, specific, and honest about unknowns.
| Input | Required | Format |
|---|---|---|
| Ticket or chat text | Yes | Thread, transcript, notes |
| Customer context | Recommended | Plan, segment, account owner |
| Current status | Optional | New, waiting, escalated, resolved |
| Internal constraints | Optional | SLA, support policy, escalation path |
## Ticket Summary - [Ticket ID / Customer]
### Customer Issue
[Plain-language issue]
### Impact And Priority
[Impact level, urgency, rationale]
### Evidence
- [Relevant facts, error messages, dates]
### Work Done So Far
- [Troubleshooting steps]
### Recommended Next Step
| Owner | Action | Deadline / SLA | Notes |
|-------|--------|----------------|-------|
### Customer Response Draft
[Optional response]
| Check | Question |
|---|---|
| Correctness | Does the summary match what the customer actually said and what support already tried? |
| Completeness | Are issue, impact, evidence, status, owner, and next step all present? |
| Context-fit | Does priority reflect SLA, customer tier, and operational impact? |
| Consequence | Could this summary cause the next agent to miss a contractual or customer commitment? |
Prompt: "Summarize this Zendesk ticket for escalation to engineering. Include issue, impact, evidence, and a customer response draft."
Bad pattern: "Customer is upset and app is broken." Good pattern: "Customer cannot export invoices for account ACME-142 since May 12. Error: 403 on export endpoint. Support reproduced on admin role."