---
title: "Just Send Me the Info Objection: 14 DM Replies"
slug: just-send-me-the-info-objection
author: "Leonardo Maldonado"
category: "DM Closing & Scripts"
articleType: listicle
tags: ["send me the info sales script","DM objection scripts for coaches"]
publishedAt: 2026-10-30T09:00:00.000Z
updatedAt: 2026-10-26T12:00:00.000Z
canonical: https://setluca.com/blog/just-send-me-the-info-objection
---# Just Send Me the Info Objection: 14 DM Replies

> The just send me the info objection is a polite exit most of the time and a real request some of the time, and you cannot tell which from the message alone. Send something genuinely useful and keep the thread open with one question. Information that helps earns the next reply; a refusal to send anything ends the conversation you were trying to save.

## Key takeaways

- Ask one or two short questions before you send anything, so what you send answers their situation instead of describing your program.
- Send something real. Refusing to send information and demanding a call reads as combative to a person who was only browsing.
- End every send with a question. A closed thread is the actual failure, not a lead who reads slowly.
- Most coaches have nothing good to send, and a 14-page PDF is worse than four sentences in the chat.
- Give people a clean way to say no. The ones who take it were never going to book, and the ones who don't take it tell you something useful.

---

## What does the just send me the info objection actually mean?

Most of the time it means the conversation got uncomfortable and the lead found a polite way out. Asking for information is socially free. It sounds interested, it costs nothing, and it hands the work back to you while they quietly disappear.

The other version is real. Some people read before they talk, and never buy anything on a first conversation. Gong calls the first kind a smokescreen objection, a surface request covering something else, and the tell is detail. The smokescreen arrives empty. The real one has a question inside it.

Both versions get the same first move, which is why this one is easier than it looks. Answer with something useful and a question, then read what comes back. It sits beside the other big ones in [objection handling in the DMs](/blog/objection-handling-in-dms), and behaves like [let me think about it](/blog/how-to-handle-let-me-think-about-it) with an errand attached.

## Why does refusing to send the info backfire?

Refusing backfires because the standard advice was written for someone already sold and stalling, and most people asking for information are not that person. "I don't really have anything to send, but I've got 15 minutes Thursday" works on a lead who wants your program. Used on a browser, it reads as a trap, and they leave without replying.

The second reason changes how you work. Buying research from Gartner found people are about 1.8 times more likely to complete a high-quality purchase when they use a seller's materials with the seller still involved, rather than reading alone. The mechanism is identical in a DM thread: what you send gets interpreted, and you want to be there when it happens.

So send the information they asked for, and stay in the conversation while they read it. That's the ordinary work of [closing clients in the DMs](/blog/how-to-close-clients-in-dms), and a long way from the pressure patterns in [how to ask for the sale without being pushy](/blog/how-to-ask-for-the-sale-without-being-pushy).

## How do you tell a polite exit from a genuine request?

Read the shape of the request, not the words. A genuine request contains something specific: a question, a constraint, or a comparison they're already running. A polite exit is smooth and empty. "Just send me the info" with nothing attached is the emptiest sentence in sales.

| Signal | Reads as a genuine request | Reads as a polite exit |
| --- | --- | --- |
| What they asked for | Names a thing: pricing, schedule, week one | "The info," "more details," "everything" |
| Detail in the thread | They've told you their goal or their problem | You've done most of the talking |
| Timing | Arrives after a real back-and-forth | Arrives right after price or a call comes up |
| Their question | Has a constraint: "I travel a lot, does that work?" | No question at all |
| What happens next | They read and come back with something | Silence, or "thanks, I'll take a look" |

### Which branch the signals point to

Two or more genuine signals: send a real answer, then ask one question about their situation. Two or more exit signals: send something small, then give explicit permission to say no. Mixed signals almost always mean price, so move into [the price conversation](/blog/the-price-conversation-in-dms) rather than sending a document that avoids the number.

## What to actually send when they ask for the info

Send a short, specific answer to their situation, in the chat, with no attachment. Four or five sentences: their goal, what the first month looks like, the price, and who it isn't for. Skipping the number turns a simple ask into [the "I can't afford it" objection](/blog/how-to-handle-i-cant-afford-it) two days later. Most coaches fail this before it arrives, because the only asset they own is a slide deck built for a webinar.

Attachments are where these threads die. Nielsen Norman Group has tested PDFs against web content since 2001 and reported in 2020 that hostility toward them has risen rather than fallen, with participants abandoning them on open. Its eyetracking work found people scan instead of reading, so a document only works if the first screen carries the answer.

### Which format fits which ask

