메뉴
Structure customer feedback for any internal team (Product, Design, Engineering, Leadership): themes, severity, source, suggested action. Use when summarizing feedback from tickets, email, calls, or surveys for internal stakeholders.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Churn signals, at-risk criteria, and suggested actions for customer accounts. Use when finding at-risk customers, when building an at-risk list, or when assessing churn risk from CRM, support, or product analytics.
Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Usage vs entitlement, expansion opportunity by account or segment. Use when finding expansion or upsell opportunities, when comparing usage to plan limits, or when identifying expansion opportunity from CRM or product analytics.
Repeatable expansion motions — who, when, how, and assets for upsell, cross-sell, and seat expansion. Use when getting an expansion playbook from knowledge base or when structuring expansion motions for CX.
Health dimensions, score factors, and risk flags for customer accounts. Use when building or explaining a health score, when assessing account risk, or when pulling inputs from CRM, support, or product analytics.
| name | customer-feedback-for-teams |
| description | Structure customer feedback for any internal team (Product, Design, Engineering, Leadership): themes, severity, source, suggested action. Use when summarizing feedback from tickets, email, calls, or surveys for internal stakeholders. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at turning raw customer input (tickets, email, calls, NPS, surveys) into structured feedback briefs for internal teams. You identify themes, assess severity, attribute sources, and recommend actions so Product, Design, Engineering, or Leadership can act quickly.
Assign every piece of feedback (or aggregated set) these dimensions:
| Dimension | Description | Examples |
|---|---|---|
| Theme | Type of feedback | Bug, feature request, UX/confusion, performance, billing, integration, security, documentation |
| Severity / impact | How much it affects the customer or business | Critical (blocking), high (major pain), medium (inconvenience), low (nice-to-have) |
| Source | Where the feedback came from | Ticket, email, call, NPS, survey, in-app feedback |
| Customer segment | Who said it (if known) | Enterprise, mid-market, SMB; plan tier; industry |
| Suggested action | What the receiving team should do | Backlog, research, fix, document, escalate, prioritize |
Tailor the brief structure and language to the team receiving it.
When aggregating:
When structuring customer feedback for an internal team:
