How to Handle Objections in DMs ("Too Expensive", "Send Me Info", "Is This Legit?")

Handling an objection in DMs comes down to three moves: acknowledge it, ask what's really behind it, and answer that specific concern, briefly and with proof. Most objections in text conversations are really questions: "too expensive" often means "I don't see the value yet", and "send me info" often means "I'm not sure, and I don't want a sales call".

I've read hundreds of objection exchanges while tuning AI setters in ReplySetter. The objections repeat endlessly, which is good news: you can prepare for them.

The framework: Acknowledge, Ask, Answer

1. Acknowledge. Show you heard it and that it's reasonable. "Totally fair."
2. Ask. Find the real concern. "Is it the overall price, or more the timing?"
3. Answer. Address that specific concern with a fact, a result or an option, then move forward with a question.

In text, keep each step short. A wall of persuasion reads as pushy.

The most common objections and how to handle them

"How much is it?" (before qualifying)

It's not really an objection, but how you handle it matters. Dodging feels shady.

fair question! it depends on what you need, but most people invest around [range]. the call is where we work out exactly what fits. what are you hoping to get help with?

"It's too expensive"

totally get it, it's a real investment. can I ask, is it more that it's above what you'd planned to spend, or that you're not sure it'd be worth it for you?

If it's value:

makes sense. most of our clients felt the same before starting. [client] was in a similar spot and [result]. the call is free, you'll know within 15 minutes if it'd pay off for you.

If it's budget:

no worries at all. we do have [smaller option / payment plan]. want me to tell you about that?

"Send me more info"

Often a polite way out. Give a little info and keep the conversation going:

sure! quick version: [one-sentence summary]. what's the main thing you'd want to know, so I send the right stuff?

"Is this legit?" / "Is this a scam?"

Don't get defensive. Give proof:

totally fair to ask, there's a lot of nonsense out there. we've been doing this since [year], here's [testimonial or result]. the call is free and zero pressure.

"I need to think about it"

of course. what's the main thing you're weighing up?

Then answer that.

"I need to talk to my partner"

makes total sense. would it help if they joined the call? that way you can both ask questions.

"I don't have time"

I hear you. that's actually a big part of what we look at, making it fit a busy schedule. would 15 minutes early morning or evening work for a quick call?

"I've tried things like this before"

that's really common. what did you try, and what didn't work about it?

Then explain how yours is different, specifically.

"Not right now"

no problem. when would be a better time to pick this back up?

Then actually follow up then. See how to follow up with leads who ghost you.

Objection handling mistakes I see

• Arguing. You can't argue someone into buying.
• Long walls of text. In DMs, every objection response should fit on a phone screen.
• Ignoring the objection and pushing the booking link.
• Generic answers. "We have great reviews!" is weaker than one specific result.
• Pressure tactics. Fake scarcity damages trust, and screenshots travel.

Build an objection bank

The best thing you can do for your setters, human or AI, is write down every objection you hear, with your best answer and proof. A simple table:

Teaching an AI setter to handle objections

An AI setter is good at objections when it has the right material. How I set it up in ReplySetter:

1. Put the objection bank in the knowledge base. Real answers and real proof, so it doesn't make things up.
2. Add an objection scenario. In ReplySetter, scenarios are rules that apply anywhere in the flow, for example "when the person raises a concern about price, acknowledge it, ask what's behind it, then answer from the knowledge base, and return to where you were".
3. Set limits. "Never offer discounts. Never promise specific results."
4. Hand off when needed. If someone's very sceptical or upset, pass to a human.
5. Test in the sandbox by playing the difficult lead yourself.
6. A/B test two approaches to the price objection and keep the one that books more. See A/B testing.

When a reply misses, the debugger shows which knowledge base snippets it used, so it's usually obvious whether the problem was a missing fact or a weak instruction.