60-Min Sales Training: "Send Me More Info" Objection

What the objection actually is and why an hour of training moves the number

Most sales floors treat "send me more info" as a small logistics request. A prospect asks for a PDF, the rep says "absolutely," the deck goes out, and the opportunity quietly dies in a follow-up sequence nobody reads. The training you run on Monday morning exists to break that reflex, because the request is almost never about information. It is a socially acceptable way to end a conversation without saying no to a human being who has been pleasant for the last four minutes.

That distinction matters operationally, not just philosophically. If the request is a genuine information gap, the correct response is to send the specific asset that closes the gap. If the request is an exit, sending anything at all is the worst available move: it converts a live conversation into a one-way channel where the prospect owes you nothing and your only follow-up lever is "did you get a chance to look at that?" Reps cannot tell the two apart from the sentence alone. The words are identical. The only way to separate them is to ask, in the ten or fifteen seconds you still have the person's attention.

An hour is the right container for this because the skill is narrow. You are not teaching discovery, or negotiation, or multithreading a complex enterprise deal. You are teaching one branch point and the language that navigates it. Narrow skills respond well to short, high-repetition sessions — the same reason a golf lesson on one swing fault beats a general "get better at golf" seminar. Sixty minutes gives you roughly five minutes of setup, fifteen of teaching, fifteen of scripting, fifteen of live role-play, five on failure modes, and five to assign accountability. Every minute is either instruction or repetition. There is no slide deck to sit through.

The frame you open with sets the tone for the rest of the hour. Do not say "today we're learning to overcome the send-me-info objection." Overcoming implies combat, and reps who go into combat mode start arguing with prospects about why a call is better than an email — a debate they cannot win because it is about the rep's convenience. Say instead: "We're not fighting this objection. We're decoding it." Decoding positions the rep as diagnostician. Diagnosticians ask questions. Fighters make assertions. The whole framework you are about to teach runs on questions, so the frame has to match.

There is also a manager-side reason to run this specific hour. "Send me info" is one of the few objections that produces a clean, countable CRM disposition. Unlike vague stalls — "let me think about it," "circle back next quarter" — an info request usually gets logged, because the rep does something afterward: they send an email. That means you have a denominator sitting in Salesforce or HubSpot right now. You can measure the before, run the training, and measure the after, without instrumenting anything new. Very few sales training topics come with a built-in measurement surface. Use the one that does.

Broaden the lens for a second, because the same decode logic transfers well beyond this one phrase. "Send me a proposal," "let me share this with my team," "can you put that in writing," and "email me your pricing" are structurally the same event: a request to convert a live, high-bandwidth conversation into a low-bandwidth artifact the prospect controls. Reps who learn the decode on "send me info" tend to apply it to the whole family within a couple of weeks, which is why the training's ROI usually exceeds what the single-phrase metric shows. Customer success teams facing "just send me the release notes" and partnership managers facing "send over a one-pager" run the identical play.

The step-by-step process for the hour

Run the hour on a fixed clock and put the agenda on the whiteboard before anyone sits down. Reps behave differently when they can see that role-play is coming; they pay closer attention during the teach because they know they will have to perform it in twenty minutes.

Minutes 0–5, setup. Open with a question, not a statement: "How many of your last ten 'send me info' prospects booked a second meeting?" Let the silence sit. Then pick one rep and ask for the specific story — the name of the company, what they sent, how long ago, whether the prospect ever replied. Specificity is what makes the cost feel real. A generic "we all know follow-up emails don't work" produces nodding; "you sent Kayla at Meridian a 14-slide deck nine days ago and she hasn't opened it" produces attention.

Minutes 5–20, the framework teach. This is where you introduce the three-question decode. Question one buys permission. Question two forces the prospect to name what they actually want. Question three trades the artifact for a calendar hold. Teach each one with the reasoning attached, because reps who understand why a line works will improvise around it correctly when the conversation goes sideways; reps who memorize without reasoning collapse the moment the prospect says something off-script.

Question one is a permission ask: "Happy to — before I send you something generic, can I ask you two quick questions so I send the right thing?" Note what this does. It agrees. It does not fight. And it frames the questions as being in service of the prospect's inbox, not the rep's quota. "Two quick questions" is a bounded promise, which is why it gets a yes far more often than an unbounded "can I ask you a few things." Keep the number honest — if you say two, ask two.

Question two forces articulation: "When you say more info — are you trying to work out whether this fits your stack, how it would integrate, or what it costs?" Three concrete options. Multiple choice is easier to answer than an open question, and whichever one the prospect picks is your real objection, surfaced in about six seconds. If they pick pricing, you have a budget conversation. If they pick integration, you have a technical stakeholder to find. If they say "honestly, none of those, I'm just not looking right now," you have received a clean no, which is worth more than a deck nobody opens.

