原文核对：2026-10-13 · 中文正文 · 英文提示词与演示
场景定位
综合阶段、活动、通话、邮件、安全采购和账户背景，解释阻碍、既往尝试、升级路径与下一步。
- 难度
- 中级
- 时间跨度
- 30 分钟
适合用于
- 近期有活动却不推进的交易。
- 需区分客户阻碍与内部流程或跟进缺口的销售团队。
- 需要明确客户行动和负责人的升级审阅。
相关工具
追踪 CRM 阶段、活动和时间。
读取账户、安全采购和旧计划。
Google Drive ↗审阅交易与内部升级会话。
Slack ↗检查解释停滞的邮件历史。
Gmail ↗起步提示词
英文原文 · 可复制后按实际材料修改
Diagnose why [deal or account] is stalled.
Use the opportunity stage history, closed activities, call transcripts, email threads, deal threads, security, legal, or procurement notes, and account context I provide.
Return:
- the most likely blocker and supporting evidence
- prior attempts and what changed
- customer, technical, legal, or procurement dependencies
- escalation path and owners
- the next customer-facing move
- missing context and risks
Separate sourced facts from inference. Draft follow-up language only; do not send it or update CRM records.追溯完整历史
当前阶段并非全部原因，综合历史和材料以区分客户、技术、法律及内部流程问题。
- 定义交易、时间窗口和支持的决策。
- 提供阶段、活动、转录、邮件、会话、安全采购和账户材料。
- 先建时间线再判断根因。
- 审阅证据、既往尝试、依赖、升级路径和下一步。
- 客户跟进发送前由交易负责人批准。
保持事实和时间边界；原因不确定时列出可区分解释的最小客户或内部检查。
形成恢复计划
就阻碍达成共识后，制定窄范围计划，逐步明确负责人、依赖和证明点。
官方提示词
英文原文 · 可复制后按实际材料修改
Create a recovery plan for this stalled deal.
Include:
- confirmed blocker and supporting evidence
- one or two hypotheses still to test
- customer-facing next step
- internal dependency and owner
- escalation path
- target date and proof of progress
- follow-up language for review
Do not send the message, update CRM, or promise a date that the sources do not support.展开英文原文对照
Give ChatGPT stage history, closed activities, call transcripts, emails, deal threads, security or procurement notes, and account context, then ask it to explain the blocker, prior attempts, escalation path, and next action.
Trace the stall across the full deal history
The visible stage is rarely the whole blocker. Give ChatGPT stage history, closed activities, calls, emails, deal threads, security or procurement notes, and account context so it can distinguish customer, technical, legal, and internal process issues.
- Define the deal, time window, and decision the diagnosis should support.
- Attach stage history, activity, transcripts, email, threads, security or procurement notes, and account context.
- Ask ChatGPT to build a timeline before naming a root cause.
- Run the starter prompt and review evidence, prior attempts, dependencies, escalation path, and next move.
- Have the deal owner approve any customer-facing follow-up before sending it.
Keep the diagnosis factual and time-bounded. If the blocker is uncertain, list the smallest customer or internal check that would distinguish the competing explanations.
Turn diagnosis into a recovery plan
After the blocker is agreed, ask ChatGPT to create a narrow recovery plan with owners, dependencies, and a proof point for each step.
官方提示词
英文原文 · 可复制后按实际材料修改
Create a recovery plan for this stalled deal.
Include:
- confirmed blocker and supporting evidence
- one or two hypotheses still to test
- customer-facing next step
- internal dependency and owner
- escalation path
- target date and proof of progress
- follow-up language for review
Do not send the message, update CRM, or promise a date that the sources do not support.