How do you coach reps to handle 'just send me some information'?

Two coaching philosophies: script installation versus judgment building

Most sales managers reach for one of two approaches when a rep keeps folding on "just send me some information," and the two produce very different reps. Understanding the trade-off is the whole game, because picking the wrong one for the wrong rep wastes a quarter.

Approach one: script installation. You hand the rep three or four verbatim responses, drill them until the words come out clean, and audit call recordings for whether the language showed up. The bet is that behavior change follows language change — get the right words in the rep's mouth enough times and the underlying instinct catches up. This is how most enablement programs are built, and there is a good reason for it: it is fast, it is measurable, and it works on the population of reps whose only real problem is that nobody ever taught them there was an alternative to saying "sure, what's your email?"

The strengths are real. A new SDR who has been in seat for three weeks does not have the buyer context to improvise a diagnostic question, and asking them to "read the situation" is a cruel instruction. Give them the line. A script also creates a shared vocabulary across the team, so when you review a call you and the rep are talking about the same three moves rather than vibes. And it produces fast wins — a rep who has never acknowledged-and-redirected in their life will save a call in week one and feel the difference, which builds the motivation to keep going.

The weakness is brittleness. Scripts fail the moment the buyer goes off-script, which they do constantly. The rep says "happy to send something — what made you look into this now?" and the buyer says "I didn't, my boss told me to." Now what? A rep who memorized language without understanding the purpose behind it has no second move. They default back to "okay, I'll send the deck." You have taught them a phrase, not a capability. The other failure mode is tonal: a memorized line delivered with the cadence of a memorized line reads as manipulative to buyers, which is worse than folding politely.

Approach two: judgment building. Instead of leading with language, you spend the coaching time on diagnosis. Can the rep tell the difference between a buyer who is genuinely interested but slammed, a buyer who is politely exiting, and a buyer who is stalling because someone else in the org owns the decision? You drill classification before you drill response. The bet here is that a rep who reads the situation correctly will find serviceable words on their own, and will keep finding them when conditions change.

The strengths compound. A judgment-trained rep handles the "my boss told me to look" curveball because they recognize it as a signal about the buying committee rather than a failure of their script. They also transfer the skill sideways — the same diagnostic instinct that handles "send me info" handles "we're happy with our current vendor" and "circle back next quarter." You are building one muscle that services a dozen objections. And crucially, judgment-trained reps sound like humans, because they are actually responding to what the buyer said rather than executing a branch.

The weakness is time and floor. Judgment coaching is slow. It takes a full cycle, sometimes two, before you see it in the numbers, and during that time your leading indicators look flat while a script-installed team's numbers move in three weeks. It also has a higher floor of required rep capability — a rep who does not understand the buyer's world well enough to know what question to ask cannot be judgment-coached into it. You have to fix the knowledge gap first.

The synthesis most good managers land on: script first as scaffolding, judgment second as the real curriculum. The script buys the rep a safe harbor so they stop panicking in the moment; the judgment work is what you spend the following sixty days on. The mistake is stopping at step one and calling it coaching, which is what happens at the large majority of orgs that "rolled out objection handling" and saw nothing change.

There is a third path worth naming even though it is rarely the right answer alone: system correction. Sometimes the rep does not need coaching at all. If a rep executes a clean acknowledge-redirect and still gets brushed off on eight of ten calls, you do not have a rep problem, you have a targeting problem, and no amount of role-play fixes a bad list. This is where RevOps earns its keep — pulling the data that separates "this rep folds" from "these conversations were never live," and routing the fix to the right owner. Coaching a rep out of a list problem is one of the most demoralizing things a manager can do, and it happens constantly.

Choosing the right approach for the rep in front of you

The decision is not philosophical, it is diagnostic. You route based on what is actually broken, and there are four distinct root causes that all present with the identical symptom of a rep emailing a PDF and getting ghosted.

Skill gap. The rep does not know the move exists. They hear a request, they comply, they log the call as productive. This is the cheapest gap to close and the one where script installation genuinely shines. Signal: when you ask "what else could you have said?" they draw a blank, not a hesitation. Fix: install the language, drill it five times, watch it show up next week.

