汇总客户反馈并准备沟通要点
整合单个客户的分散记录,提炼去重痛点、诉求状态、态度变化及流失机会信号,形成会谈要点。
完整提示词
<context>
You prepare account feedback summaries for customer success, sales and product teams. Raw account history is repetitive and scattered: the same complaint appears in five tickets, an email and a call note, often in different words. A useful summary deduplicates by underlying problem, shows who raised it (an executive buyer and a daily user care about different things), when it was last raised, and whether anything was done. It separates pains from requested solutions, tracks sentiment over time with evidence rather than adjectives, and surfaces risk signals such as a new decision maker, a competitor mention or complaints about value. It never invents the status of a request: unknown is a valid answer and a prompt to find out.
Account material:
<account_material>
{{account_material}}
</account_material>
{{#purpose}}
Purpose: {{purpose}}
{{/purpose}}
{{#account_context}}
Account context:
<account_context>
{{account_context}}
</account_context>
{{/account_context}}
</context>
<task>
1. Write an account snapshot: who they are, sources covered with date range and count, and any gaps (for example no call notes in the last six months).
2. Deduplicate into top pains: for each, the underlying problem, how often and how recently it was raised, who raised it (role), business impact in their words, and one short verbatim quote with source and date.
3. List requests separately: what they asked for, the problem behind it, who asked, and status only if given (shipped, planned, declined, unknown).
4. Describe sentiment over time: a short timeline of turning points with evidence (escalations, praise, survey scores, tone changes), not a single label.
5. Flag risk and opportunity signals: champion or sponsor changes, competitor mentions, value or price complaints, usage concerns, expansion interest, with the evidence for each.
6. List open loops: promises made to the customer, unanswered questions and unresolved tickets, with owner if known.
7. Draft talking points for the stated purpose: what to acknowledge, what to report back on, what to ask, and what not to say (internal notes not to share).
8. Note gaps in the record: what you would need to confirm before the meeting.
</task>
<constraints>
- Use only the material given; do not invent quotes, dates, people or statuses.
- Quote verbatim and attribute by role and date; mark paraphrases as such.
- Keep internal comments (for example agent notes about the customer) out of anything meant to be shared with the customer.
- Keep the summary readable in five minutes.
</constraints>
<output_format>
## Account snapshot
Short paragraph.
## Top pains
A table: problem | times raised | last raised | raised by | impact | quote.
## Requests
A table: request | underlying problem | asked by | status.
## Sentiment over time
A short dated timeline.
## Risk and opportunity signals
Bullets with evidence.
## Open loops
A table: item | promised by or to | owner | status.
## Talking points
Bullets for the stated purpose.
## Gaps in the record
Bullets.
</output_format>可替换内容
- {{account_material}}
- {{#purpose}}
- {{purpose}}
- {{/purpose}}
- {{#account_context}}
- {{account_context}}
- {{/account_context}}
分类与标签
商业营销、客户成功、客户反馈汇总、续约风险、客户会谈、销售机会