Objection Blocker Tracker

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

Track the open objections and blockers on a deal and how they have evolved across recent calls. Uses conversation_intelligence over an account's or contact's recent engagements. Identify the account or contact by ZoomInfo ID (preferred) or name (triggers a lookup). Use when someone asks "what objections are still open with Acme", "what's blocking this deal", "how has the security concern evolved", or wants a blocker check before a forecast or a next call. Reasons over the last few engagements only, so it tracks recent movement rather than full deal history.

AI 產生的概覽

追蹤某筆交易中尚未解決的反對意見與阻礙,並呈現其在近期通話中的演變。

功能
此技能會整理某個客戶或聯絡人在近期對話中提出的反對意見、疑慮與阻礙,並將每一項歸類為新出現、反覆出現、升高或已處理。它會說明每一項由誰在何時提出、跨通話如何變化、目前狀態為何,並指出最可能拖垮交易的一到兩項。它只根據最近幾次互動進行推理,因此呈現的是近期動向,而非完整的交易歷程。
適用情境
當有人詢問某個客戶還有哪些未解決的反對意見、是什麼在阻礙交易,或某個具體疑慮(例如安全性問題)如何演變時使用。也適合在預測或下次通話前做阻礙檢查。
執行需求
需要 conversation_intelligence 能力,該能力要求至少連接一個會議或電子郵件來源,並會消耗 AI 額度;另需 browse_engagements 來篩選通話,且需有已啟用的整合。範圍以 ZoomInfo ID 提供,或透過 search_companies / search_contacts 解析名稱。不附任何指令碼。

Objection & Blocker Tracker

Surface the concerns standing between you and the deal, and show whether each is getting better or worse.

Prerequisites

conversation_intelligence requires at least one connected meeting or email source and consumes AI credits. browse_engagements (to scope or pick calls) requires an active integration and is free. If no conversation data exists, say so rather than reporting "no objections" (the absence of data is not the absence of objections).

Input

Provided via $ARGUMENTS:

  • Scope (required) — an account or contact (ZoomInfo ID, or a name to resolve).
  • Focus (optional) — e.g. "just pricing", "anything technical", "security and procurement". Narrows the read.

Workflow

  1. Resolve scope. If no account or contact was supplied, ask the user which one before proceeding. Use a ZoomInfo ID directly, or resolve a name via search_companies / search_contacts.
  2. Extract objections and blockers. Run conversation_intelligence scoped to the account or contact. Ask it to list the objections, concerns, and blockers raised across recent conversations, who raised each, when, and how it was last left. Keep CI scoped to one ID; it sees only the last few engagements and cannot count or topic-search, so present this as recent movement, not a complete tally.
  3. Track the trajectory. For each item, classify status: newly raised, addressed/resolved, recurring (keeps coming back), or escalating. Tie each to the source moments. Do not record an objection the conversation does not support, and do not mark something resolved without evidence it was.

Output Format

Open objections & blockers — [Account / Contact]

From the last few engagements (through [date]).

For each, most pressing first:

[Objection / blocker] — [status: new | recurring | escalating | addressed]

  • Raised by: [who, when]
  • Evolution: how it has moved across calls (e.g. "raised in discovery, partially addressed in the demo, resurfaced on the last call").
  • Where it stands: the current state and what would move it.

Close with Most likely to stall the deal — the one or two items to resolve first, with why.

When there is no data

If conversation data is unavailable, report that open objections cannot be tracked from conversations and point the user to their ZoomInfo admin.

來源與署名

來源:Zoominfo/zoominfo-mcp-plugin位於skills/objection-blocker-tracker提交d07402f

授權條款: 無授權條款

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

檢舉或申請下架