When to ask for the meeting
Reps lose meetings in two opposite ways. Some ask too early, before the prospect has said anything that makes a meeting worth their time. More ask too late: they keep discovering until the prospect runs out of patience. The window in between is shorter than most people think.
Gong's analysis of cold calls (vendor research) found that successful cold calls ran about 5 minutes 50 seconds, nearly twice the length of unsuccessful ones. That is your whole budget: opener, reason for the call, a problem question or two, and the ask. Treat anything past six or seven minutes on a cold call as a sign you skipped the ask.
Buying signals that mean 'ask now'
- They describe the problem in their own words. 'Yeah, our reps spend half the day waiting on rings' is a yes to the problem.
- They ask a how question. 'How does that work with Salesforce?' means they are picturing using it.
- They mention timing. A renewal, a new hire, a quarter-end target or a recent change.
- They compare you to something. 'We looked at something like this last year' means the category is already on their radar.
- They stop trying to get off the phone. Longer answers and fewer 'I'm busy' signals.
Once you hear one of these, stop exploring. You are not trying to sell the product on the call; you are trying to sell the next 30 minutes. If you need a refresher on the first half of the call, start with cold call openers and how to cold call.
The ask: word-for-word scripts
A good ask has four parts: a one-line summary of what they told you, what the meeting will give them, a specific time, and who should be there. Here are four versions for different situations.
Rep:So if I heard you right, the team is making plenty of calls but only a handful turn into real conversations each day.
Prospect:Pretty much.
Rep:That's exactly what we dig into with teams your size. Worth 30 minutes with one of our specialists to see what that would look like for your reps? I have Tuesday at 10 or Wednesday at 2 your time.
Prospect:Wednesday works.
Rep:Great. I'm sending the invite now to the email ending in your company domain. Can you check it landed while I've got you?
Rep:I don't know yet if this is a fit, and you don't either. How about 20 minutes where we look at how your team runs call blocks today? If it's not useful, you'll know in the first five and we'll stop there.
Rep:It sounds like this sits with you and whoever owns the CRM setup. Would it make sense to have them on the call, so you don't have to relay everything afterwards? Who would that be?
Rep:We work with a few other outbound teams in your space, and the first conversation is usually where they figure out whether their connect problem is the list or the dialing. Want to do that for your team on Thursday morning?
Book it before you hang up
- Confirm the email address out loudRead it back. A wrong address is the quietest no-show there is.
- Send the invite while you are still talkingUse a short title the prospect will recognize next week, for example 'Acme x YourCo: fixing low connect rates'.
- Ask them to accept it now'Can you hit accept so it's locked on your side?' An accepted invite is far stronger than a verbal yes.
- Agree the agenda in one sentence'We'll look at your current call blocks and show you two options. Anything else you want covered?'
- Log it immediatelyOutcome, meeting time, the problem in their words and who else is invited. Your AE will read this note five minutes before the call.
Light qualification on a cold call: BANT and alternatives
BANT (budget, authority, need, timeline) is the best-known qualification checklist, and it is useful. The mistake is running all of it on a cold call. Asking a stranger about budget two minutes in sounds like an interrogation and hands them an easy exit. On the cold call, qualify just enough to know the meeting is worth an AE's time.
| BANT element | Ask on the cold call? | Cold call version | Save for discovery |
|---|---|---|---|
| Need | Yes, always | 'How are you handling X today?' and 'What's that costing you?' | Size of the problem in numbers, who else feels it |
| Authority | Lightly | 'Who else would weigh in on something like this?' | Full buying committee, sign-off process |
| Timeline | Lightly | 'Is this something you're looking at this quarter, or more of a later problem?' | Exact dates, dependencies, contract renewals |
| Budget | Usually no | Only if they raise price: 'Totally fair. The meeting will show you the options so you can judge.' | Budget range, who owns it, how purchases get approved |
| Framework | Stands for | Best for | Use on a cold call |
|---|---|---|---|
| BANT | Budget, authority, need, timeline | Simple, transactional sales | Need and timeline only |
| CHAMP | Challenges, authority, money, prioritization | Teams that want to lead with the problem | Challenges first, which suits cold calls well |
| MEDDIC / MEDDPICC | Metrics, economic buyer, decision criteria, decision process, (paper process), identify pain, champion, (competition) | Complex, multi-stakeholder enterprise deals | Too heavy; it belongs to the AE's discovery and beyond |
| GPCTBA/C&I | Goals, plans, challenges, timeline, budget, authority, consequences and implications | Consultative sales with longer cycles | Goals and challenges only |
A practical minimum bar for booking: one confirmed problem, the right person or a clear path to them, and openness to looking at it in the next few weeks. Write that bar down with your AE lead so you are not arguing about it meeting by meeting.
Handling 'just send me something' and other late-call stalls
'Send me something' at the end of a call is rarely a request for information. Usually it means 'I'd like this call to end politely'. Agree, then make one more attempt with a question that tests real interest. For a fuller library, see cold call objection handling.
Prospect:Just send me something and I'll take a look.
Rep:Happy to. So I send the right thing and not a generic deck: is the bigger issue getting reps into more conversations, or what happens once they're talking?
Prospect:Honestly, the first one.
Rep:Got it. I'll send a one-pager on that today. Most people find it easier to see it on their own numbers, though. Can I put 20 minutes on Thursday as a placeholder? If the one-pager doesn't land, just decline it.
Rep:Will do. Just so I call at the right moment: what changes next quarter?
Prospect:We're hiring three more SDRs in January.
Rep:That makes sense. Teams usually want the setup sorted before new reps start, not after. Would a short call in early December be more useful than one in January? I'll send an invite you can move if needed.
Rep:Thanks for saying so. Who looks after how the sales team's calling is set up?
Prospect:That would be Dana, our sales ops lead.
Rep:Thanks. Would you mind if I mention we spoke? I'll keep it short.
Rep:Thirty minutes, and you'll know in the first ten whether it's worth the rest. If it isn't, I'll be the first to say so.
If the second attempt fails, send what you promised within the hour, put a specific follow-up call in your sales cadence, and stop pushing. A polite exit today keeps the door open for the call-back, which Cognism's 2025 report (WHAM data) found books meetings at a significantly higher rate than the first cold call.
Confirming the meeting and reducing no-shows
A booked meeting that does not happen is worth nothing, and SDR quotas are usually set on meetings held. Bridge Group's 2025 survey found the median SDR quota is 10 held meetings a month, not 10 booked.
Be skeptical of no-show benchmarks. Most published ranges are vendor estimates without a sample or method. The strongest controlled evidence on reminders comes from healthcare: a Cochrane review of randomized trials found attendance of 67.8% with no reminder, 78.6% with a text reminder and 80.3% with a phone reminder. Sales meetings are not doctor's appointments, but the direction is clear: reminders work, and existence matters more than exact timing.
| When | Channel | What to send | Why |
|---|---|---|---|
| On the call | Calendar invite | Invite with a recognizable title, accepted live | Locks the slot on their calendar, not just yours |
| Within 5 minutes | Recap: their problem in their words, the agenda, who will join | Gives them a reason to attend and something to forward | |
| Day before | Email (or a short call) | One line of value: what they will walk away with | Reminds them why they said yes |
| 1 hour before | Email, or text where they have agreed to texts | Join link and your direct number | Removes friction at the last moment |
| At start time, if absent | Email and a call | 'We're on, here's the link again' | Recovers late joiners, starts the reschedule |
Subject: Wednesday 2pm: fixing low connect rates for the SDR team
Hi Jordan, thanks for the time just now. You mentioned the team makes plenty of calls but only a handful turn into real conversations, and that you are hiring three SDRs in January.
On Wednesday, Sam (our specialist) will walk through how your call blocks run today and two ways to change the math. 30 minutes, video link in the invite.
If the time stops working, just move the invite. See you then.
- Book close in. A meeting two or three working days out holds better than one two weeks out. No source we trust quantifies it for sales, but every dataset points the same way.
- Make the reschedule easy. A prospect who moves the meeting is still engaged. Track reschedules separately from no-shows.
- Recover no-shows the same day. 'No problem, things come up. Does Thursday at 11 or Friday at 2 work instead?' Then a final attempt two days later.
Handing the meeting to an AE
The handoff is where SDR work most often goes to waste. An AE who opens with 'So, tell me about your business' throws away everything the prospect already said. Agree a handoff note format with your AE team and fill it in before you log off.
| Field | Example |
|---|---|
| Problem in their words | 'Reps make 60 dials and get 3 real conversations.' |
| Why now | Hiring three SDRs in January; wants setup done first |
| Who will attend | Jordan (Head of SDR), Dana (Sales Ops) invited |
| Current tools | Salesforce, a single-line dialer, sequences in Outreach |
| What they want from the meeting | See how the team's call blocks could run differently |
| Watch-outs | Asked about price; burned by a long contract before |
| Call recording | Link to the recorded cold call |
- Introduce the AE by name on the call if you can: 'You'll be speaking with Sam, who runs these with teams like yours.'
- Send a short intro email copying the AE, so the prospect knows the face on the call.
- Close the loop. Ask the AE for a one-line verdict after the meeting: accepted, rejected and why. That feedback is how SDRs learn what a good meeting looks like.
Measuring how well you book
Three ratios tell you whether this part of the call is working. Track each one weekly, with the count behind it.
| Metric | Formula | Reference point |
|---|---|---|
| Set rate | Meetings booked / conversations | 4.6% average rep, 16.7% top quartile in Gong's 300M-call analysis (vendor data) |
| Show rate | Meetings held / meetings booked | No verified cross-market sales benchmark; track your own trend |
| Acceptance rate | Opportunities accepted / meetings held | Bridge Group 2025: median quota of 10 held meetings and 6 converted to Stage 1 per month (survey) |
If set rate is low, listen to calls that did not book and look for a missing ask. If show rate is low, look at days between booking and meeting, and at your confirmation emails. If acceptance is low, rewrite the qualification bar with your AE lead. The full funnel is in cold calling metrics.
Frequently asked questions
How do you ask for a meeting on a cold call?
Summarize the problem they described in one line, say what the meeting will give them, and offer two specific times: 'Worth 30 minutes to see what that looks like for your team? I have Tuesday at 10 or Wednesday at 2.' Then send the invite while you are still on the phone and ask them to accept it.
Should SDRs use BANT on cold calls?
Only partly. Confirm need and rough timing, and ask lightly about who else is involved. Leave budget and the buying process for the discovery meeting, where the AE has earned the right to ask. A full BANT checklist on a cold call tends to feel like an interrogation.
What are good discovery call questions to set up from a cold call?
Pass the AE the open threads: how the prospect handles the problem today, what it costs them, who else feels it, what changes if nothing changes, and what would need to be true to act this quarter. The SDR's job is to surface the problem, not to finish discovery.
How do I reduce no-shows for meetings booked on cold calls?
Book close in, send the invite live and get it accepted, email a recap within minutes, remind the day before and an hour before, and recover no-shows the same day. Controlled evidence on reminders comes from healthcare (a Cochrane review found attendance rose from 67.8% to 78.6% with text reminders), but the direction holds for sales meetings too.
What do I say when a prospect says 'just send me an email'?
Agree, then ask one question that makes the email specific ('Is the bigger issue X or Y?'). Use the answer to propose a short placeholder meeting they can decline. If they still say no, send exactly what you promised within the hour and schedule a follow-up call.
- 1.Gong, Evolve the cold call: 8 data-driven techniques (vendor research) (2021)
- 2.Gong, The hidden power of cold calling: Insights from 300M calls (vendor research) (2024)
- 3.Cognism, The State of Cold Calling in 2025 (WHAM call data, vendor research) (2025)
- 4.The Bridge Group, SDR Models, Motions & Metrics: 2025 Research Report (survey of 351 B2B companies) (2025)
- 5.Cochrane Library, Mobile phone messaging reminders for attendance at healthcare appointments (Gurol-Urganci et al.) (2013)
Spend your reps' day on conversations, not ringing phones.
TwinsAI parallel-dials up to 8 lines at once, validates every number with the carrier before it rings, and bridges a live prospect to your rep in under 450ms. It works inside HubSpot, Salesforce, Close, Attio, Outreach, Zoho and HighLevel, with no seat minimum.