How agencies handle "send me more info" replies without dumping a deck
"Can you send me more info?" lands in the shared inbox and someone on the agency team feels good about it. It reads like interest. It gets tagged positive. A deck goes out within the hour, and then nothing happens for three weeks.
That pattern is common enough that most objection-handling guides now treat the phrase as a soft deflection first and a real request second. Quarvio puts it bluntly: prospects who are ready to buy ask about pricing, and prospects who want to end the conversation politely ask for information. Brazn's write-up makes the same call and says the instinct to comply right away is the mistake. Bulk Mail Verifier's reply framework is a little more generous. It says the request can be real curiosity, but more often it is a way to defer deciding whether a conversation is worth having.
Both readings can be true on the same day. The job is to find out which one you have before you spend effort, and to do it the same way across every client workspace.
Tag it as its own reply class
Most agency reply taxonomies have positive, negative, out of office, wrong person, and unsubscribe. "Send info" usually gets shoved into positive. That inflates the client's positive reply count and hides a real gap between replies and conversations booked.
Give it its own label. Something like info-request is enough. Three things follow from that:
- The sequence still stops. Any reply stops the cadence on that contact. Nobody should get step three of a cold sequence after asking a question.
- The reply does not count as a booked conversation or a qualified positive in the client report until it converts.
- You can measure the conversion rate from info request to booked call per client. If one client's info requests never convert, the offer or the targeting has a problem that the first-touch copy is hiding.
Ask one question before sending anything
Every source we read lands on the same first move. Ask a single clarifying question before you attach a file.
Quarvio's template offers a choice: a one-page summary of how the problem gets solved for a similar company type, or a quick breakdown of the math for a company their size, plus a calendar link if a short call is easier. Bulk Mail Verifier suggests asking whether they are evaluating specific capabilities or trying to understand the general approach. SalesArmor lists four things the phrase usually stands in for: real interest with no time right now, a polite brush-off, a stakeholder who needs to weigh in, or a buyer who wants to evaluate without a salesperson in the loop.
That last list is the useful one for agencies, because each case maps to a different next action:
- Real interest, no time. Send the short thing they asked for and offer two specific times.
- Brush-off. Ask directly whether there is still interest or whether timing is off. Brazn recommends this binary question because a clear "not now" is more useful than weeks of silence.
- Stakeholder. Ask who else would look at it and offer something they can forward. This often turns into a referral path inside the account.
- Control. Respect it. Send a tight written answer and make booking easy, without pushing a call.
Keep the question to one line. Two questions in a reply to a cold prospect reads like a form.
Send one asset, never the whole folder
If they answer with something specific, answer that specific thing. Bulk Mail Verifier warns against the full dump: a PDF, a deck, a case study, a one-pager, and a "did you get a chance to review" email three days later. That is homework for someone who was already unsure.
For agency teams, this is where client isolation matters. The asset has to come from that client's approved library, written in that client's voice, and it cannot reference another client's results or names. A one-page summary that lives in the client workspace, reviewed once, beats a rep improvising from a shared drive.
GTM Bud's version is shorter still: two sentences of value, a calendar link, and an offer to send more once you know what matters. That works well when the AI drafted the first touch and a human is handling the reply. It keeps the response honest and short.
Attach a next step, then follow up once
Brazn's rule is never to send information without a defined next step attached. "I'll send that today. Would 15 minutes Thursday work to walk through it?" is the pattern. If you do have to send without a confirmed time, follow up within about 48 hours with a question about the content, not "just checking in."
After that one follow-up, stop. If they go quiet, mark the thread as a soft close in that client's workspace, keep the contact suppressed from the cold sequence, and let the account come back through a new signal later. Restarting the cold cadence on someone who already replied is how agencies earn spam complaints for their clients.
What the agency ops lead should check weekly
- Count of
info-requestreplies per client, separate from true positives - Median time from info request to first human response
- Share of info requests that turned into a booked conversation
- Which asset was sent, and whether it came from the client-approved library
- Any thread that got more than one follow-up after the info request
That last line catches the overeager rep before the client does.
Where GTM fits
GTM runs find, qualify, write, send, reply, and book inside isolated client workspaces. Sequences stop on reply, replies land in a shared inbox, and booked calls follow through to the client's calendar and CRM. A clean reply class for info requests, with one clarifying question and one approved asset, is the kind of handling that keeps "positive reply" meaning something in the client report.
If you run outbound for several clients and want reply handling built this way, join the waitlist.
Sources
- Quarvio, "Cold email objection handling: what to say when they push back": https://www.quarvio.io/blog/cold-email-objection-handling
- Bulk Mail Verifier, "Handling objections in cold email replies": https://bulkmailverifier.com/blog/handling-objections-in-cold-email-replies
- Brazn, "How to handle 'send me more information'": https://www.brazn.ai/blog/how-to-handle-send-me-more-information-objection
- SalesArmor, "How to handle 'send me more information'": https://www.salesarmor.app/objections/send-me-more-information
- GTM Bud, "How to handle cold email replies": https://gtmbud.com/blog/how-to-handle-cold-outreach-replies