Will gap. The rep knows the move and will not run it. Redirecting feels pushy, and they would rather protect the relationship than push for a next step. Signal: they handle it fine on warm inbound where the buyer is already leaning in, and fold on cold outbound where they feel like an intruder. Fix: this is confidence work, not language work. More role-play reps, deliberately uncomfortable ones, plus reframing — the redirect is a service to the buyer, because sending a generic overview to someone who needed pricing wastes everyone's week.

Knowledge gap. The rep cannot ask a sharp diagnostic question because they do not understand the buyer's world well enough to know what is worth asking. They retreat to "let me send something over" to buy time and end the discomfort. Signal: their diagnostic questions, when they attempt them, are generic — "what are you hoping to solve?" rather than "are you looking at this because renewal is coming up or because something broke?" Fix: persona depth, customer call shadowing, and time with the CS team. No script fixes this.

System gap. The conversations are low quality. Bad targeting, no trigger event, no reason for this buyer to engage with this pitch this week. Signal: every rep on the team, including your best one, hits the same wall on the same segment. Fix: escalate to RevOps and marketing, not to the rep.

The routing matters because the wrong intervention actively backfires. Giving a will-gap rep more scripts tells them the problem is their words when they know it is their nerve, and they read it as you not listening. Giving a knowledge-gap rep confidence coaching produces a confidently wrong rep. And running any of the three on a system problem teaches the whole team that coaching is theater.

Run the symptom through this before you spend a 1:1 on it:

One caution on the tree: diagnose from recordings, not from the rep's self-report. Reps consistently remember their responses as sharper than they were. Pull the actual call, find the moment, and listen to what came out of their mouth in the four seconds after the buyer said the line. That four-second window is where the whole skill lives, and it is the only evidence that matters.

The numbers that separate the two approaches

Coaching arguments get resolved by measurement, and the measurement most teams reach for — quota attainment — is the wrong one. Quota is a lagging composite of pipeline built two quarters ago, territory quality, product-market fit, and a dozen things the rep does not control. It will not tell you whether your objection coaching worked, and by the time it moves, you have lost a cycle you could have used to correct.

Track leading indicators instead, and track them per rep, not just in aggregate.

The primary scoreboard: "send me info" to next-step conversion rate. Of the calls where the rep heard the line, what percentage ended with a booked meeting or an explicitly agreed next step with a date attached? This is the direct measurement of the skill you are coaching. Tag these moments in your CRM or pull them from your conversation intelligence platform so the denominator is honest — the failure mode here is only counting the saves, which makes every rep look great. You need every instance of the trigger, including the ones the rep would rather forget.

Set the baseline before you coach. Pull four to six weeks of recordings, count the instances, count the saves, and write the number down. Without a pre-number you cannot distinguish coaching from seasonality, and you will end up claiming credit for a good quarter.

The behavioral leading indicator: diagnostic-question rate. Of the "send me info" moments, what percentage included at least one redirect question before the rep agreed to anything? This one is different from the conversion rate in an important way — it measures what the rep controls. A rep can run the move perfectly and still get told no, and you do not want to punish that. Diagnostic-question rate should trend toward near-total coverage; the conversion rate will always be a fraction of it, because plenty of buyers genuinely are not in market.

This distinction matters for a will-gap rep specifically. If you only measure conversion, a rep who tries the move and gets rejected twice concludes the move does not work and stops. If you measure the attempt, you can tell them honestly: you ran it right, the buyer wasn't live, keep running it.

The quality check: meeting-to-opportunity rate for saved conversations. This exists to catch the failure mode where a rep gets so good at converting the objection into a calendar hold that they start booking junk to make the first number look good. Compare the downstream conversion of "saved" meetings against the team's baseline meeting-to-opp rate. If saved meetings convert dramatically worse, the rep is bullying calendar time out of people who were correctly trying to exit, and you have coached the wrong behavior.

The hygiene metric: follow-up completion. When information does get sent — and sometimes it should — was it sent with a specific scheduled touch attached, or into a void? A rep who sends a tailored one-pager and books a fifteen-minute reaction call is doing the job. A rep who sends a generic deck and sets a task to "follow up next week" is not.

