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 从公开仓库中收录这些内容。

举报或申请下架