Question three is the calendar pivot: "Got it. I could write that up, but it'd take me forty minutes and you'd skim it in ninety seconds. Can I walk you through it Wednesday at ten or Thursday at two? Eighteen minutes, screen share, you'll have a real answer." Three details do the work here — two specific times instead of "when are you free," an oddly precise time-box that signals you have actually thought about the length, and a screen share that promises a demonstration rather than a monologue.

Minutes 20–35, verbatim scripts. Print them. Read each aloud, then have the room read it back together. This feels awkward for about ninety seconds and then stops feeling awkward, and the awkwardness is the point — reps need these sentences to leave their mouths without hesitation, and hesitation is what happens when a line has only ever been read silently.

Minutes 35–50, role-plays. Three rounds of five minutes: a phone cold call, a Zoom discovery stall, and a written cold-email reply. Pair a senior rep as the prospect with a newer rep as the seller. Senior reps need to feel how slippery the brush-off is from the other side; newer reps need the volume. Rotate an observer who scores against a rubric rather than offering vibes-based feedback.

Minutes 50–55, pitfalls. Name the four ways reps still cave, ask who did each one last week, and let hands go up.

Minutes 55–60, the drill and the metric. Assign a countable weekly target, name the CRM fields, and set the Friday standup.

Time, cost, and the ranges managers should plan around

The direct cost of this training is one hour of floor time multiplied by headcount, plus about thirty minutes of manager prep. For a ten-rep team, that is ten selling hours and a half hour of prep — genuinely cheap compared to almost any external program. The expensive part is not the session; it is the reinforcement week that follows, and managers who skip it get most of the cost with none of the benefit.

Budget the manager's prep as three tasks. First, pull the last thirty days of info-request dispositions from the CRM to establish a baseline — you need the denominator before Monday, or you will spend the following Friday arguing about whether anything improved. Second, print the scripts, on paper, one per rep. Screens invite multitasking. Third, pick the two role-play personas in advance so the senior reps are not inventing a prospect on the fly and accidentally playing an easy one.

On timelines: expect the behavior to show up in call recordings within two or three days, and in booked meetings within one to two weeks. The gap exists because the defuse only fires when a prospect actually says the phrase, and depending on activity volume a rep might only hear it three to eight times a week. That is a small sample. Do not evaluate an individual rep on one week of data; evaluate the floor on two to three weeks, and use recordings rather than outcomes to coach individuals in the meantime. Process evidence is available immediately; outcome evidence is not.

On expected lift, be careful about promising a specific percentage. What is reliably true is directional: a booked call converts far better than a sent asset, because a call is a two-way channel with a scheduled time and an artifact is a one-way channel with no commitment. Any conversion of an info request into a calendar hold is a strict upgrade. Rather than borrowing a benchmark from a vendor's blog, set the target relative to your own baseline — "double last month's info-sent-to-second-meeting rate" is a target the team can verify and cannot dispute.

There are real costs on the other side of the ledger worth naming out loud to the room. Some prospects will find the third question pushy, and a small number of soft opportunities will convert into explicit nos faster than they otherwise would. That is a feature, not a bug, but only if your pipeline hygiene rewards it. If your comp plan or your forecast culture punishes reps for shrinking their open-opportunity count, they will quietly stop running the defuse within two weeks, because the incentive is pointing the other way. Check that before you run the training. A rep who is measured on pipeline volume will always prefer a live-looking dead deal to a clean loss.

Tooling costs are effectively zero if you already run a conversation-intelligence tool such as Gong, Chorus, or Clari Copilot — you need recordings for the Friday standup, and any of them will do. If you have no call recording at all, the training still works, but your coaching loop degrades to self-reported anecdotes. In that case, substitute live listening: the manager sits with each rep for twenty minutes once during the week. It is more expensive in manager hours and worth it for the first cycle.

One adjacent cost to plan for: your marketing and enablement teams may need to build the assets the defuse actually calls for. The framework promises a specific artifact tied to a specific picked option — an integration brief, a security summary, a pricing explainer for one segment. If all your team has is a single 22-slide overview deck, reps will default back to sending it. Ask enablement for three short, targeted one-pagers before the training rather than after, and give each a plain filename a rep can find under time pressure.

Where teams get this wrong

The reflex yes. The most common failure has nothing to do with the script. The rep hears "send me info," says "sure, what's your email," and the moment is gone before any framework could have fired. The fix is mechanical: train a three-second pause before responding to any info request. Three seconds feels enormous to the rep and is barely noticeable to the prospect. Drill it explicitly in role-play by having the observer count the pause out loud during round one.