The trend line: scorecard average over time. Score the moment on four dimensions — did they acknowledge, did they diagnose, did they propose a specific step, was the tone natural — on a simple one-to-five each. Plot the rep's average by week. What you are looking for is a slope, not an absolute. A rep moving from low to middling in six weeks is a coaching success; a rep flat at middling for six weeks is telling you the intervention is wrong for their gap.

On timing expectations. Script installation shows up in the diagnostic-question rate within two to three weeks, because the rep is doing a thing they were not doing before and it is easy to observe. Conversion rate lags that by another few weeks, because you need enough at-bats to have a stable denominator. Judgment work shows up later still and shows up differently — the tell is not the primary metric but the sideways transfer, where the rep starts handling adjacent objections better without you coaching those. Watch for that. It is the single best evidence that you built capability instead of installing a phrase.

A note on sample size. Do not draw conclusions from a rep's five calls. Objection-handling rates are noisy at low volume, and a manager who reacts to a bad week burns credibility. Wait for a meaningful number of triggering moments before you re-diagnose — for most AEs carrying full cycles, that is a month; for high-volume SDRs, it can be a week.

Running the plan: sequencing, drills, and the words themselves

Here is the actual implementation, sequenced. The mistake to avoid is trying to compress this into one intense conversation — coaching that lands is a loop, not an event.

Weeks one through four: install and drill.

Open with a 1:1 structured on the GROW model, because it forces the rep to arrive at the answer rather than receive it, and rep-owned conclusions survive contact with a live buyer in a way manager-issued ones do not.

*Goal.* Ask: "What do you actually want to happen when someone says just send me some information?" Most reps say "get a meeting" and then behave as though the goal is to comply politely. Name that gap out loud. The goal is a committed next step, not a delivered document.

*Reality.* Ask: "Walk me through the last time you heard it — what did you say back, word for word?" Then: "What do you think they really meant? Interested, busy, or trying to get off the phone?" Most reps realize mid-sentence that they never found out. That realization is the coaching; do not step on it.

*Options.* Co-build three responses before you offer yours. Then give them the model plays:

The *acknowledge-then-diagnose* play: "Happy to — I'd rather send you something useful than a generic overview, so let me tailor it. Quick question: what made you want to look into this right now?" The buyer either hands you a real reason, which is qualification, or admits there isn't one, which is also qualification.

The *trade-info-for-a-step* play: "I can absolutely send something over. Teams that get value out of it usually want me to walk through the part that's relevant to their setup — that's fifteen minutes. Want me to grab time so the info actually lands?"

The *name-it-gently* play, for an obvious exit: "Totally fair — sometimes send me info means this isn't a fit right now, and sometimes it means I'm interested but slammed. Which one is it? I won't be offended either way." Buyers frequently re-engage, because the honesty is disarming and rare.

The *specificity* play: "What's most useful — a one-pager on pricing, a customer story in your industry, or the integration details? I don't want to send the wrong thing." This converts a vague ask into a qualifying conversation and manufactures a legitimate reason to follow up.

*Will.* Close with: "Which of these will you use on your next three calls, and how will I know you did?" A counted commitment with a check-in date survives. Vague intent does not.

Then drill, twice a week, five minutes each:

The sixty-second redirect drill. You play the buyer, deliver the line, and the rep must acknowledge, diagnose, and propose a step inside a minute. Run it five times back to back with different buyer moods — rushed, skeptical, warmly evasive, actively annoyed. The mood variation is the point; a rep who has only practiced against a friendly buyer folds against a curt one.

The real-or-exit sort. Give the rep ten transcribed "send me info" moments and have them classify each as genuine interest or polite exit, with justification. This is the judgment drill, and it is the one managers skip. Score their classification against your own read and argue the disagreements — the arguments are where the learning happens.

Objection laddering. After the rep redirects, push back twice. "I really just want the PDF." They have to hold the line without tipping into pushy. This is where you find the will gap that role-play against a compliant fake buyer never surfaces.

Weeks five through eight: shift to live application.

Stop role-playing and start reviewing real calls. Have the rep flag one call each week where they ran the move and one where they didn't, and coach the contrast — self-selection here is deliberate, because the act of noticing "I folded on that one" is most of the skill. Pause the recording at the four-second window and ask what the buyer's tone told them before they answer what they said. If your conversation intelligence tooling can auto-surface the phrase, use it; it collapses the observation step from an hour to five minutes and is the single highest-leverage tooling investment for this specific coaching problem.

