原文核对：2026-10-13 · 中文正文 · 英文提示词与演示
场景定位
把 Slack、问卷、issue 跟踪工具、客服记录或研究笔记中的反馈交给 ChatGPT Work。它可以将重复问题整理成可审阅的 Sheet 或 Doc，保留证据、设计影响、待解决问题和明确的后续行动。
- 难度
- 入门
- 时间跨度
- 30 分钟
适合用于
- 需要跨 Slack、问卷、issue、客服和研究资料审阅反馈的团队。
- 需要清晰主题、支持证据和后续行动的产品决策。
相关工具
阅读获准访问的反馈频道或会话链接。
Slack ↗阅读 issue、PR 评论和讨论串。
GitHub ↗阅读缺陷或功能需求队列。
Linear ↗阅读反馈文档、导出文件和文件夹，然后创建 Google Doc 或 Sheet。
Google Drive ↗起步提示词
英文原文 · 可复制后按实际材料修改
Analyze feedback on [feature or product area] from [time period] using @Slack, @GitHub, @Linear, and @Google Drive. Include any relevant support tickets, surveys, and research notes.
Group the feedback into clear themes, show the supporting evidence, and tell me what needs attention.
Put the findings in a Google Sheet or Doc I can review. Draft any follow-ups, but don't post or send them.开始之前
产品反馈可能分散在 Slack、问卷导出文件、issue 跟踪工具、客服记录和研究笔记里。向 ChatGPT Work 提供要审阅的来源、产品范围和日期区间。它可以把重复问题归类到 Sheet 或 Doc 中，供团队核对后再决定下一步。
可在 Work 网页端或桌面端通过已连接应用和云端文件启动此流程。如果来源在本机，请先上传导出文件，或使用桌面应用。
你会得到什么
下面的示例使用请求审核队列的问卷导出文件、客服记录、反馈会话和研究笔记。首轮整理重复出现的问题；后续再将一个过于宽泛的主题拆成两个更清晰的决策。
查看官方对话演示（英文）
ChatGPT Work conversation showing feedback analysis from four sources, supporting evidence, and a theme refinement.
用户
Analyze feedback on the request-review queue from the last 30 days using @Slack, @GitHub, @Linear, and @Google Drive. Include any relevant support tickets, surveys, and research notes. Group the feedback into clear themes, show the supporting evidence, and tell me what needs attention. Put the findings in a Google Sheet or Doc I can review. Draft any follow-ups, but don't post or send them.
ChatGPT
Files · Reviewed the survey, support export, feedback thread, and research notes
思考 18 秒I found three repeated problems across all four sources. The highest-risk issue is that requests can look ready even when a date conflict is only visible after opening them. • Conflicts are hidden in the queue: eight mentions across four sources. Show conflict status in the list and distinguish Ready from Needs attention. • Bulk approval can include blocked requests: four mentions across four sources. Skip blocked requests by default or warn before approval. • Reviewers lose their place and can't isolate work: ten mentions across four sources. Preserve search and filters and offer a Needs attention view. The table includes affected users, evidence IDs, confidence, open questions, and follow-ups. These counts are repeated mentions in a small sample, not product-wide incidence rates.
用户
Separate filter-reset issues from requests to group blocked work. Keep the recommendations short.
ChatGPT
Files · Refined the theme table and checked the supporting evidence
Done. I split the navigation theme into two distinct problems: • Search and filters reset on return: four mentions. Preserve queue state when reviewers open and return from a request. • Blocked and unreviewed work is hard to isolate: six mentions. Compare an inline filter with a grouped Needs attention view. The first two themes and their evidence are unchanged. The table now has four reviewable themes, with no issues created or assigned.
工作步骤
- 提供反馈来源、产品范围和审阅时间段。
- 要求按主题归纳重复反馈，并为每个主题保留支持链接或记录 ID。
- 创建 Google Sheet 或 Doc，列出受影响用户、置信度、待解决问题，以及需要的决策或后续行动。
- 先审阅摘要，再把主题转成 Slack 更新或 issue 草稿。
首次分析使用本页起步提示词，然后细化过于宽泛、缺乏证据或混合不同问题的主题。
把已审阅主题转成下一份草稿
已有摘要后，可以要求 Work 拆分宽泛主题、补充缺失证据、起草 Slack 更新，或将已审阅主题整理成 issue 草稿。明确受众和需要作出的决策，让下一步更清楚。
官方提示词
英文原文 · 可复制后按实际材料修改
Use the feedback summary to draft a short update for [team or channel]. Include the main themes, the evidence, and what we should do next. Don't post it.持续维护反馈频道
如果 Slack 频道或 issue 队列不断收到新报告，可以让 Work 定期检查。保持相同的审阅边界，避免未经批准就把新反馈发布为消息、issue 或人员指派。
官方提示词
英文原文 · 可复制后按实际材料修改
Check [feedback channel, issue tracker, or survey] every weekday. Tell me when a new theme appears, an existing issue gets worse, or we need to make a decision. Keep the feedback summary up to date, but don't post or send anything.展开英文原文对照
Give ChatGPT Work feedback from Slack, surveys, issue trackers, support, or research notes. It can group repeated problems into a reviewable Sheet or Doc with evidence, design implications, open questions, and clear follow-ups.
Before you start
Product feedback might live in Slack, survey exports, issue trackers, support records, or research notes. Give ChatGPT Work the sources, product area, and date range to review. It can group repeated problems into a Sheet or Doc the team can check before deciding what to do next.
Start this workflow in Work on the web or desktop with connected apps and cloud files. Attach a local export first, or use the desktop app, when the source lives on your computer.
What to expect
Here is an example using a survey export, support records, a feedback thread, and research notes for a request-review queue. The first pass groups the repeated problems; the follow-up splits a broad theme into two clearer decisions.
查看官方对话演示（英文）
ChatGPT Work conversation showing feedback analysis from four sources, supporting evidence, and a theme refinement.
用户
Analyze feedback on the request-review queue from the last 30 days using @Slack, @GitHub, @Linear, and @Google Drive. Include any relevant support tickets, surveys, and research notes. Group the feedback into clear themes, show the supporting evidence, and tell me what needs attention. Put the findings in a Google Sheet or Doc I can review. Draft any follow-ups, but don't post or send them.
ChatGPT
Files · Reviewed the survey, support export, feedback thread, and research notes
思考 18 秒I found three repeated problems across all four sources. The highest-risk issue is that requests can look ready even when a date conflict is only visible after opening them. • Conflicts are hidden in the queue: eight mentions across four sources. Show conflict status in the list and distinguish Ready from Needs attention. • Bulk approval can include blocked requests: four mentions across four sources. Skip blocked requests by default or warn before approval. • Reviewers lose their place and can't isolate work: ten mentions across four sources. Preserve search and filters and offer a Needs attention view. The table includes affected users, evidence IDs, confidence, open questions, and follow-ups. These counts are repeated mentions in a small sample, not product-wide incidence rates.
用户
Separate filter-reset issues from requests to group blocked work. Keep the recommendations short.
ChatGPT
Files · Refined the theme table and checked the supporting evidence
Done. I split the navigation theme into two distinct problems: • Search and filters reset on return: four mentions. Preserve queue state when reviewers open and return from a request. • Blocked and unreviewed work is hard to isolate: six mentions. Compare an inline filter with a grouped Needs attention view. The first two themes and their evidence are unchanged. The table now has four reviewable themes, with no issues created or assigned.
How it works
- Give Work the feedback sources, product area, and time period to review.
- Ask it to group repeated feedback into themes and keep supporting links or IDs with each theme.
- Create a Google Sheet or Doc with affected users, confidence, open questions, and the decision or follow-up needed.
- Review the summary before turning any theme into a Slack update or issue draft.
Use the starter prompt on this page for the first pass, then refine any theme that is too broad, missing evidence, or mixing separate problems.
Turn a reviewed theme into the next draft
Once the summary exists, ask Work to split a broad theme, add missing evidence, draft a Slack update, or turn a reviewed theme into an issue draft. Name the audience and decision so the next step is clear.
官方提示词
英文原文 · 可复制后按实际材料修改
Use the feedback summary to draft a short update for [team or channel]. Include the main themes, the evidence, and what we should do next. Don't post it.Keep a feedback channel current
For a Slack channel or issue queue that keeps getting new reports, ask Work to check it on a schedule. Keep the same review boundaries so new feedback does not become an unapproved post, issue, or assignment.
官方提示词
英文原文 · 可复制后按实际材料修改
Check [feedback channel, issue tracker, or survey] every weekday. Tell me when a new theme appears, an existing issue gets worse, or we need to make a decision. Keep the feedback summary up to date, but don't post or send anything.