SDR cold call script for meeting bookings

The SDR’s one metric

An SDR call has one good outcome: a meeting that holds. Everything else, rapport, education, brand-building, is a byproduct. This script is built around that fact. It spends the first ten seconds proving relevance with a trigger event, the next sixty testing ownership and timing, and the rest of the call protecting the calendar ask from the six brush-offs that kill it. No pitch, no demo language, no feature tour; the pitch is the AE’s job and the cold call that pitches dies in the objection stack.

In production use across 3-line sessions over 90 days, median volume ran about 85 dials per active hour and roughly 600 per operator day with person connects around 17.8 percent. The dialer produces the connects; the script decides whether any of them become meetings.

The structure

Trigger-event opener. One public fact, one symptom, one routing question: is that on your plate or someone else’s. The trigger must be real and verifiable, because the first fabrication ends the relationship and the account.

Ownership and symptom. The prospect’s answer to who owned the cleanup last time is the qualification spine. An owner with a scar listens for 60 more seconds; a bystander gets a referral ask or a nurture.

The meeting frame. Not a pitch, a working session, 25 minutes, with the solutions person, about what broke last time. Prospects accept working sessions; they dodge pitches.

The double-date close. Two named slots. If the prospect counters, take their time to the minute. If the prospect hesitates, the pricing objection response doubles as the second close.

The skip-this question. The prospect designs their own meeting, which raises show rate and gives the AI summary its most useful field.

Objection handling

“Just send me an email”

“I will, and it will be the agenda for Thursday 11 rather than a brochure, because agendas get opened. If the agenda reads irrelevant, reply no and I am gone.” Email as artifact of a meeting compounds; email as replacement for one rots.

“We already have a vendor”

“Expected, and I am not calling to displace anyone on a cold call. The trigger you are sitting on is the reason to have one 25 minute session: either your current setup covers it, which you will confirm and I will stop, or it does not, which is better learned before the expansion than after. Which slot?”

“No budget this cycle”

“Budget cycles are won in the quarter before them, by whoever helped write the requirements. The session costs nothing and feeds your planning doc. Do we hold a slot for the week planning starts, or should I ping you then?” Timing honesty turns no-budget into dated nurture instead of dead air.

“Who gave you my number?”

“No one, specifically: your company’s expansion was public, I work the segment, and I matched the role. That is the whole trick, and I would rather you know it than wonder.” Honest sourcing defuses the question and models the honesty the meeting will run on. Misrepresenting affiliation is exactly what the FTC’s Impersonation Rule at 16 CFR 461.3 prohibits.

“We are not buying anything this year”

“Then the meeting is cheap insurance: 25 minutes on what would need to be true for [company] to ever want this, which I will write down and leave with you whether or not anything happens. Requirements in writing age well.” Prospects who hear a no-pressure artifact sometimes book; prospects who hear pressure never do.

“Call my VP”

“Do you want to make that easy: forward the agenda I am about to send, or give me their name and I will approach them with your context, which lands better than a cold hit.” Multithreading offered politely converts a brush-off into a second thread. Log the VP’s name as a new lead with the context noted.

Gatekeeper line

One sentence, role-honest: “Hi, this is [name] with [company]. Who is running the [trigger area] for the expansion?” If pressed: “A working-session invite about what broke last time you grew; I think he will want 25 minutes.” Assistants respond to specificity and status-clarity. Get the name and title, thank them by name next attempt, and never try to trick your way past; the same assistant guards every future attempt.

Voicemail, 18 seconds

“[Name], [name] at [company] about the [trigger]. Had one specific question about how the last expansion went for your team. Thursday or Monday, [number].” Short, specific, tied to their calendar. Log it and rotate the next attempt’s daypart.

After the call

The AI summary should carry the trigger, ownership, timing, tooling-including-what-stays, the skip-this note, and the confirmed slot. The SDR edits wrong fields and sends the agenda invite from their own address within the hour. Dispositions match the trade: meeting booked, not now with a dated revisit, gatekeeper referral, wrong persona, bad number, no answer, left voicemail, do not call. No-shows get one recycle within five business days with the same agenda and zero guilt; two silent misses move the lead to dated nurture.

Compliance in one paragraph

Calls between a telemarketer and a business to induce a business purchase are mostly outside the FTC Telemarketing Sales Rule under the narrow exemption in 16 CFR 310.6(b)(7), but the exemption is narrow: it does not waive TCPA wireless rules at 47 CFR 64.1200, and B2B lists contain personal cells. Inbound leads who ask not to be called again are honored and logged immediately, and a false claim about affiliation or referrals runs into the Impersonation Rule at 16 CFR 461.3. Several states require all parties to consent to recording; use a disclosure. DialBreeze applies your internal DNC list, quiet hours and attempt caps; list provenance and claims discipline are yours. This guide describes rules, not legal advice.