# How to respond when a prospect asks for more info on a specific topic
> Stop giving away too much in LinkedIn chats. Use the bridge framework to answer feature questions and turn them into booked sales meetings today.
- HTML: https://getkinlead.com/reply-to-prospect-asking-for-more-info-on-linkedin
- Markdown: https://getkinlead.com/reply-to-prospect-asking-for-more-info-on-linkedin.md

**Short answer:** Don't send manuals or long lists when a prospect asks about a feature. Give a brief answer that proves you can solve the problem, then explain why the full answer depends on their specific setup. That gap is a real reason to book a call, and it keeps you in the conversation.

## The mistake of the information dump

When a prospect asks how a feature works, the instinct is to prove the product is powerful by explaining everything. You write four paragraphs, attach a PDF, and paste a link to the docs. It feels helpful. It usually ends the conversation.

Giving away every detail removes the reason to talk to you. If the prospect thinks they have enough to decide, they'll go quiet and decide alone, and the answer is often no. A wall of text also reads like work. People archive chats that look like homework.

There's a second cost. Long answers make you sound like a brochure. The person on the other end is working out whether you understand their problem, and a feature list doesn't answer that. They asked one question. They didn't ask for the manual. Answering more than they asked makes them scroll, and scrolling is how chats die.

Being vague is worse than being long. 'It's fully customizable' annoys people more than a paragraph does. Be short, be specific, then stop.

**The information dump**

- Four paragraphs covering every technical detail.
- A full product manual or a 20 page PDF attached to the chat.
- Every use case the feature supports, listed in order.

**The bridge**

- Two sentences that prove the feature solves their problem.
- One line on why the full answer depends on their setup.
- A specific ask for 15 minutes.

## The three part response framework

You need to give enough to earn trust and leave a gap that only a conversation fills. I call it the bridge: a short answer that proves the capability, then a reason the details depend on them. A good bridge takes about 30 seconds to write. If it's taking longer, you're probably explaining the product instead of the outcome. It works in a chat and in an email.

The dependency has to be real. If you say 'it depends on your setup' when it genuinely doesn't, the prospect will notice and stop trusting you. Pick the thing that actually changes the answer: their team size, how many leads they touch in a week, whether one person owns the inbox, which CRM they run.

1. **Confirm the feature exists.** One line. 'Yes, it does that.' Don't qualify it into a paragraph.
2. **Name one outcome.** Say what changes for the person using it. 'Most teams use it so a lead doesn't go cold after the first message.' Outcome, not process.
3. **Name the real dependency.** Pick the thing that actually changes the answer, then ask for a short call. If you can't name a real dependency, the feature probably isn't worth a call, and you should say so and move on.

## Turning a feature question into a meeting

In a real chat this is four lines, not four paragraphs. Keep it conversational. Formal language reads like a template and slows the reply down.

Notice what the reply does. It answers yes, gives one outcome, names a real variable, and asks for a specific 15 minutes. It doesn't hide anything. It just doesn't write an implementation guide in a chat window.

The variable matters more than the wording. Volume versus high touch is a real fork: the same feature gets set up differently, and the prospect knows it. If you pick a fake variable, the question sounds like a stall. Pick one you'd genuinely need to know before you could set the thing up.

Don't ask 'do you want to hop on a call?' That's easy to ignore. Offer a day and a length. '15 minutes Tuesday' gets a yes or a counter, and both move things forward. Keep the ask to one sentence. Two questions in one message gives the prospect a choice of what to ignore.

- **them:** Does your tool handle automated follow ups on LinkedIn?
- **you:** It does. Most teams use it so a lead doesn't go cold after the first message.
- **them:** How does the sequencing work?
- **you:** That part changes depending on whether you're running high volume or high touch. Do you have 15 minutes Tuesday to see which setup fits how Acme runs now?

## Handling the 'just send me a deck' pushback

