# How to reply when a prospect says send me more info
> Learn how to tell a polite brush-off from real interest and use value-first templates to turn a request for more information into a booked meeting.
- HTML: https://getkinlead.com/reply-when-prospect-asks-for-more-info
- Markdown: https://getkinlead.com/reply-when-prospect-asks-for-more-info.md

**Short answer:** When a prospect asks for more information, they're usually either politely ending the conversation or testing if you understand their problem. Avoid sending a generic brochure. Instead, send one specific piece of value that addresses their role and ask a qualifying question to see if a meeting is worth their time.

## Is this a real lead or a brush-off?

When someone says send me more info, you have to figure out if they're actually interested or just trying to get you to stop messaging them. A generic request is often a polite way to end the conversation without saying no.

Real interest usually comes with a specific question or a mention of a goal. If they ask about a particular feature or how you solve a specific problem, they have a gap in their current process they want you to fill.

The wording matters less than the follow-through. Someone who replies with a one-line request and then goes quiet was probably never in the market. Someone who answers your next question with detail is telling you they have a problem worth discussing.

If you treat every request as a hot lead and send a massive company deck, you waste your time and annoy the prospect. Qualify the intent before you spend an hour customizing a proposal.

**The brush-off**

- Sounds interesting, send me more info.
- Can you send over some details?
- Sure, send a deck to my email.

**The signal**

- Can you send more info on how you handle API integrations?
- I'm interested, but does this work for teams over 50 people?
- Send me more info on how you reduced churn for other agencies.

## Ask one question before you send anything

The fastest way to separate a real lead from a polite no is to ask one short question before you send the asset. You are not trying to start an interrogation. You are giving them an easy way to tell you what matters.

Ask about their current process, not your product. A question like 'Is the bigger issue getting leads or handling the ones you already have?' is easy to answer and tells you which asset to send. A question like 'Would you like to see our platform overview?' gives them nothing to react to.

If they answer, you now have a reason to send something specific. If they don't answer, you saved yourself the work of building a custom deck for someone who was never going to book a call.

- What are you using today for this process?
- Is the bigger pain finding leads or following up with them?
- Who else would need to sign off if this became a priority?

## The value-first response framework

Most people send a generic PDF and then ask for a meeting. This feels like a transaction where you give them a document and they give you 30 minutes of their time. The balance is off.

Use a framework that provides a small win first. Give them a piece of information that's actually useful to their job title, then ask a question that makes them realize they have a problem you can solve.

Your goal is to prove you understand their specific pain and that you have a way to fix it. Keep the product explanation short. The prospect should finish your message thinking about their own process, not your feature list.

The asset should be small enough to read in a couple of minutes. A one-page case study, a short video, or a checklist works better than a 20-slide deck because it asks for less attention and gives a clearer answer.

1. **Acknowledge the request.** Confirm you can send the info without sounding overly eager.
2. **Provide one specific asset.** Send a link to a case study, a short video, or a checklist. It must be relevant to their role. A CFO wants an ROI sheet, not a feature list.
3. **Ask a qualifying question.** Ask a question about their current process that forces them to think about their bottleneck.
4. **Suggest a call based on the answer.** Only propose a meeting if their answer proves they're a fit for your solution.

## Templates for different intent levels

How you reply depends on how much detail the prospect gave you. If they were vague, your job is to narrow down their needs. If they were specific, your job is to prove your expertise.

Don't use these as rigid scripts. Adjust the tone to match how they spoke to you. If they're formal, stay formal. If they're brief, be brief.

- **them:** Sounds interesting, send me more info.
- **you:** I can do that. Since you're the Head of Ops, would it be more helpful to see how we reduce churn or how we speed up onboarding? I'll send the right one over.
- **them:** Onboarding is the bigger pain right now.
- **you:** Got it. Here is a 1-page checklist we used to cut onboarding time by 30% for a similar agency. Does your current process struggle with the hand-off from sales to ops, or is it the technical setup that takes too long?

```
For specific requests:

'Here is the breakdown of how we handle [Specific Feature]. Most teams find the second page the most useful because it shows the actual workflow. Does your current setup struggle with the same bottleneck, or is it something else?'

For the 'Check your website' response:

'The site has the broad overview, but I have a specific example of how we did this for a company in your niche. Want me to send that over instead?'

For a pricing request:

'I can send a range, but it depends on how many people would use it and what you need it to connect to. Are you comparing this to a tool you already have, or starting from scratch?'
```

## What to avoid sending

Certain responses kill the momentum. The moment you send a generic 20-slide company deck, you've told the prospect that you don't actually know their specific problem and you're hoping they'll find something they like in your slides.

Pushing a scheduling link too early feels aggressive. If they haven't seen the value yet, a calendar link is just a request for a favor. Send something useful first, then earn the right to ask for time.

| | The mistake | Why it fails | What to do instead |
| --- | --- | --- | --- |
| The company deck | Too long and generic | Send a 1-page case study or a 60-second video |
| Calendly-only reply | Feels like a demand on time | Give value first, then ask for the call |
| The 'follow up in a week' promise | Kills the current momentum | Ask a qualifying question now |

> Never send a generic company deck as the first piece of information. Nobody reads them, and it marks you as just another salesperson using a script.

## Doing this with Kinlead

Handling these replies manually for every lead is slow. Kinlead helps by organizing your outreach and classifying replies by intent in a [unified inbox](/features/unified-inbox). This lets you see interested leads at the top of your list so you can prioritize them.

You can set a campaign to let the AI reply until there's real interest, then hand the conversation to you so you can send a specific case study or video. That keeps the first response fast without letting the AI handle the part where judgment matters.

If you have a specific sales script, you can upload it as a sales playbook. The AI uses this playbook to draft replies that match your tone and goals, so it doesn't just send generic responses. You can book a demo to see how the hand-off works in practice.

## Related

- [LinkedIn connection request templates](https://getkinlead.com/linkedin-connection-request-message-templates.md)
- [How to book LinkedIn demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)
- [Avoid LinkedIn restrictions](https://getkinlead.com/avoid-linkedin-restrictions-during-outreach.md)

## Common questions

**Should I send a PDF or a link?**

Use a link to a page or a shared file. A link lets you see whether they opened it and which part they spent time on. A PDF tells you nothing after it leaves your outbox.

**What if they don't reply to the info I sent?**

Wait two to three business days. Follow up by asking if the specific part of the asset you sent resonated with their current situation.

**How long should I wait before following up after sending info?**

Don't follow up the same day. Give them time to review the material, then check back in after 48 to 72 hours with a new question.

**What if they ask for pricing?**

Send a range or a starting point only if you can qualify first. Ask what they are comparing it to and how many people would use it. Pricing without scope is a guess that invites a no.

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