How do you coach a rep to handle a prospect who says "just send me some information in 2027

What This Objection Is — And Why RevOps Should Care

"Just send me some information" is one of the highest-frequency stalls a rep will hear, and it is rarely a genuine request for a PDF. It is a low-friction way for a prospect to end an uncomfortable call without saying "no." For a RevOps leader, this matters far beyond one rep's win rate — it is a pipeline hygiene problem. Every time a rep complies without qualifying, a genuinely unqualified lead gets logged as "engaged" in the CRM, inflating pipeline coverage with deals that will never close. By 2027, with buyers doing more pre-call research through AI assistants and self-serve content than ever, the reps who still reach a live conversation are talking to prospects who could have found generic information themselves — which means the request to "just send information" is almost always a signal of low urgency, not a genuine information gap.

Coaching a rep to handle this well changes two numbers RevOps actually tracks: stage-to-stage conversion out of early pipeline, and the accuracy of forecast categories. A rep who pivots the objection into a qualifying question either advances a real opportunity or disqualifies a fake one within the same call — both outcomes are better than a ghost deal sitting in "information sent" purgatory for six weeks. The coaching goal is not to make reps more aggressive; it's to make the moment diagnostic. Every "send me info" moment should produce one of three outcomes: a qualified next step, a clean disqualification, or (rarely) a genuinely informed prospect who needs material before they can engage further. Reps who don't have this instinct will default to compliance, because compliance feels safe and refusal feels risky. Your coaching job is to make the qualifying question feel just as safe.

The Step-by-Step Coaching Process

Build the coaching plan as a four-step cycle you run with every rep, not a one-time training session. Each step has a specific behavior to install and a way to check it landed.

Step 1 — Diagnose the current default. Pull five recent call recordings or CRM notes where a prospect said some version of "just send me info." Note exactly what the rep did next: did they comply immediately, push back awkwardly, or pivot smoothly? Most reps you coach for the first time will fall into pure compliance more than half the time. This baseline is what you'll measure improvement against.

