# How to handle prospects who ask for more info before a call
> Learn how to respond when a LinkedIn prospect asks for a deck or website link before booking a call. Send one useful proof point and keep it moving.
- HTML: https://getkinlead.com/handle-prospects-who-ask-for-more-info-first
- Markdown: https://getkinlead.com/handle-prospects-who-ask-for-more-info-first.md

**Short answer:** When a prospect asks for more info, they want to know whether a call is worth their time. Send one specific proof point that fits their role and explain the variable a document cannot cover. Then ask a narrow question and suggest a short call.

## Why prospects ask for more info

A request for a deck, a PDF or a website link usually means the prospect wants to check whether a call is worth their time. They may also need something to forward to a boss. Treat the request as a buying signal with a delay attached, then decide what to send.

A full presentation answers questions they have not asked yet. It also gives them a reason to decide alone, without you there to correct a wrong assumption. The safer move is to send one useful piece of information and leave room for a conversation.

Ask yourself what they are trying to protect. Time and status are the usual answers. Budget comes up when a boss is involved. Your reply should respect that concern and still give them a reason to talk.

The reply you send in the first two minutes matters more than the document. If you stall, the prospect fills the silence with a reason to drop the thread. Answer with a useful sentence and a question they can answer from their phone.

**Sending the full deck**

- They skim the first two slides and file the thread.
- A price or feature on page eight creates a question you never hear.
- The next message you send starts from zero.

**Sending one useful proof point**

- You show you understood their role and situation.
- They have a reason to reply with a question.
- You keep the context for a short conversation.

## What to send when they ask for a deck

Send something small enough to read in a minute and specific enough to prove you read their profile. A screenshot, a short case note, a one-page outline or a link to a relevant section can work. The format matters less than the relevance.

Write two sentences of context before the file. Name the company type and the problem. Add the result if you have one you can share. If you do not have a result, describe the process you use. Keep it accurate.

Choose the example closest to their industry or job title. Mention why you picked it so they know the message is not copied from a template.

Do not attach a file in the first reply unless they asked for that exact file. A link or a short note is easier to respond to. Save the attachment for the follow-up after they show interest.

1. **Acknowledge the request.** Say you can send something. Do not make them ask twice.
2. **Pick one proof point.** Choose the example closest to their situation. Mention why you picked it.
3. **Say what the document cannot cover.** Explain the one variable that changes your answer, such as their current stack or approval process.
4. **Ask a narrow question.** Ask about the variable you just named. A narrow question is easier to answer than 'Do you want to chat?'
5. **Offer two times.** Suggest two specific slots or ask for a day that works. Keep the call short.

> Send enough to earn a reply. Keep the call as the next step.

## Scripts for the requests you will see most

The same approach works for a deck request, a website link request and a pricing request. Give a real answer and name the gap. Then ask a question that only they can answer.

Keep the message short. Long explanations read as defensiveness.

For a pricing request, do not dodge the number. Give a starting range and say what moves it. Then ask whether they have budget approved or are still building the case.

- **them:** Can you send over some more info first?
- **you:** Yes. I can send a short case note from a 40-person agency that had the same lead-quality problem. The part that changed the result was how they filtered inbound leads before anyone contacted them. That filter depends on your current pipeline, so a generic deck would miss the useful part. What does your lead flow look like now?
- **them:** Just send the website link.
- **you:** I can send the link. The site covers the product, but it does not show which setup works for a team your size. Would a 10-minute call Thursday help you skip the parts that do not apply?
- **them:** We do not have time this week.
- **you:** Understood. I will send the case note and check back next Tuesday. If the filter idea sounds relevant, reply with 'send it' and I will include the two questions I would ask on a call.

## When they refuse the call

Some prospects will take the information and disappear. That is a result. Decide what kind of follow-up fits the account and stop spending call-booking energy on someone who has told you no twice.

Use the request itself to sort the lead. A person who wants a document for their boss needs a shareable summary. A person who wants proof needs a short demo. A person who wants a price needs a range and a reason the range moves.

A hard no is still useful. Mark the lead, note the reason and set a reminder for a later date if the account is worth it. Do not keep sending decks to someone who has stopped replying.

| | Request type | What to send | What to ask next |
| --- | --- | --- | --- |
| The hard no | A one-page summary with the problem, the process and one example | Would it help if I sent the questions your team should ask any vendor? |
| The skeptic | A short screen recording or a link to a relevant teardown | Which part of the workflow would you want to see first? |
| The researcher | A link to the most specific article or help page you have | What are you comparing, and what would make one option easier to shortlist? |
| The price checker | A starting range and the two factors that move it | Is budget already set, or are you building the case now? |

> If someone asks for pricing, give a range and name the factors that change it. Refusing to answer reads as evasive and wastes a reply.

## Follow up without sounding pushy

A follow-up should add something. Send the file you promised. Add one sentence about why it fits their situation. Then ask a question with a low cost to answer.

If they go quiet, wait longer than feels comfortable. Then send a short note that refers to the original problem and gives them a reason to reply.

Two follow-ups after the file are enough. On the third, ask whether the timing is wrong or the problem is not a priority. That gives them an easy exit and gives you a clean answer.

Track what you sent and when. A simple note in your lead list is enough. When they reply months later, you need the context to pick up the conversation without asking them to repeat themselves.

```
Hi [First name], I said I would send the [case note] about [specific problem]. The part that may apply to [Company] is [one sentence]. If it is useful, I can walk through the two questions I would ask before changing your setup. Would [day] or [day] work for a 10-minute call? If the timing is wrong, tell me and I will close the loop.
```

## Doing this with Kinlead

Kinlead writes campaign messages from the goal, tone and an optional sales playbook, so you can keep your value teaser language in one place instead of retyping it for every sequence. You can use hand-off mode when you want to take over at the first reply and apply the scripts above yourself.

Replies from every campaign land in one inbox, classified by intent, with interested replies first, and you get an email when someone replies. Queued campaign messages can be read and edited on the Actions page before they send, and any campaign can be paused.

If you want to see how the inbox and hand-off flow fit your process, [book a demo](/demo).

## Related

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

## Common questions

**Is it rude to decline a deck request?**

You can decline the deck request politely. Offer a smaller piece of information and explain why a short conversation will answer their question faster.

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

Send a video when the prospect doubts the product exists or wants proof of the workflow. Send a one-page PDF when they need something to forward internally.

**How many times should I try to move them to a call?**

Twice. After that, send the information they asked for and move to a low-pressure follow-up. If they reply again, answer the question and offer a call once.

**What if they ask for pricing before a call?**

Give a starting range and name the two factors that change the final number. Then ask whether budget is set or if they are building a case.

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