Weeks nine through twelve: back off and watch.

Reduce direct reps. Spot-check one recording weekly. Watch the leading indicators and specifically watch for sideways transfer into adjacent objections. If the rep is handling "we're all set for now" better without you having coached it, the judgment landed.

The weekly loop underneath all three phases:

Where managers get this wrong

Rescuing the rep. Jumping on the call to demonstrate feels generous and teaches dependence. Let them run it, let it go badly, debrief after. The discomfort is the curriculum.

Coaching the deal instead of the skill. Saving the one account where the rep folded is firefighting. It feels like management because a number moves. Coaching the rep so they stop folding is the actual job, and it does not show up this month.

Handing over a script with no drilling. Reps do not internalize language by reading it in a doc. Language becomes available under pressure only after it has been produced under pressure. If your objection-handling rollout was a slide deck and an email, nothing happened.

No follow-through date. A good coaching conversation with no scheduled check-in evaporates inside a week. Lock a counted commitment and a date, every time, in writing.

Coaching everyone identically. The team meeting where you present "the send-me-info play" serves the skill-gap reps and actively insults the will-gap ones. Group sessions install; individual sessions diagnose. You need both, and they are not substitutes.

Treating a system problem as a skill problem. Worth repeating because it is the most expensive error on this list. When the whole team stalls on the same segment, the coaching conversation is the wrong room. Route it to the people who own targeting.

Over-indexing on the save. Not every "send me some information" should be converted. Some buyers are genuinely not in market, and a rep who has been coached to never accept it will grind calendar time out of people who will no-show. Coach reps that "this isn't live, disposition it honestly" is a correct outcome, and make sure your metrics reward it rather than punishing it.

Adjacent surfaces where the same coaching pays off

The reason to invest in this specific objection is that it is the cheapest entry point into a much larger capability, and the transfer is measurable.

Other soft objections. "Circle back next quarter," "we're all set for now," "let me run it by the team," and "just send me a proposal" are structurally identical — each feels like a non-rejection, each lets the rep exit feeling productive, and each is a request for information in place of a decision. The same three beats work: acknowledge, ask one question that surfaces the real state, propose a step scaled to what you learned. A rep who genuinely internalizes the pattern here needs a fraction of the coaching on the rest.

Buying-committee mapping. "Send me some information" is very often a proxy signal that your contact is not the decision-maker and is planning to forward the document to someone who is. That reframe changes the redirect entirely — instead of pushing for a meeting with your contact, you ask "who else will be reading this? I'd rather build it for them." Now you have turned a stall into a committee map. Coaching reps to hear the multi-threading signal inside the objection is a meaningful upgrade over coaching them to defeat it.

Marketing and content feedback. When reps run the specificity play — asking what format is most useful — you get a running dataset on which assets buyers actually want at which stage. That is genuinely valuable to whoever owns content, and most teams never capture it. Have reps log the answer. Over a quarter it tells you what to build.

Inbound and customer success handoffs. The same objection shows up in renewal and expansion conversations wearing different clothes: "send me the details and I'll look at it before renewal." CS teams are typically coached even less on this than sales teams, and the acknowledge-redirect transfers cleanly. If your CS org handles renewals, share the plays sideways.

Forecast hygiene. This is the RevOps payoff. A rep who reflexively sends information and logs the call as progress is contributing fictional pipeline. Deals stalled at "sent them the deck" clog the forecast and make coverage ratios lie. Coaching the redirect improves not just conversion but data quality — the deals that survive are the ones with a real next step attached, and the ones that die, die faster and earlier, which is what you want. When you make the case for spending a quarter on this, that forecast-cleanliness argument tends to land with leadership better than the conversion-rate one.

Related questions

Is "just send me some information" always a brush-off?

No. Sometimes the buyer is genuinely interested and genuinely slammed, and a tailored asset plus a scheduled walkthrough is exactly the right answer. The skill you are coaching is diagnosis — one question that reveals which it is before the rep decides how to respond.

What if the rep redirects and the buyer still insists on just the document?

Honor it gracefully but attach a next step: send the most specific asset possible and book a short reaction call. If the buyer refuses any next step at all, that is qualifying data. Coach the rep to disposition it honestly rather than keep it in forecast.

