How to Handle "Send Me Some Information"

How to Diagnose Intent Before You Respond

You have a few seconds. The goal is not to run through a checklist in your head but to read the situation quickly using context you already have from the call. Four signals tell you most of what you need to know.

Timing on the call: early exit versus late stall. When the request comes matters more than almost anything else. If it arrives in the first two or three minutes, before you have had a real exchange, it is almost certainly a polite brush-off. The prospect has not heard enough to be genuinely curious, which means they are not asking for information because they want it. They are asking because they want the call to end. If the request comes later, after some back-and-forth, after a product question, or after a price mention, the situation is more ambiguous. That version is more likely to be a stall or genuine interest, and it is worth a clarifying question before you respond.

What the prospect said immediately before. The sentence that precedes the request is often the most useful signal. A prospect who says "we're pretty happy with what we have, but send me some information" is almost certainly exiting. A prospect who says "that's interesting, how does it handle X, actually, just send me some information" may have gotten distracted or uncertain mid-thought. A prospect who says "I'd need to show this to my manager, can you send something over?" is giving you a real reason with a real next step embedded in it. The content of that prior sentence tells you whether the request has any substance behind it.

Tone and energy as a signal. Tone is harder to describe but easy to feel. A prospect who has been engaged, asking questions, and responding with some energy, and then asks for information, is in a different situation than one who has been giving one-word answers since the call started. Flat tone, short responses, and minimal engagement throughout the call are consistent with a brush-off. Energy that drops suddenly at the moment of the request often signals a stall: something shifted, and the prospect is retreating to a safe phrase while they process it.

Whether discovery has happened yet. If you have not yet asked meaningful questions about the prospect's situation, their request for information creates a practical problem: you do not know what to send. That is actually useful. It gives you a natural, non-confrontational reason to keep the conversation going. You can acknowledge the request and honestly explain that you want to make sure what you send is relevant to their situation, which requires knowing a bit more. This is not a manipulation tactic. It is true, and it opens a door.

A quick diagnostic question to clarify intent. When timing and tone leave you uncertain, one question usually resolves it. Something like: "Of course. Before I put something together, can I ask what specifically prompted you to take this call today?" or "Happy to do that. What would be most useful for me to include?" A prospect who is genuinely interested will answer. A prospect who is exiting will give a vague or dismissive response, which tells you exactly where you stand. The question does not feel confrontational because it is framed around making the follow-up more useful, not around challenging their intent. It also buys you a few more seconds of conversation, which is often enough to shift the dynamic.

What to Say Immediately After: A Step-by-Step Response Structure

When a prospect says "send me some information," it is common to feel a pull toward compliance. Agreeing feels polite, and sending something feels like progress. It is usually neither. The goal in the next thirty seconds is to acknowledge the request without surrendering the conversation, surface what the prospect actually needs, and give yourself a path back to a real exchange. The sequence below does that in four steps.

Step 1: Acknowledge without immediately agreeing

The first thing you say should not be "absolutely" or "sure, I'll get that over to you." Those responses close the conversation before you understand what the prospect is asking for or why. Acknowledging the request is different from agreeing to it on the spot. You are signaling that you heard them, not that you are complying before you know what would actually be useful.

Example language: "Happy to send something over." Full stop. Do not add "I'll do that right now" or "let me grab your email." Pause and move to the next step.

Step 2: Ask a clarifying question to surface intent

This is the most important step. A single, calm question asked immediately after the acknowledgment does two things: it tells you whether the prospect is genuinely curious or trying to exit, and it keeps you in the conversation rather than handing control over to an inbox.

The question should feel natural, not confrontational. You are not challenging the request. You are trying to understand what would actually help them.

Example language: "So I can make sure I send you something relevant, what specifically were you hoping to look at?" Or: "Was there a particular part of what we covered that you wanted to dig into more?" Or, if the call is early and discovery is incomplete: "Before I pull something together, help me understand what's most important to you right now."