The calendar cave. The rep does offer a call, then ruins it with "let me know what works for you." That sentence hands the scheduling work back to the person who was just trying to end the conversation, and it will not get done. Always two specific times. If both are wrong, the prospect will propose a third — which is the outcome you wanted anyway.

The PDF promise. The rep books the meeting and then, out of politeness, adds "and I'll send the deck over in the meantime." Now the prospect has the artifact and no reason to keep the call. The rule is that the agenda email is the info: one paragraph, three bullets on what you will cover, no attachment until after the conversation. Reps resist this because withholding feels rude. Reframe it for them — you are not withholding, you are sequencing.

Over-qualifying. A rep who has just learned a question framework will ask five questions instead of two. The prospect feels interrogated, the tone flips from helpful to extractive, and the call ends worse than if the rep had simply sent the PDF. Two questions in the defuse. Everything else belongs on the booked call. This is the failure mode that shows up most in weeks two and three, once reps get confident.

Running the training without changing the CRM. If you do not add the fields, the Friday standup becomes a storytelling session. Two fields are enough: whether the defuse was used, and what the outcome was — booked, asset sent, or lost. Anything more elaborate will not get filled in.

Treating the script as the skill. The verbatim lines are scaffolding, not the deliverable. A rep reciting question two in a flat voice while ignoring the answer has technically complied and learned nothing. The skill is listening to which option the prospect picks and adapting the rest of the conversation to it. Score the role-plays on whether the rep used what they heard, not on word-for-word recall.

Manager exemption. If the sales manager runs the training and then never demonstrates the defuse on a live call, adoption decays fast. Go first at the Friday standup with your own miss recording. The willingness to play a clip where you caved does more for adoption than any amount of rubric enforcement.

Choosing your response: when to defuse, when to send, when to walk

Not every info request deserves the same treatment, and a team that runs the calendar pivot on all of them will look robotic. Teach the branch logic alongside the script.

Defuse and pivot when the conversation is live and the prospect has shown any engagement — asked a question, described a current process, reacted to something you said. You have earned the ten seconds. This is the default and should cover the clear majority of cases.

Send the specific asset without a pivot when the prospect names a real, bounded artifact and a real reason: a security questionnaire before a vendor review, a SOC 2 summary for a procurement gate, an integration doc for an engineer who is genuinely evaluating. These are not brush-offs. Fighting them makes you look like you were not listening, and the request itself is a qualification signal — someone building an internal case needs paper. Send it fast, send it precise, and attach a single next-step ask.

Send a short written summary with a next-step ask when the prospect is under time pressure — walking into a meeting, a hard stop, a bad connection. Three lines, no attachment, one specific question at the end. You are preserving the thread, not closing it.

Disqualify when question two returns "none of those." That is a gift. Log it, close the record, and reinvest the follow-up hours somewhere with a pulse. The reps who resist this are usually the ones whose pipeline count is being watched more closely than their conversion rate.

Escalate to a multithread play when the prospect says a version of "send me something I can share internally." That phrase is a different animal from a solo brush-off — it names an audience. The right move is to find out who the audience is and what question they need answered, then build for that person specifically and ask for the call with them on it. This is the highest-value branch and the one reps most often waste, because sending a shareable deck feels like progress while it is actually a handoff to someone who cannot ask you follow-up questions.

Making it stick after the hour ends

The training is the cheap part. The week after is where the behavior either sets or evaporates, so put the reinforcement on the calendar before anyone leaves the room.

Assign a countable weekly target — every rep converts at least three info requests into calendar holds, across any channel. Phone, video, or email reply, it does not matter which. Volume matters more than channel purity in week one because you are building reps, not optimizing them.

Structure the week so there is a touch every day. Tuesday, each rep runs three live defuses and flags the recordings. Wednesday, a ten-minute standup where pairs listen to one recording each and name one thing that worked. Thursday, a written drill: five email replies using the written script, reviewed by a peer before sending. Friday at the end of the day, a fifteen-minute standup where every rep brings one win clip, one miss clip, and their own conversion number.

The miss clip is the part people skip and the part that matters. Make it voluntary in name and go first yourself as the manager, with a genuinely bad one. A floor that can watch its own manager get brushed off and laugh about it will surface problems early. A floor where only wins get played will hide the pitfalls until the quarter is over.

For the following Monday, bring one number: last month's baseline against week one's result. Do not dress it up. If it moved, name the two reps whose behavior moved it and have them describe exactly what they said. If it did not move, check the recordings before you check the reps — nine times out of ten the defuse simply is not being attempted, and that is a reinforcement problem rather than a skill problem.

