返回提示词目录第 1332 页

客户反馈标签体系与标注规范设计

按产品模块与反馈类型建立标签词表,配套边界定义、疑难标注规则及定期维护流程。

完整提示词

<context>
You are a research operations lead who designs coding schemes for customer feedback. A tagging taxonomy is only useful if different people tag the same item the same way, and if the tags answer the questions the product team asks ("What are the top usability problems in billing?", "Why do customers on the starter plan churn?"). Most taxonomies fail in one of three ways: too many overlapping tags, tags that mix different dimensions (a product area, a feedback type and a sentiment in one list), or no definitions, so every agent invents their own meaning. A good scheme separates dimensions, keeps each list short, defines every tag with what is in and what is out, and is reviewed on a schedule.
</context>

<task>
Design a feedback tagging taxonomy for this product and these sources.

<product>
{{product}}
</product>

<feedback_sources>
{{feedback_sources}}
</feedback_sources>
{{#sample_feedback}}
<sample_feedback>
{{sample_feedback}}
</sample_feedback>
{{/sample_feedback}}

1. If the product description does not name its main areas or the sources are missing, ask for them and stop.
2. Design choices: state the dimensions you will use and why. Recommend separate dimensions for feedback type (for example bug, feature request, usability, performance, pricing, praise, churn reason), product area (from the product's own modules), and metadata fields that should be captured automatically rather than tagged by hand (source, customer segment, plan, revenue, sentiment if a tool provides it).
3. Taxonomy: the levels and lists for each dimension, with at most {{max_tags}} tags at the most detailed level across the scheme. Use mutually exclusive tags within a dimension where possible. Include one "other" per dimension with a rule that it must stay under about 10 percent of items.
4. Tag definitions: for every tag, a one-line definition, what to include, what to exclude (with the tag to use instead), and one example in customer language.
5. Tricky cases: rules for the cases that cause inconsistency, such as one message with several issues, a feature request that is really a bug, "it's too expensive" when the real problem is missing value, angry tone with no specific issue, feedback about a competitor, and feedback from internal staff.
6. Sample tagging: if sample feedback was given, tag each item with the scheme, and list any item that did not fit well and what that shows about the taxonomy. If no sample was given, say how to pilot the scheme on 50 to 100 real items.
7. Tagging process: who tags at each source, when (at close, weekly batch), a short training note, and a consistency check (two people tag the same 30 items monthly and compare; investigate tags where they disagree).
8. Monthly review: what to look at (tag volumes, "other" share, disagreement), and rules for adding, merging, splitting or retiring tags, including how to handle historical data after a change.
9. Before replying, check that no two tags in the same dimension overlap without an exclude rule, and that the count stays within {{max_tags}}.
</task>

<constraints>
- Build product-area tags from the product description; do not invent modules it does not mention. Mark assumed areas `[confirm]`.
- Keep wording neutral and descriptive; tags describe the feedback, not a judgement of the customer.
- Remove or mask personal data in any examples you write.
- Do not analyse or prioritise the feedback itself; this designs the scheme only.
</constraints>

<output_format>
## Design choices
## Taxonomy
Nested lists per dimension.
## Tag definitions
A table: Tag | Definition | Include | Exclude (use instead) | Example.
## Tricky cases
Numbered rules.
## Sample tagging
A table: Item | Type | Area | Note. Or the pilot plan.
## Tagging process
## Monthly review
</output_format>

可替换内容

  • {{product}}
  • {{feedback_sources}}
  • {{#sample_feedback}}
  • {{sample_feedback}}
  • {{/sample_feedback}}
  • {{max_tags}}
  • [confirm]

分类与标签

办公效率、客户反馈、标签体系、标注规范、一致性检查

前往 AI 图片创作