The answer to this question tells you almost everything. A prospect who gives a specific answer ("I want to see the pricing breakdown" or "I'd like to share the case study with my partner") is genuinely engaged. A prospect who says "just the overview" or "whatever you have" is usually trying to close the call without saying so directly.

Step 3: Re-anchor to the conversation

Once you have a clarifying answer, use it to pull the conversation back to the prospect's situation rather than pivoting immediately to logistics. This is where you reconnect what they asked for to what they told you earlier in the call. A re-anchoring phrase does not have to be long. It just has to make the transition feel natural rather than forced.

Example language after a specific answer: "That makes sense given what you mentioned about [their situation]. Let me ask you one more thing before we wrap up, because it'll help me make sure what I send is actually useful to you." Then ask the next discovery or qualification question you need.

Example language after a vague answer: "I can do that. I want to make sure it's worth your time to read, so let me ask, what would need to be true for this to be something you'd move forward on?" This is not a hard close. It is a question that surfaces whether there is a real conversation to be had.

Step 4: Offer something specific, not a generic deck

If you reach the end of the exchange and sending something is appropriate, name what you will send rather than offering an open-ended package. A generic one-pager or a full product deck signals that you did not listen. A specific, targeted piece signals that you understood what they need and took it seriously.

Example language: "I'll send you the one-page breakdown on [specific feature or outcome they mentioned], along with a short note on how we've handled [their specific situation]. That should give you what you need to evaluate it."

Pair this with a confirmed next step before you get off the call. More on that in the next section.

How the sequence looks across three scenarios

The brush-off scenario (prospect asks early, before discovery is complete): "Happy to send something over. So I know what to pull together, what were you hoping to get a better look at?" If the answer is vague, re-anchor: "Got it. Before I do that, I want to make sure what I send is actually relevant to your situation. Can I ask you a couple of quick questions?" Prospects who are not actively hostile will often say yes. You have preserved the call.

The genuine-curiosity scenario (prospect asks after a product or pricing question): "Happy to send that. Was there a specific part of the pricing you wanted to look at in more detail, or were you thinking about sharing it with someone else on your team?" This question is low-pressure and diagnostic. If they say they want to share it with a decision-maker, you have just uncovered a stakeholder you did not know about. That is a useful discovery, not a dead end.

The late-call stall (prospect asks after a closing attempt): "Of course. Help me understand what you'd be looking for in what I send, because I want to make sure it actually moves things forward for you." Then: "If the information answers that question, is this something you'd be ready to move on?" You are not pressuring them. You are clarifying what decision the information is meant to support, which is a reasonable thing to ask.

Should You Actually Send Information?

Sometimes yes. Usually not a generic deck. Avoid sending anything as a substitute for a confirmed next step.

Sending something after a call is not inherently wrong. The problem is what gets sent, and whether it replaces or supports the next conversation. A targeted, specific piece of content that addresses a question the prospect raised can be genuinely useful. A full product overview sent because the rep did not know what else to do is rarely read and tends not to move a deal forward on its own.

When sending something is appropriate: The prospect asked a specific question you could not fully answer on the call. They need to share information with a stakeholder who was not on the call. They requested a specific document such as a case study, a pricing summary, or a technical spec. In each of these cases, what you send has a clear purpose tied to something the prospect told you.

What to send versus what not to send: Send the one thing that answers the specific question or serves the specific purpose they named. Do not send a general capabilities deck, a full product PDF, or a link to your website and let them figure it out. If you cannot name what you are sending and why it addresses something the prospect said, you are sending it for your own comfort, not theirs.

A useful framing: before you hit send, finish this sentence. "I'm sending this because the prospect asked about [specific topic], and this document addresses that directly." If you cannot complete the sentence, reconsider what you are sending.

Pair it with a confirmed next step. Information sent without a scheduled follow-up is a conversation that has effectively ended. Before you get off the call, confirm when you will reconnect and what you will be discussing. "I'll send that over today. Let's plan to talk [specific day] so I can answer any questions after you've had a chance to look at it." If the prospect will not commit to a next step, that tells you something important about where the deal actually stands. It is better to know that before you spend time assembling a package they may not open.

