Renewal Prep

作者 Zoominfod07402feb2b9無授權條款收錄於 2026年10月8日更新於 2026年10月8日

Prepare for a renewal by assembling pre-renewal context — value delivered and value moments, risk handles, and stakeholder state — from recent conversations and account_research. Identify the account by ZoomInfo company ID (preferred) or name/domain (triggers a lookup). Use when someone asks "prep me for the Acme renewal", "what's our case for renewal", "what are the risks going into this renewal", or wants a renewal brief. Strictly evidence-based: it does not assume the renewal date or terms; if those are not provided, it asks the user before drafting.

AI 產生的概覽

為客戶帳戶彙整以證據為基礎的續約簡報,涵蓋已交付價值、風險與相關人員。

功能
針對指定帳戶,從對話情報與帳戶研究中蒐集價值時刻、風險與相關人員狀態,產出續約前簡報。它透過 ZoomInfo 公司 ID 或名稱/網域解析帳戶,不擅自假設續約日期、期間與 ARR,而是向使用者詢問,並輸出包含續約理由、風險與因應做法、相關人員以及建議計畫的結構化簡報。此技能僅為指示文件,未附帶指令碼。
適用情境
當有人要求為某個客戶續約做準備、想了解續約理由、想了解續約面臨的風險,或需要一份續約簡報時使用。適用於需要以證據為基礎準備續約溝通之客戶成功與帳戶管理工作。
執行需求
需要存取 conversation_intelligence(至少連接一個會議或電子郵件來源)與 account_research,兩者都會消耗 AI 額度;browse_engagements 為選用項目,需要已啟用的整合。帳戶識別使用 ZoomInfo 公司 ID,或透過 search_companies 依名稱/網域查詢。未包含指令碼。

Renewal Prep

Build the case and the risk map for a renewal: where value has landed, what could derail it, and who decides — grounded in what was actually said.

Prerequisites

conversation_intelligence requires at least one connected meeting or email source; conversation_intelligence and account_research consume AI credits. browse_engagements (optional cadence check) is free and needs an active integration. If no conversation data exists, build from account_research and say the value/risk read is limited, 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.
  • Renewal details (ask if not given) — the renewal date, term, and ARR are often not in ZoomInfo data. Do not assume them. If they matter to the brief and were not provided, ask the user before drafting.

Workflow

  1. Resolve the account. Use the ZoomInfo ID directly, or resolve a name/domain via search_companies.
  2. Confirm the renewal basics. If the renewal date/term/value are not supplied and the brief depends on them, ask the user once. Do not invent a renewal date — an unprompted wrong date is worse than an acknowledged unknown.
  3. Gather evidence. Run conversation_intelligence scoped to the account for value moments (wins, outcomes, positive signals customers voiced), risks and unresolved concerns, and stakeholder engagement. Pull account_research for deal history and relationship context. Optionally use browse_engagements for recent cadence. Keep CI scoped to the account; it sees only the last few engagements.
  4. Assemble the brief. Make the renewal case from evidence (specific value the customer acknowledged), map the risks with handles, and flag any assumption you could not verify.

Output Format

Renewal prep — [Company]

Renewal basics — date, term, ARR if known; otherwise "not provided — confirm with the user" (do not guess).

The case for renewal — value moments and outcomes the customer actually acknowledged, with source moments.

Risks & handles — each risk (with evidence), and a concrete way to address it before the renewal conversation.

Stakeholders — who holds the renewal, champion status, anyone who has gone quiet.

Recommended plan — one to three evidence-based moves leading into the renewal.

Evidence discipline

Build the case from what the customer said, not from generic value claims. Mark assumptions clearly. Where you asked the user for renewal details, attribute them.

When there is no data

If conversation data is unavailable, give the account_research view, note that value moments and conversational risk could not be assessed, and ask the user for the renewal specifics.

來源與署名

來源:Zoominfo/zoominfo-mcp-plugin位於skills/renewal-prep提交d07402f

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架