Skip to content
RAY BEHARRY

Agent 22 of 71 · Sales Enablement

Objection Handling Agent

Treat objections like bugs. Find where deals stall, group the stalls into a small number of root objections, fix the highest-impact ones with a sharper Line, a stronger Proof and a better Next Step, and prove the fix worked by watching resolution rate and time to the next meeting.

Agent contract

Use to run the weekly Objection Lab: collect stall moments, cluster by persona and stage, rank by frequency x deal impact, rewrite the top objections as LPNS answers, and ship ESOT updates with a before/after digest.

When it runs

  • The weekly Objection Lab cadence is due (default: Thursday).
  • Field Feedback Analyst reports a new or growing objection cluster.
  • A launch read shows a persona stalling on the same reason across several deals.
  • A trigger-map term (governance, latency, TCO, roadmap risk, migration effort, data residency, change management) spikes in call flags.

What it needs

InputRequiredFrom
Stall moments and objection snippets from callsYesGong (integration)
Opportunity stage history and loss reasonsYesSalesforce (integration)
Current objection blocksYesEnablement Source of Truth (ESOT)
Proof items by personaYesProof Vault
Clustered field feedbackOptionalField Feedback Analyst

How it works

  1. Collect the week's stall moments: the exact buyer words, persona, stage, deal ID and what happened next.
  2. Cluster stalls into root objections by persona and stage, mapping each to the trigger map (governance, latency, TCO, roadmap risk, migration effort, data residency, change management).
  3. Rank clusters by frequency x deal impact (open pipeline value or stage), show the counts, and keep the top three to five.
  4. For each, rewrite the answer as LPNS: a two-sentence Line, one Proof with ProofID or source, and one question or ask that advances the deal.
  5. Mark pricing and roadmap objections for manual owner confirmation; never let a draft promise a discount or a ship date.
  6. Ship proposed ESOT updates plus a 'what changed' digest showing three before/after answers, and route for approval.
  7. Measure prior fixes: objection resolution rate and median days to next meeting for deals that used each revised answer.

What it delivers

Weekly report: ranked objection table (cluster, persona, stage, count, pipeline at risk), LPNS rewrites with ProofIDs, 3 before/after examples, approval status, resolution rate and time-to-next-meeting for last week's fixes.

Output contract: objection-lab-report

Quality bar

  • Clusters show counts and deal IDs; no objection is ranked on anecdote alone.
  • Every rewrite follows LPNS exactly: two sentences, one proof, one advancing question.
  • Before/after examples use real stall wording (redacted), not invented dialogue.
  • Resolution claims are measured_result with window and n.

Hands off

When a person steps in

  • If an objection reveals a real product gap or defect, escalate to the product owner rather than writing around it.
  • If a fix lacks proof, publish the gap in the report and request proof instead of shipping an unproven answer.

Example

Request

“Run this week's Objection Lab for the mid-market pipeline.”

Result

61 stall moments clustered into 6 objections; top 3: migration effort during close (17, $1.2M pipeline), data residency (11), audit-log retention (9). 3 LPNS rewrites shipped as proposals. Last week's TCO fix: resolution 58% vs 39% baseline (n=24); days to next meeting 6 vs 11.

Illustrative example from the package documentation, not a client result.