What to do when a prospect resists scheduling a follow-up. If you ask for a next step and the prospect deflects, that is diagnostic information. A response like "just send it and I'll reach out if I have questions" is a softer version of the original brush-off. You can acknowledge it without accepting it as the final word: "Of course. I'll send it over. I'll also plan to follow up on [specific day] just to make sure it landed and answer anything that comes up." You are not demanding a commitment; you are naming a specific action you will take, which keeps the conversation on your calendar rather than disappearing into theirs.

Common Mistakes Reps Make When They Hear This Request

The deal is rarely lost in the moment the request arrives. It tends to be lost in the ten seconds that follow. The instinct to comply feels professional, but compliance without a plan often ends the conversation before it has a real chance. Here are the most damaging patterns to recognize and eliminate.

Agreeing immediately and ending the call

The rep says "absolutely, I'll get that over to you" and wraps up. The call ends without a booked next step, without discovery, and without any commitment from the prospect. The deal is now on life support before it ever started. Consequence: the prospect has no reason to re-engage, and the rep has nothing to follow up on.

Sending a generic deck or brochure

The rep fires off a standard one-pager or a company overview PDF that was not tailored to anything the prospect said. The prospect receives something that could have been sent to anyone. Consequence: the material signals that the rep was not listening, and the prospect has no reason to respond because nothing in the document speaks to their situation.

Not asking what information they actually want

The rep assumes they know what the prospect means. They skip the clarifying question entirely and send whatever feels most complete. Consequence: the rep may spend time preparing and sending material the prospect did not need, while the real concern goes unaddressed.

Treating "I'll send it over" as a next step

Sending an email is not a next step. A next step requires a commitment from the prospect: a scheduled call, a specific date, a defined action they will take. When the rep logs "sent follow-up email" as progress, the deal is usually stalled. Consequence: the pipeline looks active but nothing is moving.

Following up on the email instead of re-opening the conversation

The rep sends the material, waits a few days, then sends a follow-up that says "just checking in to see if you had a chance to review." This puts the rep in a passive position and hands all control to the prospect. Consequence: the rep is now chasing instead of leading, and each follow-up without a response makes re-engagement harder.

Misreading a vague answer as confirmation of interest

After asking a clarifying question, the rep receives a non-answer: "just send whatever you have" or "anything is fine." Rather than treating this as a signal that the prospect may be exiting, the rep interprets it as permission to proceed and sends a full package. The vague answer was the prospect's second attempt to close the call. Sending a comprehensive deck in response does not re-engage them; it confirms that the conversation is over. When a clarifying question produces a vague answer, the more useful move is to name the ambiguity directly: "I want to make sure I send you something worth reading. Is there a specific question you're trying to answer, or is this more about getting a general sense of what we do?" That question is harder to deflect without revealing intent.

The pattern across all these mistakes is the same: the rep treats the request as a task to complete rather than a signal to diagnose. Fixing that instinct starts in practice, not on a live call.

How to Practice This Deflection Before It Costs You a Live Call

Knowing the right response to "send me some information" is not the same as delivering it naturally under pressure. On a live call, the request arrives without warning, often mid-conversation, and the instinct to comply is strong. The only way to override that instinct is repetition before the call, not reflection after it.

Solo verbal drills: lock in the sequence before adding variation

Start without a partner. The goal of a solo drill is to make the acknowledge-clarify-re-anchor sequence automatic so you are not constructing it in real time when a prospect catches you off guard.

Say the request out loud to yourself: "Can you just send me some information?" Then respond aloud, working through the full sequence: acknowledge the request, ask a clarifying question, and transition back to the conversation. Do this ten times in a row. Then vary the phrasing of the request: "Just shoot me an email," "Send me a deck," "Can you put something together for me?" The sequence stays the same; only the trigger changes. When you can move through the sequence without pausing to think, you are ready to add a partner.