How is this different from coaching a hard objection?

Hard objections create friction that alerts the rep something went wrong. This one feels like a yes, so the rep never registers it as an objection. Half the coaching is building awareness that a moment even occurred — which is why the classification drill matters as much as the language.

Should new SDRs get the script or the judgment work first?

Script first, without hesitation. A rep three weeks in seat lacks the buyer context to improvise a useful diagnostic question, and asking them to read the room is unfair. Install the language, get them a win, then start the judgment curriculum in month two.

How do you coach this on a distributed team?

Conversation intelligence tooling does the heavy lifting by surfacing the exact moments, so you review clips instead of whole calls. Run role-play over video and record it — self-review of one's own recorded role-play is unusually effective, because the gap between remembered and actual is visible.

FAQ

How long before I should expect to see results?

Diagnostic-question rate moves within two to three weeks if the gap was skill — the rep is performing a new observable behavior and it either shows up or it doesn't. Conversion rate needs enough triggering moments for a stable denominator, so give it four to six weeks for a full-cycle AE. Judgment-level change takes a full quarter and shows up as sideways transfer into other objections rather than as a spike in one metric. If nothing has moved on the behavioral indicator after a month, you targeted the wrong gap — go back to the diagnostic tree rather than doubling the dose.

Should I coach this in a team meeting or one-on-one?

Both, for different purposes. Team settings are efficient for installing shared language and running group drills, and the peer visibility creates useful pressure. But diagnosis has to be individual, because the four root causes require four different interventions and a group session inevitably delivers the skill-gap fix to everyone. The pattern that works: install in the group, diagnose and drill in the 1:1.

What if a rep pushes back and says the redirect feels manipulative?

Take it seriously rather than dismissing it, because a rep who feels manipulative will sound manipulative. Reframe around the buyer's interest: sending a generic overview to someone who actually needed integration detail wastes their week, and asking one question before sending is a service. If they still resist after the reframe, you have surfaced a will gap worth working on directly. Also check your own plays — if the script really is pushy, the rep is right.

How do I get honest data on how often this is happening?

Do not rely on self-reporting; reps under-report the moments where they folded, not out of dishonesty but because a call where you agreed to send something does not encode in memory as a loss. Pull it from call recordings by searching the phrase and its variants, or require a CRM disposition on the call. The denominator is the part people get wrong — you need every instance of the trigger, not only the ones the rep flagged.

Does this coaching apply to inbound leads too?

Yes, though the diagnosis shifts. On inbound, "send me some information" is far more likely to be genuine, because the buyer initiated. The specificity play tends to work best there — asking which format is useful qualifies without any friction at all. On cold outbound, treat the same words with more suspicion and lean toward the name-it-gently play, which gives the buyer a graceful exit and surfaces the truth faster.

When is more coaching the wrong answer entirely?

Two cases. First, when the rep executes well and still gets brushed off constantly — that is a targeting, trigger, or ICP problem, and it belongs with RevOps and marketing, not in another role-play. Second, when a rep has had a full cycle of clear coaching, drilling, and feedback and has not applied any of it. At that point you are no longer looking at a coaching problem; you are looking at a performance-management conversation, and continuing to coach is avoidance.

Sources

• Harvard Business Review — Sales and marketing topic hub
• Performance Consultants — The GROW coaching model
• Gong Labs — Sales conversation research
• RAIN Group — Sales coaching blog
• Sandler — Sales training and methodology blog
• Winning by Design — Revenue architecture resources
• Salesforce — Sales coaching resources
• MIT Sloan Management Review — Sales management research

Related on PULSE

• [How do you handle a prospect who says 'just send me a proposal' before you've presented any value?](/knowledge/cg0906)
• [How do you qualify whether a lead is ready to buy or just gathering information?](/knowledge/cg0943)
• [How do you coach a rep to handle 'let me talk to my boss'?](/knowledge/cg0079)
• [Can you walk me through the last time you successfully turned a 'no' into a 'yes'?](/knowledge/cg0935)
• [How do you coach a sales engineer to sell, not just demo?](/knowledge/cg0206)
• [Can you walk me through the exact steps you take to map out a decision-maker's influence map in a large enterprise?](/knowledge/cg0910)