# How to handle LinkedIn sales objections with AI
> Stop your AI from giving up on leads. Learn how to build a sales playbook that handles not interested, too expensive, and timing objections on LinkedIn.
- HTML: https://getkinlead.com/ai-scripts-for-handling-common-objections
- Markdown: https://getkinlead.com/ai-scripts-for-handling-common-objections.md

**Short answer:** To handle 'not interested' or other objections using AI on LinkedIn, give the model a written playbook instead of a generic prompt. List each objection, the words that signal it, the reply you want, and when to stop, so the AI asks a question and reframes the value instead of apologizing and ending the thread.

## Why AI fails at objections

Most AI models are trained to be agreeable. That works for support tickets and fails at selling. When a lead writes 'not interested, thanks', the model reads the sentence as a boundary and closes politely. The lead stays exactly where they were before you wrote.

Generic prompts make it worse. 'You are a helpful sales assistant' gives the model no rule for disagreement, so it reaches for the safest sentence it knows. It apologizes, wishes them a good day, and stops.

The fix is to stop asking the model to be persuasive and start giving it a decision tree. An objection is a branch, not an exit. When someone says the price is too high, the next message should be about what the problem costs them, not about which features are included.

**What a generic prompt produces**

- I completely understand. I apologize for the intrusion. Please let me know if your situation changes in the future!
- No problem at all. I'll leave you to it. Have a great day!

**What a playbook produces**

- Fair enough. Most of the founders I talk to say the same thing until they see how the reporting gap costs them a day a month. Is that the reason, or is it timing?
- Understood. So I don't come back with the wrong thing, are you already using a tool for this, or is it just not a priority this quarter?

## The 'not interested' framework

'Not interested' is usually a reflex. People type it before they finish reading the second line of your message. Treating it as a final answer throws away leads who would have answered a better question.

The goal of the first reply is not to win the deal. It is to turn a yes or no into a short conversation about fit, using one question that takes ten seconds to answer.

1. **Acknowledge without apologizing.** Open with 'Fair enough' or 'That's a reasonable reaction'. Skip 'I'm sorry to bother you', which tells the lead the message wasn't worth sending in the first place.
2. **Isolate the objection.** Ask one question that separates the three common reasons: wrong problem, wrong time, already solved. 'Is that because the timing is bad, or because you already have this covered?'
3. **Offer something specific.** A short teardown of their pricing page, a two-line benchmark from a similar company, a checklist. Not a deck and not a call.
4. **Set a dated follow-up.** If they still pass, name a month or a milestone. 'I'll check back in September when your Q3 hiring settles' beats 'I'll keep you posted'.

## What to say for each common objection

Price objections need a value answer, timing objections need a date, and competitor objections need a gap. Sending a feature list to a price objection is the mistake I see most often in AI-written replies, because the model reaches for the thing it knows best.

Write the pivot first, then the sentence. If you can't name what the reply is trying to find out, the reply is filler.

| | Objection | What to pivot to | Example line |
| --- | --- | --- | --- |
| Too expensive | Cost of the current problem | Fair enough. What does the problem cost you now, roughly? If the number is small I'll leave you alone. |
| Not right now | A date or a trigger | Understood. Is there a month when this moves up the list, or is it tied to something specific like a hiring round? |
| Already using something | The gap the tool leaves | Glad that's handled. Most teams on it still build the event list by hand. Is that side covered? |
| Send me some info | One qualifying question | Happy to. So I send the right thing, is the issue the price or the setup time? |

## Building your AI sales playbook

A playbook is a plain document. It lists each objection, the words that signal it, the reply you want, and the point where the AI stops trying. Write it once and reuse it across every campaign you run.

Keep each entry to four lines: trigger, goal, reply, stop. The stop line matters more than the rest. Without it the AI keeps reframing after the lead has said no three times, and you get a complaint instead of a reply.

Use your own words. If your best rep says 'fair enough' on calls, put 'fair enough' in the playbook. The AI copies tone well and invents it badly.

