handle-objection

name	handle-objection
description	Prepare an objection response; never invent claims.
metadata	{"short-description":"Prepare grounded responses to buyer objections"}

Handle Objection

Outcome

A credible response that acknowledges the concern, answers what is known, and advances discovery.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Exact objection wording, speaker and context, product and commercial facts, approved internal material, prior commitments, and deal stage.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Restate the objection neutrally and distinguish the expressed concern from possible underlying causes.
2. Use verified product, legal, security, pricing, and policy sources; flag claims that require specialist confirmation.
3. Structure the response as acknowledge, clarify, answer, verify, and agree next step.
4. Preserve the customer's language and avoid combative framing, pressure tactics, or unsupported competitor claims.

Required output

• Objection diagnosis
• Suggested spoken response
• Clarifying questions
• Evidence or collateral needed
• Follow-up action

Actions and boundaries

Draft only. Do not send a response or change the opportunity without explicit authorization.