Chengeng Objection Handling

What It Solves

In insurance sales, a customer saying too expensive or let me think cannot be treated as a simple price objection and answered with a rebuttal. The harder problem is identifying which stage the objection appears in, whether the gap is information, trust, decision-making conditions, or missing groundwork, and whether a direct pitch would overstate unconfirmed facts. Chengeng Objection Handling is built for deliverable sales coaching tasks. It does not replace the advisor’s final judgment; it turns a vague conversation into a checkable reasoning chain: preserve the customer’s words, locate the stage, analyze the source, inspect prior gaps, then provide strategy and phrasing options.

How It Works

The skill processes input in a fixed order. Typical materials include customer objection wording, chat context, current sales stage, already explained plan, budget, coverage details, service boundaries, and desired tone. Core capabilities include:
- Stage analysis: distinguish whether the customer is stuck on whether to buy, whether they can, or whether it is worth it.
- Source analysis: identify whether the objection comes from insufficient information, insufficient trust, decision relationships, market, company, product, the salesperson, or missing groundwork.
- Groundwork check: find missing trust-building, problem clarification, framework setting, or boundary explanation in earlier conversations.
- Strategy selection: decide whether the current response should acknowledge, explain, add value, set boundaries, or step back.
- Reference phrasing: provide a softer version, standard version, and firmer version so the advisor can choose based on style.
- Prevention actions: trace similar objections back to what should be communicated earlier next time.

The default output usually contains eight sections: situation judgment, sales stage judgment, objection source analysis, groundwork check, response strategy, reference phrasing, prevention plan, and quality check. It runs a quality gate first, separating confirmed facts, reasonable judgments, and items to verify. If key fields are missing, it prioritizes a gap list, minimal follow-up questions, and a low-confidence version instead of producing a final draft. If materials conflict, it stops from presenting definitive conclusions.

Boundaries and Notes

This skill is useful for analyzing sales objections, selecting response strategies, and proposing preventive actions, especially when facts, inferences, and unconfirmed items must be separated. It should not be used to promise sales closure, claims outcomes, underwriting results, medical advice, legal conclusions, or income results, and it should not be mixed with unrelated tasks such as platform configuration or file organization. Usage notes: do not rebut the customer first, do not treat every objection as a price issue, do not use fear, humiliation, or high-pressure tactics, and do not invent cases, product conclusions, or unconfirmed information.