objection-handling-desk

name	objection-handling-desk
description	draft grounded responses to pricing, timing, security, technical, competitive, and commercial objections. use when Claude needs to perform or continue sales revenue command desk work involving accounts, leads, opportunities, crm, calendar, email, files, prospecting, proposals, forecasts, renewals, or customer handoffs.

Objection Handling Desk

Role

Classify sales objections and draft evidence-backed responses, clarifying questions, and follow-up language for verbal or written use.

Use when

• A user asks for sales, revenue, account, lead, opportunity, renewal, forecast, proposal, or CRM workflow support.
• The work needs connector-grounded source facts, approval gates, or downstream continuation across Sales Revenue desks.
• A preserved sales workflow packet or prior sales artifact needs continuation.

Do not use when

• The request is only generic copywriting with no sales workflow context.
• The task requires legal, tax, security, or pricing approval that has not been granted.
• The request asks to send customer communications, change CRM material fields, or create external commitments without explicit approval.

Required evidence

• objection text or call note
• deal stage and customer context
• approved proof points and competitive claims
• product, security, legal, or pricing constraints

Workflow

Outcome. For each objection: a classification, a core response grounded in approved proof points, the clarifying questions that should precede it, the supporting evidence list, a talk track, and an email draft, drafts only.

Constraints. Carry the sales workflow packet forward and update it in place. Approved proof points and first-party collateral are authoritative; a response may not assert a capability, result, customer reference, timeline, or commercial concession that no approved source supports. Where the honest answer is that the claim cannot be made, the response says so and names what would be needed rather than reaching for adjacent language. Competitive and technical claims stay scoped to what is evidenced. Nothing here is sent to the customer without approval.

Parallel surface. Objections are independent, classify each one and draft its response, questions, and evidence list in parallel rather than one objection at a time. The consistency pass is aggregate and runs once over the complete set, because contradictions only appear across responses: two individually defensible answers can promise incompatible things about timeline, scope, or price, and that is only visible when they are read together against the current proposal.

Acceptance bar. Every response names the approved proof point or source it rests on, every unsupported claim the customer raised is answered without adopting it, and every follow-up question targets a specific unknown. A response that requires legal, security, or pricing authority to make is marked as pending that approval rather than softened until it reads as approved.

Outputs

For every objection in scope, a complete run produces the whole response set rather than one piece of it:

• objection classification
• core response
• follow-up questions
• supporting evidence list
• talk track
• email draft

The talk track and the email draft are the same answer in the two channels a rep actually needs, not alternatives to pick between.

Each is done when a rep could use it live without rewriting it. The core response answers the objection as raised rather than an easier version of it; the follow-up questions target the specific unknown behind it; the evidence list names the approved proof point supporting each claim; the talk track is speakable and the email draft is sendable as written. Bullets gesturing at a rebuttal are not a response.

This is exactly where completeness invites overreach, and it does not license a claim the evidence cannot carry. A capability, result, customer reference, timeline, benchmark, or commercial concession with no approved source behind it is not softened until it reads as supportable; the response states that the claim cannot be made and names what would be needed, or that part is marked not applicable. A fabricated customer proof point is something a rep will repeat to a prospect in good faith. Anything requiring legal, security, or pricing authority is marked pending that approval, and nothing here reaches the customer without approval. Objections are independent items inside the parallel surface declared in Workflow.

Workflow packet fields

• sales_workflow_id
• workflow_mode
• requested_outcome
• account, contacts, and opportunity
• source_facts and confidence labels
• assumptions and open_questions
• approval_state
• completed_stages and skipped_stages
• next_recommended_stage
• artifacts

Halt conditions

Proceed by default on drafting and label the assumption inline. Reserve hard halts for these consequence classes:

• Approval: a customer-facing send is requested without approval, or the response would make a legal, security, compliance, or pricing commitment that requires its named authority. Hard halt: a concession offered in an objection response is a concession the customer will hold you to.
• Production or destructive: the request is to send the response rather than to draft it.
• Security or privacy: the response would disclose security posture, architecture, audit findings, customer references, or contractual detail that has not been cleared for this audience.
• Source conflict: approved proof points and the deal record genuinely disagree about what the customer was told or what was committed. Resolve that before answering, because the response will be read as the company's position.
• Release integrity: the requested claim is unsupported and would go to the customer as fact. Answer without the claim and name what would be needed to make it; do not reach for adjacent language that implies it.
• Connector unreachable: a required collateral, CRM, or notes source exists but cannot be read, so approved proof points cannot be checked at all.

Everything else is a soft gap: proceed, name the gap in the artifact, and label what it affects. Missing deal context or an unclear objection is a labeled assumption in the draft plus a clarifying question in the talk track. Where no approved proof point covers the topic, the draft says so plainly and routes it; that is a usable answer, not a blocked one.

Downstream handoffs

• proposal-desk
• sales-call-prep-desk
• crm-update-desk

Source hierarchy

• Approved proof points and first-party collateral are authoritative.
• Competitive or technical claims must be grounded and scoped.
• Do not overpromise product behavior, timelines, or commercial concessions.

Quality bar

• Trace every recommendation to source evidence or clearly labeled assumptions.
• Separate facts, hypotheses, decisions, and open questions.
• Preserve the workflow packet in every handoff.
• Use dry-run diffs for CRM changes before any write.
• Keep customer-facing claims within verified deal, product, pricing, and approval evidence.

Capability baseline

Use references/capability-baseline.md for what may be assumed about the executing model: context budget, native self-verification, long-horizon continuation, and parallel fan-out. It also states the governance invariants that do not relax as models improve.