设计客户反馈收集与流转流程
为销售、支持和成功团队设计反馈表单、去重路由、状态通知与月度检查机制,形成可执行的处理流程。
完整提示词
<context>
You design the pipe that carries customer feedback from customer-facing teams to product decisions. The people who use it are sales, support and success staff with little time: if submitting takes more than two minutes or nothing ever comes back, they go back to messaging their favourite PM, and the loudest account wins.
What good looks like: one front door; each submission records the customer's problem and evidence, not only a feature name; duplicates become extra evidence on one record; every item has an owner and a status the submitter can see; and someone checks monthly that feedback actually reaches decisions.
Company size: {{company_size}}
</context>
<task>
<current_situation>
{{current_situation}}
</current_situation>
<teams_and_tools>
{{teams_and_tools}}
</teams_and_tools>
1. State four or five principles for this company (one front door, problems over solutions, evidence over volume, every submitter hears back, the process serves decisions).
2. Design the intake form, placed inside a tool submitters already use. Required fields, kept to six or fewer: customer or account, segment or plan, the problem in the customer's words, what they were trying to do, impact (blocked, workaround, nice to have) with any revenue or deal at stake, and a link or verbatim quote. Optional: product area guess, deadline the customer mentioned. No field asking for a priority score.
3. Deduplication and linking: who checks new items against existing problem records, how a duplicate is merged as extra evidence (account, quote, revenue) rather than closed, and how the combined record shows the count of accounts and segments.
4. Routing rules: from product area to an owning team or PM, with a fallback owner for unclear items, and how urgent items (bugs, security, data loss, contractual commitments) leave the feedback path for the incident or support process.
5. Service levels and statuses: acknowledge within 2 working days, triage within 10 working days; statuses such as received, needs info, under review, planned, not planned now, shipped. Say who notifies the submitter at each change and give a two-line template for "not planned now".
6. Health check, monthly: share triaged within the service level, share of items with a customer and evidence attached, median days from submission to decision, share of roadmap items with linked feedback, and a quick pulse of submitters (does it feel worth submitting?).
7. Fit the process to the size: under-50 a shared form and weekly 30-minute triage by one PM; 50-500 a form in the existing tool and a product ops or rotating triage owner; over-500 per-area queues, a shared taxonomy with an owner and quarterly calibration.
8. Rollout over four to six weeks: pilot with one customer-facing team, migrate open items, announce, and retire the old channels by redirecting rather than ignoring them.
</task>
<constraints>
- Use the tools named; do not recommend buying a new tool unless the current ones cannot hold a form, a record and a status, and then describe the capability needed without naming vendors.
- Do not invent volumes or team names; mark gaps as [X].
- Keep customer personal data to what is needed to follow up; say to check the company's privacy rules for storing customer quotes.
- If the teams or tools are not described, ask for them and stop.
</constraints>
<output_format>
## Principles
Four or five bullets.
## Intake form
Table: field | required | type (dropdown, text, link) | help text shown to submitter.
## Deduplication and linking
Numbered steps and who does them.
## Routing rules
Table: product area or signal | owner | fallback | exits to (incident, support, none).
## Service levels and statuses
Table: status | meaning | who sets it | submitter notified (yes/no) | target time. Then the "not planned now" template.
## Health check
Table: measure | how to calculate | target | source.
## Rollout
Week-by-week checklist.
## Questions
What to confirm.
</output_format>可替换内容
- {{company_size}}
- {{current_situation}}
- {{teams_and_tools}}
- [X]
分类与标签
办公效率、客户反馈、产品运营、团队协作、流程设计