A useful variation once the basic sequence feels automatic: practice responding to the request at different points in a simulated call. Deliver your opener, then immediately hear the request. Deliver a full two-minute discovery exchange, then hear it. The sequence is the same, but the re-anchoring step changes depending on what you have already learned about the prospect. Practicing both versions prevents the common failure of handling the early brush-off well but freezing when the request arrives late in a call.

Peer roleplay: vary tone, timing, and prospect scenario

Solo drills lock in the structure. Peer roleplay stress-tests it. Ask a colleague to play the prospect and vary three things: tone, timing, and scenario.

Tone variation matters because the request sounds different when a prospect is genuinely curious versus politely exiting. A flat, clipped "just send me something" is not the same as a warmer "that sounds interesting, can you send me more details?" Your response needs to work across both. Timing variation matters because the request can arrive early in a call before any discovery has happened, or late after a price question. The clarifying question you ask should shift depending on where you are in the conversation. Scenario variation keeps the practice realistic: a cold call prospect asking for information is different from a warm inbound lead doing the same thing. Run at least five rounds with your partner rotating through different combinations before switching roles.

After each round, the person playing the prospect should give brief feedback on two things: did the acknowledgment feel natural or defensive, and did the clarifying question feel like genuine curiosity or like a tactic? Those two impressions are what a real prospect will have, and they are worth knowing before you face the situation live. If the clarifying question consistently feels like a tactic, the phrasing needs work, not the structure.

AI-assisted simulation: repeated reps with structured feedback

Peer roleplay is valuable but limited by availability. AI-assisted practice gives you a way to run realistic simulated conversations repeatedly, at any time, and receive structured feedback on how you handled the exchange. Platforms built for AI sales roleplay can simulate prospect behavior across different call types and difficulty levels, then score the session and return specific feedback on where the response held up and where it broke down.

For this specific deflection, a useful practice format is a cold call or qualification call scenario set to medium or hard difficulty, where the prospect is likely to push back or disengage quickly. After the session, review the feedback on how you handled the moment the request appeared: did you acknowledge it, did you ask a clarifying question, did you re-anchor, and did you maintain control of the conversation? If the same weakness appears across multiple sessions, that is the part of the sequence to isolate and drill further. For a broader approach to building this kind of deliberate repetition into your practice, the guide on how to practice objection handling covers the full framework.

RepLift supports AI sales roleplay practice across call types including Cold Call and Qualification / Setter Call, with configurable difficulty and structured scoring after each session. After a session, you receive an overall practice score, dimension-level scores, strengths, weaknesses, and evidence-based feedback. You can review previous sessions and observe whether the same weaknesses keep appearing, which makes it easier to decide where to focus next. If RepLift identifies a weakness in a session, it can recommend more focused next practice so the following session concentrates on that area rather than repeating the full call from the top. If you want to try it, you can apply for RepLift Private Beta.

What to review after each practice session

After any practice session, whether solo, peer, or AI-assisted, ask three questions. First: did you acknowledge the request before redirecting, or did you immediately push back? Skipping the acknowledgment makes the response feel confrontational. Second: did your clarifying question actually diagnose intent, or was it vague? A question like "what would be most useful for you to see?" is better than "what kind of information do you want?" Third: did you re-anchor to the prospect's problem, or did you pivot to your product? The re-anchor should connect back to something the prospect said, not to a feature you want to explain.

A fourth question worth adding once the basic sequence is solid: did you secure a next step before the practice session ended, or did you let the conversation close on "I'll send it over"? The sequence is not complete until a specific follow-up is on the calendar. If you consistently nail the acknowledge-clarify-re-anchor steps but still end sessions without a confirmed next step, that is the gap to close next.

How to know when the response is ready for live calls

The response is ready when you can deliver the full sequence, acknowledge, clarify, re-anchor, without hesitation across at least three different prospect tones and two different call stages. If you still pause before the clarifying question, or if you skip the re-anchor when the prospect pushes back a second time, keep practicing. The standard is not perfection; it is automaticity. When the sequence runs without conscious effort, it will hold up when a real prospect uses this deflection to end the call.