8 min read
What to do when a prospect says "just send me some information"
Written by the ReplyCircuit team · Last verified September 2026
The reply sounds like interest, so the rep does too much: a 12-page brochure, a generic capabilities deck, maybe a price list — then silence. No follow-up task, because the ball is "in their court". No note on the record, because nothing happened worth logging. Two weeks later nobody knows whether the prospect opened any of it, the thread is buried, and a contact who replied to your sequence — which most never do — has quietly gone cold. The brush-off worked exactly as intended: it ended the conversation politely.
The short answer
- "Just send me some information" is usually a polite brush-off — treat it as a test of intent, not a buying signal.
- Answer with one specific, short thing and one question; the full deck ends conversations instead of advancing them.
- Send it through a tracked link and set a follow-up task in days — an open is a signal, silence is an answer.
The manual workaround
- Read the reply for intent before you attach anything: did they name a topic, give a timeline, or ask a question back? Three tells separate real interest from a polite exit.
- Send one specific, short thing matched to their situation — never the full deck.
- Ask exactly one question in the same email, so the reply tests whether the interest is real.
- Share it through a tracked link (HubSpot's documents tool) so an open is a signal, not a mystery.
- Pause the sequence, log what was sent on the record, and set a follow-up task a few days out — days, not weeks.
With ReplyCircuit
- ReplyCircuit classifies the reply as a soft information request and flags the intent level — genuine question or polite brush-off.
- It pauses the sequence so the next step doesn't land on someone who just asked you to slow down.
- It keeps the request and intent on the record so your team can choose the right resource and response.
- It drafts the follow-up task and logs the request on the record — the review card shows the HubSpot work for a one-tap approval.
The most common reply in outbound is a test
"Just send me some information" arrives more than any other reply, and it gets the worst handling — not because reps are lazy, but because it sounds like a yes. It isn't. Most of the time it's the politest available exit: easier than saying no, and it ends the conversation with everyone feeling fine. Sometimes it's genuine. The reply itself can't tell you which — only your response can.
The standard response fails the test in both directions. The rep attaches the full deck — twelve pages of everything, in case something lands — which is homework the prospect never asked for. Then nothing is logged and no task is set, because the ball is "in their court". Two weeks later the thread is dead and nobody can say whether the deck was even opened. The brush-off worked: polite, final, invisible.
The world-class response is smaller and sharper. One specific, short thing matched to their situation. One question that tests whether the interest is real. A tracked link so an open is a signal rather than a mystery. And a follow-up task dated in days — because unlike the competitor reply, there's no renewal window to wait for. The only asset here is recency.
That is the manual version — and it has two failure points. The first is the deck reflex: under inbox pressure, attaching the big brochure is faster than choosing the one right page. The second is the follow-up that never gets scheduled, because "ball's in their court" feels like an outcome. ReplyCircuit identifies the request, pauses the sequence, logs the context, and prepares the follow-up task the moment the reply lands.
Start a free trialThe by-hand routine (how teams do it today)
Teams that handle this well without tooling all do a version of the same five steps. It works — the cost is judgement at inbox speed:
1. Read for intent first. Before you attach anything, look for the three tells: did they name a topic, give a timeline, or ask a question back? "Send me something on pricing" is a different reply from "send me some information" — the first gets your full attention, the second gets the correct, cheap handling.
2. Send one specific thing. Not the deck — the one page or two-minute read that matches their world. You're respecting the literal request ("some information") while keeping the commitment small enough to actually happen.
3. Ask one question in the same email. "Is bid admin actually eating time on your side, or is it more the reporting?" The reply — or its absence — is the intent test. A brush-off goes quiet; real interest answers a specific question with a specific answer.
4. Share it as a tracked link. Upload the document in HubSpot (Sales > Documents) and send the shareable link rather than an attachment. HubSpot records the open on the contact record — now "did they even look at it" is a fact, not a guess.
5. Pause the sequence and set the task. Pause them out of the cadence (sequences → your sequence → pause the enrolment), log what you sent and when on the record, and create a follow-up task (contact record → create task) three to five business days out. Opened the doc? Follow up tomorrow. Silence? Follow up anyway, once, then close the file honestly.
Done properly that's four minutes per reply. Its failure mode isn't refusal — it's that attaching the big deck is faster than choosing the right page, and "ball's in their court" feels like a finished task instead of a missing one.
Every "send me information" reply is a rep-hour decision
Handle it wrong and it costs you a deck, a dead thread, and a contact who replied once and never will again. Handle it right and it costs four minutes: one page, one question, one task. ReplyCircuit reads the reply the moment it lands, pauses the sequence, logs the request, and puts the follow-up task in front of you for one-tap approval — so the most common reply in outbound stops being the most wasted one.
Start your 14-day trialNo credit card · Cancel any time
Why the deck reflex loses
Sending everything feels like maximum effort. It's actually minimum thought — and the prospect can tell. A generic twelve-page deck says "I didn't read your reply closely enough to know what you need", which is precisely the suspicion a brush-off was testing. The rep who sends one relevant page reads as someone worth replying to; the rep who sends the library reads as a mail merge with a pulse.
There's a second, quieter cost: the deck spends your whole story at the moment of lowest intent. If they skim it and it misses, the follow-up has nothing new to say — "did you get a chance to read it?" is the weakest sentence in sales. Send one page and the follow-up has somewhere to go: the answer to your question, the second resource, the specific thing they reacted to.
And none of it is measurable as an attachment. A tracked document link converts the dead zone into a signal — opened twice on Thursday is a warm follow-up on Friday; unopened in five days is your answer, delivered without an awkward email. HubSpot's documents tool does this out of the box on paid Sales or Service Hub seats; without it, a link to a single relevant page on your own site beats a PDF attachment for the same reason.
What ReplyCircuit does with an information request
ReplyCircuit reads the reply the moment it lands and classifies it as an information request — and reads the intent with it. A named topic or a timeline flags as genuine interest and gets surfaced as warm; the vague "send me some information" flags as the brush-off pattern and gets the correct, cheap handling. Either way, the sequence pauses so no further steps fire at someone who just asked you to slow down.
It then prepares the HubSpot work: a follow-up task dated days out rather than weeks and the request logged on the record with its original context. The review card shows that work in one place; you approve it in seconds. ReplyCircuit does not choose a resource or write or send the email response; those decisions stay with your team.
The compounding effect is honesty in the pipeline. Every information request ends up classified and scheduled for follow-up — or closed out on purpose. No more contacts drifting in a maybe-state because someone sent a deck in March and never found out if it was opened.
What to expect afterwards
The first change is that the reply rate on the follow-up climbs — because the follow-up now has something to say. "You asked about X — here's the one page, and my question still stands" lands completely differently from "just bumping this to the top of your inbox". One is a professional continuing a conversation; the other is a stranger asking for attention twice.
The second change is that your pipeline tells the truth about these contacts. Instead of a fog of maybes who got a deck once, every information request resolves: real interest, worked properly — or a polite brush-off, closed honestly with everything logged. Both are wins. The expensive version is the one most teams run: a thread that dies slowly and a record that says nothing about why.
What an information request actually looks like
From: p.lindqvist@northbuild.ca
Subject: Re: cutting bid admin for your estimating team
Hi,
Thanks for reaching out — just send over some information and I'll take a look when I get a chance.
Peter Lindqvist — Operations Manager, Northbuild Construction
The ask
"Some information" — no topic named, which is tell #1 of a low-intent request
The timeline
"When I get a chance" — no urgency, no decision point. Tell #2
The exchange
No question back to you — a genuinely interested reader asks something. Tell #3
Received
Tuesday — if there's no task dated this week, this thread is already dying
What kills it
Sending the 12-page deck, logging nothing, and never following up because the ball is "in his court"
What ReplyCircuit does with that exact reply
The same message arrives at your processing address. Here is the review card the rep sees:
Information request · low intent · 92% confidence
- Contact
- Peter Lindqvist — Northbuild Construction
- Intent read
- Brush-off pattern: vague ask, no timeline, no question back — handle fully anyway
- Sequence
- Paused — no further steps fire while the information request plays out
- Follow-up task
- Drafted for 4 business days out — days, not weeks, because there is no contract window to wait for
- Logged
- Request, what was sent, and the date — on the record, so the thread can't die invisibly
Copy-paste: the one-thing, one-question reply
The whole strategy in one email: a single short resource matched to their world, one question that tests intent, and a stated follow-up so the thread has a future either way. Notice what's not here — the brochure, the deck, the pricing PDF.
The one-thing, one-question reply
Subject: Re: {{original_subject}}
Hi {{first_name}},
Happy to. Rather than a generic brochure, here's the one page that matters most for {{their_situation}} — it's a two-minute read: {{tracked_link}}
One question while it's in front of you: {{qualifying_question}}?
If I don't hear back, I'll follow up early next week with anything that's useful. Either way, no more sequence emails from me in the meantime.
{{your_name}}Common questions
Sources
Keep reading
"Send me some information" is a test — most reps fail it by passing too hard
ReplyCircuit classifies every reply and keeps HubSpot accurate automatically.
Start your 14-day trial14-day free trial · No credit card · Cancel any time