Match the format to the question rather than to whichever asset you already own. Four sentences in the chat is the default, and every other format is an exception you should be able to name.

| What you send | Works when | Fails when |
| --- | --- | --- |
| Four sentences in the DM | Almost always; this is the default | The question is genuinely technical |
| A 45-second voice note | They wrote something emotional or messy | They're at work or somewhere shared |
| One mobile-first web page | They asked to compare options | It's testimonials with no price |
| A short screen recording | The question is "how does it actually work" | It runs over two minutes |
| A 14-page PDF | Essentially never | Always |

One page and one voice note cover nine versions of this out of ten, and [voice notes in the DMs](/blog/voice-notes-in-dms-for-sales) carry tone that text drops.

## 14 copy-paste replies for "just send me the info"

### 1. The Two Questions First

> "Yeah, happy to. Two quick things so I send you something useful instead of a brochure: what are you working on right now, and what's the part that keeps not working?"

**When:** your default first reply, before you send anything. **Why:** it moves them from receiving to describing, and a person describing their own problem is in a different conversation than one reading your marketing. **If they push again:** if they answer, send script 5 with their words in it. If they repeat the ask, send script 3.

### 2. The Price-Shaped Question

> "Sure. Quick check so I answer the right thing: are you mostly wanting to know what it costs, or how the actual coaching works?"

**When:** the request landed a message or two after you mentioned you work with people. **Why:** "send me the info" is often "how much is it" wearing a coat. **If they push again:** give the number plainly. Dodging it here creates the next objection.

### 3. The Menu

> "Can do. Which is more useful right now: what the 12 weeks actually look like, what it costs, or who it doesn't work for?"

**When:** they've asked twice, or your questions went unanswered. **Why:** it turns an open request into a choice, and any choice is a reply. The third option signals you won't oversell them. **If they push again:** "all of it" is honest. Send script 5 and stop diagnosing.

### 4. The Useful Trade

> "Here's the short version: [one specific thing about their situation]. That's the piece most people in your spot get wrong. Want the rest of how we'd handle it?"

**When:** you know enough to say something true and specific about them. **Why:** you give first, the value is real, and the next question is theirs to ask. Same mechanic as [warming up a cold lead before pitching](/blog/how-to-warm-up-a-cold-lead-before-pitching). **If they push again:** if they say yes, keep the shape: one useful thing, one open door.

### 5. The One-Screen Answer

> "Here it is, short version. You're trying to [their goal]. It's 12 weeks, we talk every Monday, and your training and food live in one place. It's $2,400, or three payments of $850. It's not a fit if you want somebody checking your food logs daily. What's the part you'd want to poke at?"

**When:** any genuine request, and the fallback whenever you're unsure. **Why:** it answers, prices, disqualifies and asks, all inside one screen. **If they push again:** if they poke at one part, you're in a real conversation. Silence means information wasn't the problem, so run script 12.

### 6. The Voice Note Version

