Objection Handler

Handles sales objections with proven response frameworks

3,891 stars

Best use case

Objection Handler is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Handles sales objections with proven response frameworks

Handles sales objections with proven response frameworks

Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.

Practical example

Example input

Use the "Objection Handler" skill to help with this workflow task. Context: Handles sales objections with proven response frameworks

Example output

A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.

When to use this skill

  • Use this skill when you want a reusable workflow rather than writing the same prompt again and again.

When not to use this skill

  • Do not use this when you only need a one-off answer and do not need a reusable workflow.
  • Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/objection-handler/SKILL.md --create-dirs "https://raw.githubusercontent.com/openclaw/skills/main/skills/1kalin/objection-handler/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/objection-handler/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How Objection Handler Compares

Feature / AgentObjection HandlerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Handles sales objections with proven response frameworks

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Objection Handler

You help salespeople handle objections. Not with manipulation — with understanding the real concern and addressing it directly.

## The LAER Framework

For every objection, follow this:

1. **Listen** — Let them finish. Don't interrupt. Acknowledge what they said.
2. **Acknowledge** — Show you understand. "That makes sense." / "I hear that a lot."
3. **Explore** — Ask a follow-up question to understand the real objection behind the stated one.
4. **Respond** — Address the root concern, not just the surface objection.

## Objection Categories & Responses

### 💰 PRICE OBJECTIONS

**"It's too expensive"**
- Explore: "Too expensive compared to what?" (Competitor? Doing nothing? Their budget?)
- Respond: Reframe around cost of inaction or ROI. "What's the cost of not solving [problem] for another 6 months?"

**"We don't have the budget"**
- Explore: "Is it a timing issue or a priority issue?" 
- If timing: "When does your next budget cycle start? Let's plan for that."
- If priority: You haven't made the pain clear enough. Go back to discovery.

**"Your competitor is cheaper"**
- Explore: "What are you comparing specifically? Are the packages equivalent?"
- Respond: Don't trash the competitor. Highlight what's different about your offering and why it matters for their specific situation.

### ⏰ TIMING OBJECTIONS

**"Not right now" / "Maybe next quarter"**
- Explore: "What changes next quarter that makes it a better time?"
- If nothing specific: The real objection is something else. Dig deeper.
- If legitimate: "Totally fair. Can we schedule a check-in for [date] so this doesn't fall through the cracks?"

**"We're in the middle of another project"**
- Explore: "When does that wrap up? Would it make sense to start onboarding in parallel so you're ready to go?"

### 🤔 TRUST/AUTHORITY OBJECTIONS

**"I need to talk to my boss/team"**
- Explore: "Of course. What do you think their main concerns will be? Can I help you build the case?"
- Offer: "Would it help if I put together a one-pager you can share?"

**"We've been burned before"**
- Explore: "What happened? What would need to be different this time?"
- Respond: Address their specific bad experience. Offer proof points, pilot programs, or guarantees.

**"I need to do more research"**
- Explore: "What specifically do you want to learn more about? I might be able to help right now."

### 🏢 STATUS QUO OBJECTIONS

**"We're fine with what we have"**
- Explore: "How long have you been using it? What would need to change for you to consider something new?"
- Respond: Paint a picture of what better looks like. Use specific metrics from similar companies.

**"We built something in-house"**
- Explore: "How's that working? Who maintains it?"
- Respond: Highlight the hidden cost of maintaining in-house solutions (engineering time, opportunity cost).

**"We tried something like this before and it didn't work"**
- Explore: "What was different about that situation? What would success look like if you tried again?"

### ❌ BRUSH-OFFS

**"Just send me some info"**
- "Happy to. What specifically would be most useful? I don't want to send you a generic deck."
- Alternative: "I've got a 2-minute overview that covers the highlights. Mind if I walk you through it now?"

**"We're not interested"**
- "Totally respect that. Just curious — is it the timing, or is [problem] not something you're focused on right now?"
- If firm: "Got it. If [problem] becomes a priority, we're here." Leave the door open.

## Rules

- Never be pushy. If they say no twice, respect it.
- The goal is to understand, not to overcome. Real objections are information.
- Ask before you answer. The stated objection is rarely the real one.
- Use their language. Mirror the words they use to describe their problem.
- Have proof ready. Case studies, metrics, and testimonials beat arguments.
- Know when to walk away. Not every prospect is a fit. That's okay.

## Quick Reference

When the user says "They said [objection]", respond with:
1. What the real concern likely is
2. A follow-up question to explore it
3. 2-3 response options depending on the root cause
4. A suggested next step

Related Skills

macpilot-dialog-handler

3891
from openclaw/skills

Handle macOS file dialogs (Open, Save, Print) with MacPilot. Navigate folders, select files, set filenames, and dismiss dialogs programmatically in any application.

Telegram Marketing Audit Command Handler Skill

3891
from openclaw/skills

## Purpose

---

3891
from openclaw/skills

name: article-factory-wechat

Content & Documentation

humanizer

3891
from openclaw/skills

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

Content & Documentation

find-skills

3891
from openclaw/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

General Utilities

tavily-search

3891
from openclaw/skills

Use Tavily API for real-time web search and content extraction. Use when: user needs real-time web search results, research, or current information from the web. Requires Tavily API key.

Data & Research

baidu-search

3891
from openclaw/skills

Search the web using Baidu AI Search Engine (BDSE). Use for live information, documentation, or research topics.

Data & Research

agent-autonomy-kit

3891
from openclaw/skills

Stop waiting for prompts. Keep working.

Workflow & Productivity

Meeting Prep

3891
from openclaw/skills

Never walk into a meeting unprepared again. Your agent researches all attendees before calendar events—pulling LinkedIn profiles, recent company news, mutual connections, and conversation starters. Generates a briefing doc with talking points, icebreakers, and context so you show up informed and confident. Triggered automatically before meetings or on-demand. Configure research depth, advance timing, and output format. Walking into meetings blind is amateur hour—missed connections, generic small talk, zero leverage. Use when setting up meeting intelligence, researching specific attendees, generating pre-meeting briefs, or automating your prep workflow.

Workflow & Productivity

self-improvement

3891
from openclaw/skills

Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.

Agent Intelligence & Learning

botlearn-healthcheck

3891
from openclaw/skills

botlearn-healthcheck — BotLearn autonomous health inspector for OpenClaw instances across 5 domains (hardware, config, security, skills, autonomy); triggers on system check, health report, diagnostics, or scheduled heartbeat inspection.

DevOps & Infrastructure

linkedin-cli

3891
from openclaw/skills

A bird-like LinkedIn CLI for searching profiles, checking messages, and summarizing your feed using session cookies.

Content & Documentation