大多数 App 都用同样三句模板回评论，让品牌听起来像外包客服。下面 15 个 Prompt 生成具体、有人味的回复，能让 1-2 星的用户改分。一项针对开发者回复的研究（Hassan 等）发现：收到回复后有 4.4% 的用户上调了评分，没收到回复的只有 0.7%——大约 6 倍的提升；回复了至少一半评论的 App，90 天内评分能提升约 0.3-0.7 星。覆盖：愤怒型、bug 报告、误判功能、功能请求、好评，以及最被忽略、却最有提分空间的 3 星中段。
TL;DR
- Apple 单条回复最多 5,970 个字符，Google Play 上限只有 350 个字符。同一条评论，两个平台得写成完全不同的草稿——下面每个 Prompt 都接收目标平台。
- 48 小时内回。Apple 回复最多 24 小时才公开显示；Play 上，用户只在你第一次回复时收到推送和邮件通知（之后编辑不再通知）。
- 永远别在回复里要求改评分。把问题修好、引用用户原话、给一个带日期的具体动作，他们会自己改分。
- 模板 1（1 星愤怒）和模板 6（3 星”差一点”）提分杠杆最大。每周跑一次模板 15 保持语气真诚。
适合哪些场景
自己管评论的移动 App 创始人、App 工作室的客服负责人、关注评分速率的增长团队、负责 App Store / Play Store 回复的客服运营。在 App Store Connect 回复需要 Account Holder、Admin 或 Customer Support 角色；在 Google Play 则需要有回复权限的开发者账号成员。
什么时候不建议这样写 Prompt
不要用来回你还没读完的评论。也不要在公开平台上跟用户争退款或表达法律立场——那些请转到邮件或工单系统，走平台外处理。
两个平台的限制速览（截至 2026 年 6 月）
| 限制项 | App Store（Apple） | Google Play |
|---|---|---|
| 回复字符上限 | 5,970 | 350 |
| 公开显示时间 | 最多 24 小时 | 几乎即时 |
| 是否通知用户 | 不直接通知 | 仅第一次回复推送 + 邮件 |
| 每条评论可回次数 | 一条可编辑的回复 | 多次，仅第一次会通知 |
| 谁能回 | Account Holder / Admin / Customer Support | 有回复权限的开发者账号成员 |
| 之后可否编辑 / 删除 | 可以（编辑会被标注） | 可以 |
350 字符的 Play 上限是最硬的约束：逼你把”认同”和”那一个动作”放最前面，其余全砍。每个 Prompt 都有一个 [platform] 槽位，让模型按平台调整篇幅。
评论回复的结构
一条好的评论回复按顺序包含五个动作：
- 认同具体的不满——把用户的某句话引一句回去，让对方知道你读了。
- 一句话说清发生了什么，诚实，不要道歉表演。
- 给出一个具体动作，已做或将做，有日期就带上日期。
- 留一个真人联系方式（邮箱或支持链接），平台外的事走这里。
- 温和收尾，不要求改评分，也不要太肉麻。
这套 Prompt 适合用在哪
- 1-2 星愤怒型挽回
- Bug 报告但信息不全
- 3 星”差一点”提分尝试
- 功能请求确认
- 5 星回复不浪费这一刻
15 个 Prompt 模板
任何当前主流模型都能很好地处理这些——我们在 GPT-5.5、Claude Sonnet 4.6、Gemini 3.1 Pro 上都测过（均为 2026 年 6 月版本）。论语气，Claude Sonnet 4.6 默认写出来最不官腔。把 {platform} 换成 App Store（最多 5,970 字符）或 Google Play（硬上限 350 字符），让模型按平台控制篇幅。发送前把每个 {...} 占位符换成你的真实内容。
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 星——那是深化拥护的最好机会。
优化技巧
- 永远用同一语言回复评论（模板 10 处理这件事）。
- 把评论里的某句话引一句回去——证明你真的读了。
- 尽量带一个有日期的具体动作（下个版本、本周、周二之前）。
- 按平台控制篇幅：Play 回复压在 350 字符内；App Store 同样建议控制在约 130 字内，因为移动端用户只会扫读。
- 48 小时内回——评分上调与及时回应强相关。
- 维护一份公开语气指南，每周跑一次模板 15。
- 同一 bug 出现 5+ 条评论时——先上线修复再回复；只回不修会烧光信任。
FAQ
- 回复真的能改评分吗？ 会，对 2-3 星尤其明显。一项针对开发者回复的分析（Hassan 等）显示，收到回复后 4.4% 的用户上调了评分，没回复的只有 0.7%；回复了至少一半评论的 App，90 天内评分约提升 0.3-0.7 星。
- 能直接请用户改评分吗？ 不要。Apple 的回复规范要求回复保持尊重、不含营销或垃圾内容，Play 用户也反感这种话。把体验改好，他们会自己改。
- 开发者回复能写多长？ Apple 单条最多 5,970 字符，Google Play 上限 350 字符（截至 2026 年 6 月）。先写 Play 版本——能塞进 350 字符，到哪都够用。
- 用户什么时候能看到我的回复？ App Store 上回复最多 24 小时才显示，且不会直接通知评论者。Google Play 上用户会收到推送和邮件，但只在你第一次回复时——之后编辑不再通知。
- 5 星都要回吗？ 选有具体内容的回，纯表情就跳过。具体型 5 星回复往往直接转化为转介绍。
- 能删掉我不同意的评论吗？ 不能。你可以编辑或删除自己的回复，但要让用户的评论被移除只能通过商店的正式举报通道，且仅在违反指南（辱骂、刷量、跑题）时。其他情况只能回复。
相关阅读
- App Store listing Prompt
- App 引导文案 Prompt
- Release notes Prompt
- 流失分析 Prompt
- App Store 审核常见问题
- 用 AI 写 App 审核申诉草稿：重新提交而不像求情
- 用 AI 回复 App Store 评论，又快又不像机器人
- Product / App / Startup Prompt 总目录