Step 2 — Install the acknowledgment-then-pivot script. Teach a two-part response: acknowledge the request (so the prospect doesn't feel deflected), then ask one specific, open-ended qualifying question tied to their business, not yours. Example: "Happy to send that over — quick question so I send the right thing: what's driving you to look at this now?" The rep should practice this until the acknowledgment and the pivot come out as one fluid sentence, not two separate, hesitant moves.

Step 3 — Role-play under resistance. The scripted version is easy. Coaching only sticks when the rep has practiced it against a prospect who pushes back a second time ("I really just want the PDF"). Here the rep needs a second-layer response: restate willingness to send, then attach a condition — a specific follow-up time — before sending. This is the step most coaching programs skip, and it's the one that determines whether the rep folds under mild pressure.

Step 4 — Review live calls and correct in the moment. Nothing replaces listening to the rep handle this objection live and giving feedback within 24 hours, while the call is still fresh. Use a simple pass/fail per call: did the rep ask a qualifying question before agreeing to send anything? Track this weekly per rep.

Costs, Timelines, and Typical Coaching Ranges

Coaching this specific objection is inexpensive relative to most sales enablement investments, but it needs a realistic timeline. A single 45-60 minute role-play session gets the script into a rep's short-term memory; it takes three to five repeated live-call reviews, spread over two to three weeks, before the pivot becomes an unconscious habit rather than something the rep has to consciously remember mid-call. Budget roughly 20-30 minutes of manager time per rep per week during the reinforcement period — this is coaching time you're likely already spending on call reviews, just redirected toward one specific skill instead of general feedback.

If you're formalizing this into a broader RevOps enablement motion, expect a typical rollout to a team of 8-12 reps to take four to six weeks: one week to build and test the script and role-play scenarios, one to two weeks of initial training and role-play, and two to three weeks of live coaching reinforcement before you can trust the behavior has stuck without direct oversight. Larger sales orgs (50+ reps) usually need a train-the-trainer layer — front-line sales managers coached first, then cascading the drill to their teams — which extends the full rollout to eight to ten weeks but scales far better than a single RevOps or enablement lead trying to personally role-play with every rep.

On the metrics side, set your improvement window at four to six weeks post-coaching before drawing conclusions. Pivot rate (the percentage of "send me info" moments where the rep asks a qualifying question first) typically moves fastest — often visible within the first two weeks — because it's a binary behavior that's easy to self-monitor. Downstream metrics like stage conversion and forecast accuracy take a full sales cycle to reflect the change, which for most B2B RevOps orgs means six to twelve weeks depending on deal cycle length. Don't judge the coaching a failure before that window closes.

Where RevOps Teams Get This Wrong

The most common mistake is treating this as a script problem when it's actually a confidence and reinforcement problem. Handing a rep a card with the pivot question written on it changes nothing if the rep still feels like asking a question is "pushy." Coaching has to address the underlying belief — that qualifying is a service to the prospect, not an imposition — before the script will stick under real pressure. Reps who intellectually understand the pivot but still fold on live calls almost always have this unresolved belief problem, not a knowledge gap.

A second frequent error: RevOps builds a CRM field or tag to track "information requested" but never closes the loop with a required qualifying-question field or a mandatory follow-up date. Without that structural gate, the tracking becomes passive reporting instead of an enforcement mechanism, and reps quietly revert to old habits within a few weeks because nothing in the system actually requires the new behavior. If you want the coaching to hold, build the qualifying question and the follow-up commitment into the CRM workflow itself — not just into the training deck.

Third, teams over-rotate on the script and under-invest in listening for the *answer*. A rep can ask a perfect qualifying question and then completely ignore the answer, sending the same generic deck regardless of what the prospect said. Coach reps to actually reference the prospect's stated problem in whatever they send — a one-line personalized note beats a longer, generic attachment every time, and it's the detail that turns "I'll look at it" into an actual reply.

Finally, some managers coach the objection once and never revisit it, treating it as a solved problem after a single good role-play. Objection-handling skills decay without reinforcement — build a quarterly refresh into your coaching cadence rather than assuming a skill taught once in Q1 survives untouched into Q4.

Decision Framework: When to Push, When to Send, When to Disqualify

Not every "send me info" moment should be handled identically, and part of coaching a rep well is teaching judgment, not just a script. Use this framework to help reps decide in real time:

If the prospect answers the qualifying question with a specific, business-relevant problem, the rep should treat this as a green light to advance — set a discovery call rather than just sending a document, since the prospect has already shown engagement. If the prospect deflects the qualifying question but doesn't hang up or get annoyed, the rep should send a short, personalized piece of information with a firm, pre-agreed follow-up date attached — this is the middle path, appropriate for a prospect who may be early-stage but not yet a lost cause. If the prospect gets irritated by a single respectful question, or refuses to say anything about their situation at all, that itself is diagnostic: coach the rep to politely disqualify and move on rather than chasing a lead that was never going to convert. Chasing every stall equally wastes as much rep time as complying with every stall automatically.

Related questions

What should a rep do if the prospect insists on getting information with no conversation at all?

Send one short, personalized document tied to what little context you have, and attach a specific follow-up date before sending — never send information with no next step defined.

How do you know if "send me info" is a real stall versus a legitimate early-stage need?

Ask one qualifying question. A genuinely interested prospect will answer with specifics; a stalling prospect will deflect, get vague, or seem annoyed by the question.

Should this coaching differ for inbound versus outbound prospects?

Yes — inbound prospects who filled out a form have already shown some intent, so the qualifying question can be lighter; cold outbound prospects need a more deliberate pivot since urgency hasn't been established yet.

How often should a coach revisit this specific objection with a rep?

Reinforce weekly for the first month after initial training, then fold it into a quarterly objection-handling refresh so the skill doesn't decay.

FAQ

Why do prospects say "just send me some information" so often? It's a socially easy way to end a call without saying no outright. Most of the time it reflects low urgency or unfelt pain rather than a genuine need for a document.

Is it ever appropriate for a rep to just send the information without asking anything? Only when the prospect is already clearly qualified from prior context — even then, coach the rep to attach a specific follow-up rather than sending and waiting passively.

What's the single most important thing to coach first? The acknowledgment-then-pivot sequence: acknowledge the request so the prospect feels heard, then immediately ask one specific qualifying question in the same breath.

How do I measure whether the coaching is actually working? Track pivot rate (how often the rep asks a question before sending) weekly, and track downstream stage conversion and forecast accuracy over a full sales cycle, typically six to twelve weeks.

What if the rep feels like asking a question is too pushy? Role-play the exact scenario repeatedly until the rep hears, in their own recorded voice, that a respectful question doesn't sound aggressive — this is usually a confidence gap, not a skill gap.

Does this coaching change with more AI-assisted buyer research expected by 2027? The core skill stays the same, but urgency signals shift — a prospect who has already used self-serve tools to research your category and still asks for basic information is showing lower intent than in past years, so the qualifying question becomes even more important to run every time.

Sources

• https://www.gong.io/blog/
• https://blog.hubspot.com/sales
• https://www.salesforce.com/resources/articles/sales-objections/
• https://www.sandler.com/blog
• https://www.rainsalestraining.com/blog
• https://www.gartner.com/en/sales
• https://hbr.org/topic/sales

Related on PULSE

• How do you coach reps to handle "just send me some information"?
• How do you handle a prospect who says "just send me a proposal" before you've presented any value?
• How do you qualify whether a lead is ready to buy or just gathering information?
• How do you handle a prospect who says they need to "think it over" after your pitch?
• What is the first question you ask when a prospect says they have no timeline?