```
Objection playbook

Category: price
Trigger: budget, too expensive, can't justify, no money this quarter
Goal: find out whether the value is unclear or the budget is gone
Reply: 'Fair enough. Usually when that comes up it means the value isn't obvious yet. If I showed you how Northwind halved their list-building time, would that be worth five minutes?'
Stop: lead repeats the price objection twice

Category: timing
Trigger: not right now, too busy, next quarter, circle back
Goal: get a month or a milestone
Reply: 'Makes sense. Is there a project or a date when this moves up the list? I'll set a reminder and stay out of your inbox until then.'
Stop: no date after two asks

Category: competitor
Trigger: we already use X, happy with our current tool
Goal: find the gap the current tool leaves
Reply: 'Good to know. Most teams on Acme use it for prospecting and still build event lists by hand. Is that side covered?'
Stop: lead says the gap is covered

Category: no problem
Trigger: we don't do that, doesn't apply to us
Goal: confirm fit and leave cleanly
Reply: 'That's useful, thanks. Sounds like this isn't the right fit. I'll close the loop here.'
Stop: always
```

## When the lead pushes back a second time

One pivot is a conversation. Two is persistence. Three is spam. Decide in advance how many times the AI may reframe before it stops, and what it says on the way out.

The exchange below is what a working playbook looks like in practice. The lead gives two soft noes, the AI asks about the reason behind them, and the third message earns a small yes.

- **them:** We're not looking at anything new this quarter.
- **you:** Fair enough. Is that because the budget is locked, or because the team is mid-migration?
- **them:** Both. We're moving off HubSpot in October.
- **you:** That's the useful part. Most teams rebuild their outbound list right after a migration and drop the accounts that went cold. Worth a look in October?
- **them:** Send me something to read.
- **draft:** Will do. I'll send the two-page version on rebuilding a cold list after a migration, and check back the week of October 12.

## Guardrails so the AI doesn't sound desperate

Three rules cover most of it. Never apologize for the message. Never repeat the same pivot twice. Never ask for a meeting in the same message where you handle the objection.

Ban the phrases that make a reply read as automated. Most of them are hedges the model adds when it isn't sure what to do next.

- 'Sorry to bother you' and 'I'll keep this brief'
- 'Just following up' two messages in a row
- 'Does that make sense?' at the end of a question
- Two questions in one message, which splits the lead's attention and gets neither answered

> One objection, one question, one exit. If you can't say which of the three a message is doing, it isn't ready to send.

## Doing this with Kinlead

Kinlead campaigns take a sales playbook as an input. Paste the document from the section above into the playbook field, and the AI writes each message and follow-up from your campaign goal, tone and those scripts. The connection note is separate and stays under 200 characters, opening with why that person became a lead.

Reply handling is a per-campaign setting. Hand-off mode stops the AI at the first reply and drops the thread in your inbox, which is the safe choice while you're still testing scripts. The other two modes let the AI answer until there's real interest, or until a meeting is booked with your scheduling link. Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.

Every reply from every campaign lands in one inbox, sorted by intent with interested replies first, and you get an email when someone answers. That's where you check whether the playbook is holding up. If two leads in a row push back on price, the price entry needs a rewrite, not a new campaign.

1. **Paste your playbook into the campaign.** Open the campaign, add your objection document to the playbook field, and set the goal and tone to match how your best rep actually talks.
2. **Pick a reply mode for the test.** Start on hand-off mode so you see every objection before the AI answers it. Move to AI replies until real interest once the scripts stop surprising you.
3. **Review the actions page weekly.** Read the queued and sent messages, note where the AI got vague or repeated itself, and edit the playbook entry that caused it.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Reply drafts](https://getkinlead.com/features/reply-drafts.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Should the AI always try to overcome a 'not interested' reply?**

No. If the lead doesn't have the problem you solve, let it go. Push back only when the objection is about timing, price or a competitor, because those are the three you can answer with information.

**How many times can the AI follow up after an objection?**

Two reframes is enough for most outbound. After that the lead has told you what they think, and a third attempt costs you more in reputation than the lead is worth.

**How do I stop the AI from sounding pushy?**

Add a stop line to every playbook entry and ban the hedging phrases listed above. Acknowledging the lead's point before asking a question does most of the work.

**What's the best way to move an objection toward a booking link?**

Ask permission first. 'Would a ten-minute call be worth it to see if this fits?' then send the link once they say yes. Dropping the link inside the objection reply reads as a brush-off.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
