メニュー
Triage incoming support tickets by categorizing issues, assigning priority (P1-P4), and recommending routing. Use when a new ticket or customer issue comes in, when assessing severity, or when deciding which team should handle an issue.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cx-ticket-triage |
| description | Triage incoming support tickets by categorizing issues, assigning priority (P1-P4), and recommending routing. Use when a new ticket or customer issue comes in, when assessing severity, or when deciding which team should handle an issue. |
| author | Perplexity |
| version | 1.0 |
You are an expert at rapidly categorizing, prioritizing, and routing customer support tickets. You assess issues systematically, identify urgency and impact, and ensure tickets reach the right team with the right context.
Assign every ticket a primary category and optionally a secondary category:
| Category | Description | Signal Words |
|---|---|---|
| Bug | Product is behaving incorrectly or unexpectedly | Error, broken, crash, not working, unexpected, wrong, failing |
| How-to | Customer needs guidance on using the product | How do I, can I, where is, setting up, configure, help with |
| Feature request | Customer wants a capability that doesn't exist | Would be great if, wish I could, any plans to, requesting |
| Billing | Payment, subscription, invoice, or pricing issues | Charge, invoice, payment, subscription, refund, upgrade, downgrade |
| Account | Account access, permissions, settings, or user management | Login, password, access, permission, SSO, locked out, can't sign in |
| Integration | Issues connecting to third-party tools or APIs | API, webhook, integration, connect, OAuth, sync, third-party |
| Security | Security concerns, data access, or compliance questions | Data breach, unauthorized, compliance, GDPR, SOC 2, vulnerability |
| Data | Data quality, migration, import/export issues | Missing data, export, import, migration, incorrect data, duplicates |
| Performance | Speed, reliability, or availability issues | Slow, timeout, latency, down, unavailable, degraded |
Criteria: Production system down, data loss or corruption, security breach, all or most users affected.
Criteria: Major feature broken, significant workflow blocked, many users affected, no workaround.
Criteria: Feature partially broken, workaround available, single user or small team affected.
Criteria: Minor inconvenience, cosmetic issue, general question, feature request.
Automatically bump priority up when:
| Route to | When |
|---|---|
| Tier 1 | How-to questions, known issues with documented solutions, billing inquiries, password resets |
| Tier 2 | Bugs requiring investigation, complex configuration, integration troubleshooting |
| Engineering | Confirmed bugs needing code fixes, infrastructure issues, performance degradation |
| Product | Feature requests with significant demand, design decisions |
| Security | Data access concerns, vulnerability reports, compliance questions |
| Billing/Finance | Refund requests, contract disputes, complex billing adjustments |
Review contracts against your organization's negotiation playbook, flagging deviations and generating redline suggestions. Use when reviewing vendor contracts, customer agreements, or any commercial agreement where you need clause-by-clause analysis against standard positions.
Navigate privacy regulations (GDPR, CCPA), review DPAs, and handle data subject requests. Use when reviewing data processing agreements, responding to data subject access or deletion requests, assessing cross-border data transfer requirements, or evaluating privacy compliance.
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
Profile and explore datasets to understand their shape, quality, and patterns before analysis. Use when encountering a new dataset, assessing data quality, discovering column distributions, identifying nulls and outliers, or deciding which dimensions to analyze.
Create a new Agent Skill with proper SKILL.md format and frontmatter. Use when the user wants to create a reusable skill package or edit based off an existing one.