Finally, extend the play deliberately in week three. Once the core objection is handled reliably, run a twenty-minute version of the same session on "send me a proposal" and another on "let me talk to my team." The decode structure is identical — permission, specificity, pivot — so the second and third sessions cost a fraction of the first and compound the return on the original hour of sales training.

Related questions

How do I run this if my team is fully remote?

Same clock, same content. Use breakout rooms for the role-plays with three people each — seller, prospect, observer — and have observers post rubric scores in the main chat. Record the breakouts if your tool allows, since remote sessions lose the hallway coaching that happens naturally on a floor.

What if a rep refuses to stop sending decks?

Check the incentive before the attitude. Reps who are measured on open-pipeline count are rewarded for keeping soft deals alive. Look at what their dashboard tracks. If the comp plan or forecast review punishes clean losses, the behavior is rational and the fix is managerial, not motivational.

Should SDRs and AEs be trained together?

Yes for the framework, separately for the scripts. SDRs hit the objection on cold calls with no context; AEs hit it mid-cycle with a relationship. Run the teach jointly, then split for role-plays so each group drills its own scenario at realistic difficulty.

How do I measure this without a conversation-intelligence tool?

Use two CRM fields — defuse used, and outcome — plus twenty minutes of live listening per rep per week. It is manager-hour expensive and directionally accurate. Add call recording when budget allows, but do not wait for tooling to start the training.

Does this apply outside net-new sales?

Yes. Customer success hears "send me the release notes," partnerships hears "send a one-pager," and recruiters hear "email me the job description." All three are the same request to swap a conversation for an artifact, and the same three questions work with light rewording.

FAQ

What is the three-question defuse in plain terms?

It is a short sequence a rep runs the moment a prospect asks for information. The first question asks permission to ask two things. The second offers three concrete options so the prospect names what they actually want. The third trades the document for a short, specific meeting time. The whole thing takes under twenty seconds when practiced.

Won't this sound scripted or pushy to prospects?

It sounds scripted when it is under-practiced, which is exactly why the hour includes fifteen minutes of live role-play. Reps adapt the phrasing to their own voice and industry during that block. The tone stays helpful because every question is framed around not wasting the prospect's inbox, and the rep agrees to the request before asking anything.

How quickly should a manager expect to see results?

Behavior change shows up in recordings within two or three days. Booked-meeting changes take one to two weeks because reps only encounter the objection a handful of times per week, and that sample is too small to judge individuals on quickly. Evaluate the floor over two to three weeks and coach individuals from recordings in the meantime.

What if the prospect genuinely wants information?

Then send it, quickly and specifically. If someone names a real artifact — a security summary, an integration doc, a procurement form — that is a qualification signal, not a brush-off. The second question separates the two cases in about six seconds, which is the entire point of asking it rather than guessing.

Is there a follow-up path for prospects who decline the call?

Yes. Send only the asset matching the option they picked, not a general deck, and pair it with one specific next-step question. Keep the sequence short and close the loop honestly rather than running eight touches into silence. If they never engage, log it as an asset-sent outcome and move on.

Do I need to buy anything to run this training?

No. You need a whiteboard, printed scripts, a room, and an hour. Call recording makes the Friday coaching loop much better, and two custom CRM fields make the metric real, but neither is a purchase if you already run a CRM and a conversation-intelligence tool.

Sources

• Josh Braun, "How to Defuse 'Send Me an Email'" — https://joshbraun.com
• 30 Minutes to President's Club, cold call objection episodes — https://www.30mpc.com
• Gong Labs research on sales conversation patterns — https://www.gong.io/resources/
• Close.com blog, handling "send me more information by email" — https://www.close.com/blog
• The Bridge Group SaaS AE and SDR benchmark research — https://blog.bridgegroupinc.com
• Chris Voss, *Never Split the Difference*, HarperBusiness, 2016 — https://www.blackswanltd.com
• HubSpot Sales Blog, objection handling guides — https://blog.hubspot.com/sales
• Sales Hacker articles on objection handling and discovery — https://www.saleshacker.com
• Salesforce Sales Cloud documentation on custom fields and reporting — https://help.salesforce.com
• RAIN Group research on sales conversations and buyer preferences — https://www.rainsalestraining.com/blog

Related on PULSE

• [The "Just Send Me a Proposal" Trap — 60-Min Training](/knowledge/st0067)
• [Objection Handling Bootcamp: Template for a One-Hour Team Sales Session](/knowledge/st0777)
• [Top 10 sales role-play templates for objection handling practice](/knowledge/st0753)
• [Top 10 objection handling role-play scenarios for sales teams](/knowledge/st0538)
• [Top 10 objection handling training drills for B2B sales reps](/knowledge/st0537)
• [60-Min Sales Training: "We Have No Budget" Objection](/knowledge/st0460)