Skip to content
RAY BEHARRY

Agent 24 of 71 · Sales Enablement

Sales Talk Track Agent

Give sellers words that work in the moment. Translate approved ESOT blocks into talk tracks per role and stage, write the three tagged intro variants used in launches, and answer live seller questions with a two-sentence line, one cited proof and one question that moves the deal, refusing to improvise beyond what ESOT supports.

Agent contract

Use to write role- and stage-specific talk tracks, the A/B/C first-call intros, discovery questions and live LPNS answers drawn only from ESOT, with confidence labels, citations and an honest 'insufficient data'.

When it runs

  • A seller or manager asks how to answer a specific buyer question or objection.
  • Launch Experiment Designer requests intros A/B/C for a Three-Intro Test.
  • ESOT blocks for a persona or stage change and talk tracks reference the old wording.
  • A new seller cohort is onboarding and needs a role talk-track pack.

What it needs

InputRequiredFrom
Approved ESOT blocksYesEnablement Source of Truth (ESOT)
Buyer question, persona, stage and deal contextYesYou
Persona cards and proof preferencesOptionalBuyer Personas
Approved kernels for intro variantsOptionalMessage Memory
Voice cardOptionalBrand Voice Memory

How it works

  1. Classify the request: live answer, intro variant, role talk track or discovery question set; capture persona and stage.
  2. Retrieve matching ESOT blocks by persona, stage and theme tags; ignore any block that is proposed, expired or unapproved.
  3. If no approved block covers the question, return 'insufficient data', name the gap, and log it for the Objection Lab.
  4. Compose the LPNS: a two-sentence Line in the buyer's language, one Proof with its ESOT- or PRF- citation, and one Next Step question or ask.
  5. Attach a confidence label (high, medium, low) derived from the cited blocks' confidence and expiry.
  6. Apply hard rails: pricing and roadmap answers state 'requires confirmation from <owner>' and give no numbers or dates beyond ESOT.
  7. For intros, write A/B/C variants that differ only by narrative, tag each with its CRM variant value, and store talk tracks in templates/lpns-answer.md format.

What it delivers

LPNS card: question, persona, stage, Line (2 sentences), Proof (1 cited ESOT-/PRF- ID), Next Step (1 question or ask), confidence label, citations, hard-rail notes; intro packs list A/B/C with CRM variant values.

Output contract: lpns-answer

Quality bar

  • Line is two sentences maximum; Proof is exactly one cited item; Next Step is one question or ask.
  • Every factual statement traces to an approved, unexpired ESOT block.
  • 'Insufficient data' is returned instead of a plausible guess when ESOT has no coverage.
  • Pricing and roadmap answers carry the manual-confirmation rail every time.

Hands off

When a person steps in

  • If a seller asks for a discount commitment, contract term or ship date, refuse to supply one and route to the named pricing or roadmap owner.
  • If cited blocks contradict each other, return low confidence and escalate the conflict to the ESOT owner.

Example

Request

“A CISO asks 'where is our data stored and can we keep it in the EU?' in an evaluation call. What do I say?”

Result

Line: 'All customer data for EU tenants is stored and processed in Frankfurt and Dublin. You choose the region at setup and it can be locked by policy.' Proof: ESOT-0114 (trust center residency page, PRF-0031). Next Step: 'Would it help if our security lead walked your team through the DPA this week?' Confidence high.

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