> "Easier to talk than type this one, gimme a sec." (Then 40 seconds: their situation, what you'd do, the price, one honest limit.)

**When:** their message was long or emotional, or the answer has an "it depends" in it. **Why:** a person who hears you stops picturing a template. **If they push again:** a voice reply means you're close. "Can you type that" means they're at work, so send script 5.

### 7. The Send-and-Ask

> "[The information they asked for.] One question while you look at it: is the money the sticking point, or the time?"

**When:** every time you send anything, without exception. **Why:** a send with no question is a goodbye with extra steps. **If they push again:** whichever they name is the real objection. Money goes to the price thread, time to the schedule.

### 8. The Honest Exit

> "Totally fine either way. Sometimes 'send me the info' means 'this isn't for me right now,' and that's a normal answer. Which is it? No wrong reply here."

**When:** two or more exit signals, or a second unanswered send. **Why:** with the pressure off, honesty gets cheap. You get a clean no, or the real objection. **If they push again:** if they say it's the wrong time, ask what would have to change.

### 9. The Browsing Pass

> "All good. Sounds like you're in look-around mode, which is smart with something this size. I'll leave it here. If you want it later, just say the word."

**When:** they're clearly early, and pushing would cost you the relationship. **Why:** browsers buy on their own timeline, and the coach who let them is the one they message in March. **If they push again:** nothing. This ends the thread warmly. Set a reminder for six weeks out.

### 10. The Wrong-Fit Redirect

> "Straight answer: from what you've told me, I don't think this is your thing. What you actually need is [the real thing]. Want me to point you at someone who does that properly?"

**When:** the information they want is for a problem your program doesn't solve. **Why:** honest disqualification is rare enough to be memorable, and it saves you the client who buys and then resents it. **If they push again:** if they want in anyway, spell out what they won't get before you take money.

### 11. The One Thing

> "Did that answer it? Curious which part landed and which part you'd push back on."

**When:** 12 to 24 hours after a send that got a "thanks" and nothing else. **Why:** it asks for a reaction, not a decision, and reactions hand you the next thing to talk about. **If they push again:** if they name an objection, handle it. If they say "all good," ask what they're comparing you to.

### 12. The Quiet Follow-Up

> "No pressure on this. Last thing from me: if you started in January instead of now, what would you want sorted by then?"

**When:** roughly 48 hours of silence after a real send. **Why:** it asks about their year, not your program, so it's answerable without feeling sold to. **If they push again:** if this gets nothing, stop. Two more messages won't fix what four didn't.

### 13. The Second Ask

> "Course. Before I send more, what's still open after the last one? Don't want to hand you another wall of text to sort through."

**When:** they've received information once and asked for more. **Why:** a repeat request usually hides an unnamed objection, and more documents make it worse. **If they push again:** a vague answer means the decision isn't theirs alone, which runs like [the spouse objection](/blog/i-need-to-talk-to-my-spouse-objection).

### 14. The Call Bridge

> "Makes sense. Honestly, the two things you're asking about are quicker said than typed. Want 15 minutes Thursday, or should I keep answering here? Both work."

**When:** the thread is going well and the questions have got specific. **Why:** the call is the faster option, not the price of your attention, so declining it ends nothing. **If they push again:** if they choose the DMs, keep going. Plenty of people buy in text.

## A worked example: Priya and the 12-week thread

Priya coaches strength clients online. Her program is 12 weeks at $2,400 up front, or three payments of $850, which totals $2,550, so the plan costs $150 more. This walkthrough is illustrative, built from the pattern rather than one account.

A lead replies to her story on Tuesday. Four messages later: "just send me the info!" Priya's old move was the 14-page PDF built for a webinar. Her new move is script 1, two questions, 26 words. The lead answers: lifting two years, stalled on her squat, travels for work a week a month.

### What the follow-up surfaced and what it cost

Priya sends script 5 with those words in it and ends on the travel question, because the lead raised it. Nothing Wednesday. Thursday morning, script 11: which part landed. The lead says the payment plan is the issue, so the real objection surfaces on day three instead of never. Priya answers plainly, and the lead books on Saturday.

Count the work: nine messages over five days, about two minutes each, so roughly 18 minutes of writing against a $2,400 decision. The PDF version took 30 seconds and ended in silence.

## What are the most common mistakes with this objection?

**The Instant Send.** You fire off a link within seconds, before you know anything. What arrives is generic, so it gets skimmed and forgotten.

**The Refusal.** "I don't send info, but let's hop on a call." It reads as a gatekeeper move, and browsers leave rather than argue with you.

**The Silent Send.** You attach the thing and say "let me know!" The thread is now closed and the next move belongs to nobody.

**The Document Dump.** Three links, a PDF and a testimonial reel. Volume says you don't know which part matters to them, and it buries the price.

**The Follow-Up Grind.** Four "just checking in" messages after one unanswered send. Everything past message two trains them to ignore you, so space them using [the best time to follow up with a lead](/blog/best-time-to-follow-up-with-a-lead).

## What about the harder versions of "send me the info"?

**They ask after the call is already booked.** Cold feet, or preparation. Send the one-screen answer and re-confirm the time in the same message, so the booking stays anchored.

**They ask on behalf of someone else.** Send the short version plus one line they can forward, then ask who it's for. Often the real lead is the one asking.

**They already bought from you before.** Skip diagnosis. They know your work, so send the price and the start date. Treating a returning client like a cold lead is insulting.

**They message at 2am asking for everything.** Answer at a human hour with the one-screen version. Late-night asks are usually impulse, and a 3am reply teaches them you're always available.

**They receive it, then reappear three months later.** Don't resend the same asset. Open with what changed: "Last time you were stuck on your squat. Where's that now?"

## Why isn't the info you send moving anyone forward?

Usually the asset is wrong for the channel rather than wrong in content. Run the symptom down this table before you rewrite anything.

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| Sends get opened, then silence | No question at the end of the message | End every send with one question about their situation |
| Nobody opens the attachment | It's a PDF on a phone | Put the answer in the chat as four sentences |
| They reply "looks great!" and vanish | The price wasn't in what you sent | State the number in the same message as the value |
| The thread dies after your second message | You asked for the call before you'd earned it | Move the ask to message four or later |
| Replies come back short and polite | The asset is about you, not them | Rewrite the first sentence to name their goal |

## How does an AI setter handle "just send me the info"?

An AI setter handles the routine version: recognising the ask, pulling the short answer you wrote instead of a generic link, and ending on a question so the thread stays open. What it must never do is invent an asset you don't have, or send a document you haven't already approved for that purpose. That's the difference between an assistant and a liability.

Timing is the other half, and platform rules set it. Meta's Messenger Platform gives a business 24 hours to reply to a user message, and the human agent tag extends that to seven days when a real person answers. On WhatsApp, a customer message opens a 24-hour service window for free-form replies; after it closes you're limited to approved templates, covered in [WhatsApp's 24-hour rule](/blog/whatsapp-24-hour-window). Miss the window and your options narrow. Meta's Instagram documentation also asks businesses to disclose automated service at the start of a thread where local law requires it, so build that in rather than around it.

### Where a human setter still beats it

The honest limit is emotion. When the ask has an emotion under it (grief, embarrassment, a body someone is ashamed of) a good human setter hears it and answers with something no script covers. Software gets a useful reply out fast and keeps the thread alive. It does not hear what wasn't typed. Route those threads to yourself, and let the machine handle the ninety people who genuinely wanted the price. The questions you'd want it asking first are in [lead qualification questions for coaches](/blog/lead-qualification-questions-for-coaches).

## What to do the next time it lands

The just send me the info objection is a fork in the conversation. Send something short and genuinely useful, put one question at the end of it, and let the reply show you if this is a buyer or a browser. Then respect the answer. The coaches who win this one have something worth sending, and they ask what happened after it landed.


## FAQ

### Should I send information when a lead asks for it?

Yes, almost always. Refusing looks like a gatekeeper move and loses people who were genuinely researching. Send a short, specific answer in the chat rather than an attachment, and finish with a question so the conversation stays open while they read it.

### Is the just send me the info objection always a brush-off?

No. It's a polite exit most of the time, but some people genuinely read before they talk. The difference shows in the detail: a real request names a specific thing or carries a constraint inside it, while a brush-off is smooth, short and empty.

### What should I send when someone asks for more details?

Four or five sentences in the DM: their goal in their words, what the first month looks like, the price, and who it isn't for. Add a 45-second voice note if the answer is nuanced. Skip the PDF, which most people abandon on a phone.

### How long should I wait before following up on the info I sent?

Around 48 hours for a first follow-up, then one more a few days later, and stop. Platform rules matter too: Meta gives a business 24 hours to reply freely, extended to seven days with the human agent tag for a human response.

### Should I ask for a call instead of sending information?

Offer the call as the faster option, not as a condition. "These are quicker said than typed, want 15 minutes Thursday, or should I keep answering here?" gives them a real choice, and leaving the DM route open means declining the call doesn't end the conversation.

### What do I do if they ask for information a second time?

Ask what's still unanswered before sending anything else. A repeat request usually hides an objection they haven't said out loud, and more documents make that worse. If the answer is vague, ask who else is involved in the decision.

### Can an AI setter handle this objection?

It handles the routine version well: recognising the ask, sending the short answer you approved ahead of time, and ending with a question. Keep emotionally loaded threads for yourself. With Luca, you can set any channel to review, so you see those before anything goes out.


## Sources

1. [Gartner. "The B2B Buying Journey."](https://www.gartner.com/en/sales/insights/b2b-buying-journey)
2. [Gong. "5 Types of Sales Objections and How to Handle Them." Retrieved October 17, 2026.](https://www.gong.io/blog/sales-objections/)
3. [Nielsen Norman Group. Moran, K. "How People Read Online: New and Old Findings." April 5, 2020. Retrieved October 26, 2026.](https://www.nngroup.com/articles/how-people-read-online/)
4. [Nielsen Norman Group. Nielsen, J. and Kaley, A. "PDF: Still Unfit for Human Consumption, 20 Years Later." August 9, 2020. Retrieved October 26, 2026.](https://www.nngroup.com/articles/pdf-unfit-for-human-consumption/)
5. [Meta for Developers. "Messenger Platform Policy Overview.". Retrieved October 26, 2026.](https://developers.facebook.com/docs/messenger-platform/policy/policy-overview/)
6. [Meta for Developers. "Instagram Messaging.". Retrieved October 26, 2026.](https://developers.facebook.com/docs/messenger-platform/instagram/)
7. [Meta for Developers. "WhatsApp Business Platform Pricing.". Retrieved October 26, 2026.](https://developers.facebook.com/docs/whatsapp/pricing)

---

Published by SetLuca.