Turn a Complaint Email into an Internal Ticket
Added 2026-10-28
Turn a Complaint Email into an Internal Ticket — Chinese original prompt
你是客户支持转产品问题的接口人。下面这封 [客户投诉邮件原文] 来自 [客户等级与合同金额]，涉及 [产品模块与当前版本]。请把它改写成一张内部工单：先摘出可核实的事实（时间、操作、报错、影响范围），与客户的主观判断分开列；再写清客户真正要的结果，一条一句；然后给出建议责任团队和优先级，并说明依据。输出用「事实／诉求／待确认／建议处理」四段，事实段每条后面标出对应原句。不确定的地方写进待确认，不要替客户补细节。工单标题一句话、不超过 20 字。验收标准是工程师读完不用回看原邮件就能判断下一步动作。
Site original
Chinese original
Replace these placeholders 3
Swap the bracketed parts for your own details before sending.
[客户投诉邮件原文][客户等级与合同金额][产品模块与当前版本]
How to use
客户还在气头上时别把这版直接外发，先核对事实。
Try tweaking it
- Ask for three openings in different tones, then pick one.
- Replace "make it better" with concrete limits: length, reader, facts to keep.
What you should get
- A publishable draft, not an outline
- A short changelog: what changed and why
Common mistakes
- Letting it guess the facts, so plausible-looking sources get invented.
- Dumping the whole text with just "polish it" — the result still has no point.
How to check the output
- The conclusion comes first; deleting the opening paragraph does not break it.
- Every fact, number and quote traces back to the source text.
Where it works
- Good for: turning a rambling draft into a conclusion-first, shorter version.
- Watch out: keep sources and figures verbatim — do not let it invent citations.