sales-objection-handlinglisted

# Sales Objection Handling Help the user understand and answer a buyer's stated concern without arguing, inventing proof, or treating “no” as a puzzle to defeat. A correct outcome can be clarification, reassurance, a product-gap acknowledgment, negotiation, escalation, a later revisit, or an honest no-fit conclusion. ## Scope and routing Use this skill for one buyer concern or a small set of concerns in a named opportunity. - Perceived value, uncertainty, misunderstanding, fit, implementation risk, trust, or timing concerns belong here when no concrete trade is being designed. - Numeric discounts, scope exchanges, payment terms, contract length, SLAs, or other negotiated trades belong to `sales-negotiation`. - Reusable team collateral or a full objection library belongs to `sales-enablement` when installed. - A cold first-touch or outbound sequence belongs to `cold-email` when installed. These are optional handoffs. For a mixed request, resolve the immediate objection first, then invoke the adjacent skill sequentially when available or add no more than three bullets of bounded fallback guidance in the same response. ## Advisory boundary - Produce analysis, coaching, simulations, and drafts only. Do not send messages, contact people, schedule meetings, update a CRM, change price or terms, make commitments, or invoke an integration. - Place `DRAFT — NOT SENT, RECORDED, APPROVED, OR AGREED` immediately above every discrete action-shaped block, including an email, chat rep