Objection Blocker Tracker

by Zoominfod07402feb2b9No licenseListed Oct 8, 2026Updated Oct 8, 2026

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-generated overview

Tracks open objections and blockers on a deal across recent calls and shows how each has evolved.

What it does
This skill surfaces the objections, concerns and blockers raised in an account's or contact's recent conversations and classifies each as new, recurring, escalating or addressed. It reports who raised each item, when, how it has moved across calls, and where it currently stands, then names the one or two items most likely to stall the deal. It reasons only over the last few engagements, so it presents recent movement rather than a complete deal history.
When to use it
Use it when someone asks what objections are still open with a given account, what is blocking a deal, or how a specific concern such as security has evolved. It also fits a blocker check before a forecast or a next call.
Requirements
Requires the conversation_intelligence capability, which needs at least one connected meeting or email source and consumes AI credits, plus browse_engagements for scoping calls, which needs an active integration. Scope is given as a ZoomInfo ID or a name resolved through search_companies or search_contacts. Ships no scripts.

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.

Source and attribution

Source:Zoominfo/zoominfo-mcp-plugininskills/objection-blocker-trackerat commitd07402f

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Objection Blocker Tracker Agent Skill | SourceWeft