Ae Cs Handoff

作者 Zoominfod07402feb2b9无许可证收录于 2026年10月8日更新于 2026年10月8日

Produce an AE-to-CS handoff brief — everything the incoming CSM needs from the sales conversations. Builds an engagement timeline, then runs conversation_intelligence in parallel on the key engagements to pull requirements, success criteria, stakeholders and how they like to work, and the relationship state. Identify the account by ZoomInfo company ID (preferred) or name/domain (triggers a lookup). Use when someone says "build the handoff for Acme", "what does the CSM need to know", "prep the post-sale transition", or closes a deal that needs a clean handoff.

AI 生成的概览

根据销售对话生成 AE 到 CS 的交接简报,涵盖需求、承诺、相关方与风险。

功能
该技能为接手客户成功经理整理售后交接简报。它解析客户账户、构建互动时间线、深入读取信号最强的销售互动,并汇总成一份可直接交付 CSM 的文档,内容包括交易摘要、成功标准、已作出的承诺、相关方、未决事项与风险,以及建议的第一步行动。它会区分承诺与愿景,并将每项内容归因到来源对话。
适用场景
适用于交易达成并需要顺利交接给客户成功团队时,或有人询问 CSM 需要了解该客户的哪些信息时。也适合准备售后交接或为指定客户生成交接简报的请求。
运行要求
需要启用的日历、邮件或会议集成来构建互动时间线,并需要至少一个已连接的对话来源用于深入读取。对话、账户与联系人研究步骤会消耗 AI 额度。账户识别使用 ZoomInfo 公司 ID 或通过名称/域名查询。不附带脚本,仅为说明文档。

AE-to-CS Handoff Brief

Capture what was promised, what success looks like, and who the people are — so the CSM starts from context, not a cold account.

Prerequisites

browse_engagements (timeline) requires an active calendar/email/meeting integration; conversation_intelligence (the deep read) requires at least one connected source and consumes AI credits, as do account_research and contact_research. If no conversation data exists, build the structural handoff from research and flag that the conversational detail (requirements, working style) is missing, pointing the user to their ZoomInfo admin.

Input

Provided via $ARGUMENTS:

  • Account (required) — ZoomInfo company ID (preferred), or a name/domain to resolve via search_companies.
  • Context (optional) — the product sold, deal size, go-live timing, anything the CSM specifically needs.

Workflow

  1. Resolve the account. Use the ZoomInfo ID directly, or resolve a name/domain via search_companies.
  2. Build the timeline. Call browse_engagements (account-scoped) for the sales-cycle engagements; identify the few that carry the most signal (discovery, key demos, negotiation, commitments). Limit to roughly the 2-4 highest-signal engagements — each gets its own conversation_intelligence call in step 3, which costs AI credits, so do not fan out across the whole timeline. Keep their engagement IDs.
  3. Deep-read the key engagements in parallel. Run conversation_intelligence on those engagement IDs (one CI call per engagement) for stated requirements and success criteria, commitments made to the customer, decision-makers and how they like to work, and any sensitivities. Pull account_research and contact_research for the structural picture. CI sees only the last few engagements, so anchor on the key ones rather than expecting full history.
  4. Assemble the handoff. Synthesize a CSM-ready brief. Distinguish what was promised (must be honored) from what was aspirational. Attribute each requirement and commitment to the conversation it came from. Do not invent commitments.

Output Format

AE-to-CS handoff — [Company]

Deal summary — what was sold, why they bought (the core problem and desired outcome), in 2-3 lines.

Success criteria — how the customer defined success, in their words, with sources.

Commitments made — what the AE promised the customer (and any timelines). These transfer to the CSM.

Stakeholders — per key person: role, influence, champion/skeptic, and how they like to work (cadence, format, sensitivities) where the conversations show it.

Open items & risks — anything unresolved at close that the CSM inherits.

Recommended first move — the CSM's best opening action, tied to the above.

When there is no data

If conversation data is unavailable, give the research-based account and stakeholder structure, and flag that requirements, commitments, and working style could not be captured from conversations.

来源与署名

来源:Zoominfo/zoominfo-mcp-plugin位于skills/ae-cs-handoff提交d07402f

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架