大多数 App 都用同样三句模板回评论，让品牌听起来像外包客服。下面 15 个 Prompt 生成具体、有人味的回复，常常能让 1-2 星的人改评分。覆盖：愤怒型、bug 报告、误判功能、功能请求、好评、最被忽略的 3 星中段。
适合哪些场景
自己管评论的移动 App 创始人、App 工作室的客服负责人、关注评分速率的增长团队、负责 App Store / Play Store 回复的客服运营。
什么时候不建议这样写 Prompt
不要用来回你还没读完的评论。也不要在平台上跟用户争退款或表达法律立场——那些请走平台外。
Prompt 结构公式
评论回复 Prompt 一定带这六个要素：
- 角色：让 AI 扮演谁（资深 PM / 独立创始人 / 产品设计师 / 独立开发者 / 增长负责人）。
- 上下文：阶段（想法 / MVP / 增长 / 规模化）、团队规模、流量或 ARR、平台（web / iOS / Android）、受众、限制。
- 目标：一个具体交付物——一段 PRD、一组用户故事、一个实验设计、一篇上线公告。
- 限制：时间线（本 sprint / 本季度）、要砍的范围、不能动的东西（现有流程、计费、合规）。
- 输出格式：表格、清单、可贴 ticket 的 JSON、或带标签的段落，能直接粘到 Linear / Notion / Jira。
- 示例 / 信号：1-2 份你欣赏的参考或竞品、加 1 个想避开的反例。
这套 Prompt 适合用在哪
- 1-2 星愤怒型挽回
- Bug 报告但信息不全
- 3 星”差一点”提分尝试
- 功能请求确认
- 5 星回复不浪费这一刻
15 个可直接复制的 Prompt 模板
1. 1 星愤怒挽回
单条杠杆最大的模板。目标：让他们再试并改评分。
You are a founder responding personally to a 1-star review of {app}. The user is angry. Write a reply that: (1) starts by acknowledging the specific frustration, no apology theater, (2) names what you understand happened in one sentence, (3) offers one concrete action you took or will take, (4) gives a direct contact ({email}), (5) does NOT ask them to update the rating. Less than 120 words. Voice: human, slightly humble.
Review: {paste}可替换变量： app, email, review
优化建议： 太官腔时追加：“Rewrite so a friend would believe this came from a real person, not a support queue.”
2. Bug 但信息不全
The reviewer reports {app} is broken but gives no detail. Write a reply that asks for exactly 3 specific items ({device + OS, steps to reproduce, error text or screenshot}) without sounding like a form. Less than 90 words. End with one warmth signal.
Review: {paste}3. 误判功能（其实存在）
Reviewer claims {app} lacks {feature} but the feature exists. Write a reply that: never says "you are wrong", points to where the feature lives (1 line), and includes a tip that makes them feel smarter for finding it. Less than 90 words.
Review: {paste}4. 功能请求确认
Reviewer asks for {feature}. Write a reply that: thanks them in 1 line (no gushing), tells them honestly whether it is planned / under consideration / not on the roadmap, and asks one curious question to learn more. Less than 80 words.
Review: {paste}5. 价格抱怨
Reviewer says {app} is too expensive or refused to pay. Write a reply that: validates the price concern, names what the price includes in 1 sentence, mentions any trial / free tier honestly, and does NOT discount. Less than 100 words.
Review: {paste}6. 3 星”差一点”提分
Reviewer gave 3 stars and listed 1-2 things they wished worked better. Write a reply that addresses each point concretely, mentions what is in the next release, and treats them as the most valuable reviewer you have (because 3-star is the lift opportunity). Less than 110 words.
Review: {paste}7. 5 星回复换转介绍
Reviewer left 5 stars and a short positive note. Write a reply that: thanks them by referencing one specific thing they said (NOT "we appreciate it"), shares one small upcoming feature they will love, and softly invites them to share with a friend. Less than 80 words.
Review: {paste}8. 隐私 / 数据顾虑
Reviewer raised a privacy concern about {app}. Write a reply that: states exactly what data is and is not collected (no marketing fluff), links to the privacy policy, and offers a way to opt-out or delete their data. Less than 130 words. Voice: precise, non-defensive.
Review: {paste}9. 崩溃 / 数据丢失
Reviewer reports the app crashed and lost data. Write a reply that: acknowledges the severity, asks 3 diagnostic questions, offers a manual recovery path if any exists, and gives a direct human contact. Less than 130 words. Voice: urgent, accountable.
Review: {paste}10. 非英语评论本地化
Below is a 1-2 star review in {language}. Write a reply in the same language that: addresses the specific complaint, names a concrete action, and offers a contact. Then provide the English back-translation so the team can audit. Less than 100 words in the target language.
Review: {paste}11. 竞品对比
Reviewer compares {app} unfavorably to a competitor. Write a reply that: never names the competitor, acknowledges what they value about that experience, points to one specific thing {app} does that the competitor does not. Less than 100 words.
Review: {paste}12. 喷子 / 恶意评论
Reviewer left an abusive or trolling review of {app}. Write a brief, neutral, public-facing reply that: does not engage with the abuse, states the facts, leaves a contact for legitimate concerns. Less than 60 words. Note: also recommend whether to report the review under {Apple, Google} guidelines.
Review: {paste}13. 大事故时的回复包
We had a {duration}-hour outage that triggered a wave of 1-star reviews. Write 4 variants of a public reply addressing the outage: (a) acknowledge + facts, (b) what we fixed, (c) what we are changing process-wise, (d) credit / compensation if any. Each less than 110 words.14. 更新打破了功能
Reviewer is upset that an update changed or removed a feature they used. Write a reply that: validates the disruption, explains why honestly in 1 sentence, offers a workaround, and asks if they would join a small group to test the next revision. Less than 110 words.
Review: {paste}15. 批量语气审计
Below are 10 draft review replies our team wrote this week. Audit them on 5 dimensions: (1) reads human, (2) addresses the specific review, (3) has a concrete action or fact, (4) honest about limitations, (5) ends warmly without being saccharine. Score each 1-5 and rewrite any below 3.
{paste 10 replies}容易踩的坑
- 所有 1 星贴同一段模板——读者一眼看穿。
- 道歉五次却没有任何具体动作。
- 在回复里要求改评分——商店都不鼓励，且显得急切。
- 在公开评论里和用户辩论——即便他错了，读者是潜在用户。
- 隔几天才回——用户在 48 小时内才会去看你是否回了。
- “非常感谢”这种通用结尾，毫无评论里的具体内容。
- 完全不回 5 星——那是深化拥护的最好机会。
优化技巧
- 永远用同一语言回复评论。
- 把评论里的某句话引一句回去——证明你真的读了。
- 尽量带一个有日期的具体动作（下个版本、本周、周二之前）。
- 回复保持在 130 字以内；移动端读不动长回复。
- 48 小时内回——评分上调强相关于及时回应。
- 维护公司公开语气指南，每周跑模板 15。
- 同一 bug 出现 5+ 条评论时——先修 bug 再回复；只回不修会烧光信任。
FAQ
- 回复真的能改评分吗？: 会，对 2-3 星尤其明显。行业数据显示 48 小时内用心回复，约有 5-15% 会改评分。
- 能直接请用户改评分吗？: 不能。Apple 不鼓励，Play 用户也反感。把体验改好，他们会自己改。
- 5 星都要回吗？: 选有具体内容的回。具体型 5 星回复往往直接转化为转介绍。
- 多快该回？: 48 小时内。超过一周，评分回升效应明显下降。
- 能删掉我不同意的评论吗？: 只能通过商店的正式举报通道，且仅在违反指南（辱骂、刷量、跑题）时。其他情况只能回复。