Objection Handler

Provides structured response frameworks for the objections every CSM faces. Not scripts -- frameworks that help you understand what the customer is actually saying, what is driving it, and how to respond in a way that addresses the real concern, not just the surface objection.

How to Use

Provide:

• The objection (what the customer said)
• The context (when they said it, what was happening in the conversation)
• The account context (health, renewal proximity, relationship strength)
• What you think is really driving it (the stated reason is often not the real reason)

The Objection Diagnosis Framework

Every objection has a surface statement and an underlying driver. The response must address the driver, not just the statement.

Pricing Objections

"It is too expensive"

Feature Gap Objections

"You do not have X feature"

Adoption Objections

"My team is not using it"

Value Objections

"I am not sure we are getting enough value"

Relationship Objections

"We do not feel supported"

Response Structure

For every objection, the response follows three steps:

1. Acknowledge -- show you heard them. Do not argue, defend, or immediately counter. "I understand your concern about the pricing" or "That is fair feedback about the support experience"
2. Diagnose -- understand what is really driving it. Ask a question before responding. "Can you help me understand what is behind that?" or "What would need to be true for you to feel confident in the value?"
3. Respond -- address the underlying driver with a specific action. Not a promise, not a defence -- an action. "Let me build the ROI analysis and present it next week" or "I am going to review the support history and come back with a specific improvement plan by Friday"

Output

For each objection, the skill produces:

• The objection diagnosed (what the customer said vs. what is likely driving it)
• 2-3 response options calibrated to the likely driver
• Questions to ask before responding (to confirm the diagnosis)
• What not to say (common mistakes for this objection type)
• Follow-up actions (what to do after the conversation)

Quality Gates

• Did you diagnose before responding? Responding to the surface objection without understanding the driver addresses the wrong problem
• Is the response specific to this account? "The product delivers great value" is generic. "Your team saved 340 hours this quarter through workflow automation" is specific
• Does the response include an action, not just words? Every objection response should end with something you commit to doing -- not just something you said
• Did you avoid being defensive? The instinct when challenged is to defend. The effective response is to acknowledge and redirect

Principles

• Objections are information, not attacks. A customer who raises a concern is telling you what matters to them. That is more valuable than a customer who says nothing and quietly leaves
• The first response to any objection is a question, not an answer. "Can you tell me more about that?" or "What would need to change?" gives you the information to respond effectively
• Never argue with the customer's perception. If they feel the product is too expensive, telling them they are wrong does not change their feeling. Showing them the value might
• The best objection handling happens before the objection. A customer with strong value evidence, deep adoption, and a multi-threaded relationship raises fewer objections. Prevention is more effective than response