Some prospects ask for a deck, a Loom, or a one pager. Often that's a reflex to avoid another call. Sending the full deck hands them a reason to decide without you, and they'll skim it in half a minute.

Give them a small piece instead. A 45 second clip of the exact feature they asked about proves you aren't hiding anything and keeps the conversation open. The clip does one job: it shows the thing works. It doesn't need music, a title card, or a script. A screen recording with your voice is enough, and it takes two minutes to make.

If they insist on the deck after the clip, send a short one. Two or three slides on the feature, no pricing, no case studies. Then ask the question again.

1. **Record 45 seconds on the exact feature.** Screen and voice. Only the thing they asked about. No product tour.
2. **Put their name and company in it.** Say 'since Northwind runs a two person sales team' in the first ten seconds. It shows the clip is for them.
3. **Re-bridge in the message.** After the clip: 'The part I can't show in a video is how this maps to your pipeline. Worth a short call?'

> The full deck ends the conversation. A 45 second clip keeps it open.

## When they ask about price, security or integrations

These questions feel like they need a document. Most need one line and a reason to keep talking. The pattern is the same as a feature question: answer the part that builds trust, hold the part that needs their context.

Pricing is the one people get wrong most often. Sending a number before you know their seat count invites a comparison you can't win. Sending nothing looks evasive. A starting point plus what changes it does the job.

| | What they ask | What to send | What to hold back |
| --- | --- | --- | --- |
| How much does it cost? | A starting point and what changes it | A full quote before you know their seat count |
| Is our data safe? | A one line answer and a link to your security page | The 40 page questionnaire before they've seen the product |
| Does it work with our CRM? | Yes or no, and the name of the integration | A field mapping walkthrough |
| Can it handle our volume? | One sentence on the biggest account you've run | A capacity planning spreadsheet |
| Can we see just this feature? | A 10 minute call on that feature alone | The full 45 minute demo |

## What to do when they go quiet after your answer

Plenty of people who ask a feature question and get a bridge reply will go quiet. That's normal. They got a useful answer and went back to their day.

Don't send 'just following up'. Send one more small piece of the answer and repeat the ask once. The follow-up works because it adds something. A nudge that only asks for attention gets ignored, and it also tells the prospect you have nothing new.

Timing matters too. Wait three or four days before the follow-up. A message the same afternoon reads as pushy, and a message two weeks later gets buried.

```
Hi [Name], one thing I left out on the [feature] question: [one detail that matters for their setup]. Worth 15 minutes on [day] to see whether it fits how [Company] runs [process]?
```

## Doing this with Kinlead

Kinlead handles the early part of these conversations. Each campaign chooses how replies are handled: hand the conversation to you at the first reply, let the AI reply until there is real interest, or let the AI reply until a meeting is booked using your scheduling link. For feature questions, hand-off mode is the one that fits, because you want to write the bridge yourself.

Replies from every campaign land in one inbox, classified by intent, with interested replies first, and you get an email when someone replies. A feature question doesn't sit unread while you're doing something else. Outreach runs from your own LinkedIn account at a human pace, one action every five minutes, inside the limits and send window you set. The reply modes are explained on the [AI LinkedIn outreach](/features/ai-linkedin-outreach) page.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Automating meeting bookings](https://getkinlead.com/automating-linkedin-meeting-bookings.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**Should I send a pricing sheet when they ask about a feature?**

No. Pricing is a separate conversation about value. If you send a price sheet alongside a feature explanation, the prospect will judge the feature by the cost rather than the result.

**How short should the teaser answer be?**

Keep it to two sentences. One to confirm the capability and one to describe the primary benefit. Anything longer looks like an information dump.

**What if the feature is the only reason they are interested?**

That is the best time to use the bridge. If the feature is that important, they'll be more willing to jump on a 15 minute call to make sure it solves their specific problem.

**What if they ask the same question twice?**

Answer it once more, slightly differently, and name the dependency again. If they still push for the full detail in writing, offer the 10 minute call on that feature alone and stop there.

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