By Siddharth GangalAn SDR call script should make the first conversation easier, not make the rep sound programmed. The most useful scripts are modular: identity, verified context, reason for calling, role-level relevance, and one question. When the prospect answers, the rep leaves the script and listens.
Direct answer. In the first 30 seconds, say who you are, cite one truthful reason for calling now, connect it to a plausible consequence for the person’s role, and ask one low-friction diagnostic question. Do not claim you “know” their problem. Earn the next 30 seconds rather than pitching the whole product.
This is a script library for SDR prospecting openers. The sales call talk-track guide remains the canonical framework for a full call—opening, discovery, value, objection branches, and close. The sales objection framework owns complete diagnosis after pushback. The examples here are editorial templates, not claims that a phrase produces a particular conversion rate.
Use an SDR script as a modular opener
Memorize the components, not the sentences. Salesforce’s current cold-calling guidance recommends a personal opening, relevant questions, and a defined next phase. A useful SDR script follows that shape while preventing false personalization.
Write alternatives in your natural speaking voice. Read each aloud. Remove words you would not use with a colleague. Mark the point where you must stop and let the prospect answer. If the script requires the prospect to remain silent for 45 seconds, it is a pitch, not an opener.
| Script component | Purpose | Unsafe shortcut |
|---|---|---|
| Identity | Tell the person who is calling | Hiding the company or pretending the call is personal |
| Verified context | Explain why this account or person entered the call list | Invented research, familiarity, or private pain |
| Reason now | Connect the context to a timely business question | Manufactured urgency |
| Role relevance | State a plausible consequence in the buyer’s language | Generic “save time and money” benefit |
| Question | Invite correction or a short answer | Stacking three discovery questions before listening |
Build the first 30 seconds from five parts
Use this five-line preparation card. The bracketed fields are inputs to verify, not merge tags to read robotically.
“Hi [first name], this is [name] with [company]. I’m calling because [verified trigger or relevant operating fact]. Teams with [role-level responsibility] often have to decide [specific tradeoff the trigger creates]. I don’t know whether that is live for you—how are you handling [one narrow job] today?”
Neutral cold opener: “Hi Maya, this is Jon with Acme. I work with RevOps teams on routing and CRM follow-through. I don’t know if either is a priority at Northstar, so I’ll start there: who owns the handoff from an inbound request to the correct opportunity today?”
Permission-led variant: “Maya, Jon at Acme. This is a prospecting call based on Northstar’s expansion into Europe. Can I take 25 seconds to explain the operational question behind it, then you can tell me whether I’m off?”
Direct hypothesis variant: “Maya, Jon at Acme. I saw Northstar is hiring its first regional RevOps lead. That can create a choice between central routing and local ownership. Is that something your team is designing now, or is the role focused elsewhere?”
These variants do different jobs. Neutral is safest when context is thin. Permission-led makes the commercial nature explicit and gives control. The hypothesis variant uses stronger context but must invite correction. The full sales call opening guide covers delivery, pacing, and transitions.
Adapt openers to the reason for calling
The trigger changes the reason and question—not your identity. Never convert a public event into a claim about private priorities.
New executive
“Hi [name], [rep] with [company]. I saw [executive] joined to lead [function]. New leaders often audit [specific operating area] early, though I don’t know their mandate. Has [area] entered the review, or is the focus somewhere else?”
Hiring expansion
“Hi [name], [rep] at [company]. [Company] has several open roles across [team/region]. When headcount changes, [role] usually has to choose how [handoff, training, coverage, or reporting] scales. What is the team standardizing first?”
Funding or market expansion
“Hi [name], [rep] with [company]. I’m calling after [verified funding/market announcement]. Expansion can put pressure on [role-owned system] before it changes revenue. Are you already adjusting [narrow job], or is the current model holding?”
Technology change
“Hi [name], [rep] at [company]. I saw [verified implementation/hiring signal related to technology]. Teams making that change often revisit [integration, adoption, or process job]. Is that inside your remit, and if so, what has to remain stable?”
Prior engagement or referral
“Hi [name], [rep] with [company]. [Truthful source] pointed me to you after [specific context]. They said you own [area], not that you have a problem. Is [job] worth a brief comparison, or should I close the loop?”
Before dialing, use the sales call preparation checklist to separate verified facts, reasonable hypotheses, and unknowns. If a trigger cannot be verified, use the neutral opener.
Adapt relevance and questions by buyer role
Keep the trigger constant and change the consequence and question. Suppose the verified trigger is a company hiring 20 salespeople across two regions.
| Role | Relevant consequence | Question to test |
|---|---|---|
| VP Sales | Coverage, ramp, consistency, and manager visibility | “What must stay consistent as the two regions ramp?” |
| RevOps | Territories, routing, CRM state, permissions, reporting | “Which ownership rule becomes hardest when the new reps start?” |
| SDR manager | Lists, messaging, coaching capacity, handoffs | “Where does the current onboarding workflow break first at that cohort size?” |
| Enablement | Certification, content, practice, reinforcement | “What behavior must every new rep demonstrate before live calls?” |
| Salesforce/CRM owner | Schema, access, automation, duplicate and write control | “Which CRM changes are required before accounts are assigned?” |
| Founder | Repeatability, cost, leadership bandwidth, pipeline learning | “Which part of the founder-led motion is hardest to transfer?” |
The question should be answerable without the prospect revealing sensitive information. It should test whether the job exists and who owns it. If the person says it is outside their remit, ask for the correct function once; do not pressure them to disclose a name.
Bridge initial objections without debating
Use bridge responses to diagnose, not rebut. Keep these short because the canonical objection framework provides the full Listen–Acknowledge–Explore–Respond pattern.
| Prospect says | Limited bridge | Stop condition |
|---|---|---|
| “Not interested.” | “Understood. Before I close this out, was I wrong about the job, or is it simply not a priority?” | They repeat the decline or ask not to be contacted |
| “Send me information.” | “Happy to. So I send one relevant thing, is the question [A], [B], or neither?” | They decline to clarify; send only what was requested or close |
| “We already use [vendor].” | “That makes sense. Is the current setup fully covering [narrow job], or is that not something you are reviewing?” | They confirm fit and no evaluation |
| “Bad time.” | “Got it. Would you prefer I close the loop, or is there a specific time when a 30-second context check is appropriate?” | No permission or explicit decline |
| “How did you get my number?” | Answer truthfully and specifically; offer correction or suppression. | Any request to stop or remove data |
Do not chain questions after a clear no. Do not conceal data provenance. Do not treat an objection as a contest. Move to the full objection-handling framework when the prospect raises a substantive concern and remains willing to talk.
Use the printable SDR call structure
Print one card per call block.
BEFORE: Account ___ · contact/role ___ · verified fact and source ___ · hypothesis (not fact) ___ · role consequence ___ · one question ___ · permitted call basis/time/region checked ___ · suppression checked ___.
OPEN: “Hi ___, this is ___ with ___.” · reason now ___ · relevance ___ · question ___ · STOP AND LISTEN.
BRANCH: relevant → one discovery question · wrong owner → ask for function · busy → permission or close · objection → acknowledge + one diagnostic · decline/opt-out → confirm and disposition.
CLOSE: agreed next action ___ · owner ___ · date/time ___ · requested material ___ · CRM disposition ___ · suppression/update ___.
Use the broader cold call checklist for equipment, dialing, discovery, disposition, follow-up, and coaching controls that sit around the words.
Practice with this 100-point rubric
Score observable behavior, not charisma. Rate each criterion from one to five, multiply by its weight, add the results, and divide by five. This yields a practice score out of 100—not a forecast of meetings booked.
| Criterion | Weight | Observable evidence |
|---|---|---|
| Context accuracy | 15 | Every factual reference is verified; no invented familiarity or pain. |
| Opening clarity | 15 | Identity, company, and purpose are understandable on first listen. |
| Role relevance | 15 | Consequence fits the role without generic benefit claims. |
| Question quality | 15 | One short question is easy to answer and reveals whether a conversation exists. |
| Listening and adaptation | 20 | Rep stops, reflects the answer, and selects the next branch rather than reading. |
| Pressure control | 10 | Permission, decline, correction, and opt-out are handled without argument. |
| Next-step clarity | 10 | Outcome, owner, and timing are explicit or the call is cleanly closed. |
Run three rounds. First, the buyer follows the expected path. Second, the buyer corrects the trigger or role assumption. Third, the buyer interrupts, objects, or declines. Record with participant consent where required. The rep self-scores before receiving peer and manager scores. Calibrate scorers on the same example so “sounds confident” does not substitute for accuracy and listening.
Test scripts without fooling yourself
Change one meaningful component at a time. Define the eligible account set, role, trigger, call window, dial method, rep cohort, and outcome taxonomy. Randomly alternate two opener structures where practical, while keeping list and timing balanced. Do not compare a funded-account script with a generic list and attribute the difference to words.
Measure valid conversations, correct-owner discoveries, permission to continue, qualified next actions, explicit declines, opt-outs, wrong or invalid data, correction time, and follow-through completion. Report counts and denominators. Listen to a sample of both successful and unsuccessful calls; disposition labels alone can reward optimistic logging.
A script “wins” only if it improves the intended behavior without increasing pressure, false claims, opt-outs, or data errors. Small samples should remain directional. Preserve call examples, scoring notes, eligibility rules, and version dates so later results can be reproduced.
Keep compliance upstream of the script
Legal and policy eligibility is a pre-dial gate, not a sentence added to the opener. The FTC’s Telemarketing Sales Rule guide discusses scope, disclosures, misrepresentation, calling time, Caller ID, abandoned calls, records, prerecorded messages, and Do Not Call requirements. It says most B2B calls are exempt from the TSR while describing exceptions; it also warns that FCC, state, and other rules may apply.
Do not read “most B2B calls” as universal permission. Requirements vary by calling technology, recipient, purpose, location, consent, industry, number type, and jurisdiction. The FCC’s 2024 consent ruling states that telemarketing robocalls require prior express written consent, subject to applicable scope and exemptions. That is not a rule for every manually dialed B2B call; it is a reason to classify technology and recipients before dialing. Maintain suppression, honor requests, identify the caller truthfully, avoid spoofing or misleading claims, and train reps on the applicable procedure. Seek qualified legal review for your program; this article is not legal advice.
A strong SDR script is therefore short, truthful, adaptable, and easy to abandon when the prospect speaks. The opener earns a conversation. Listening determines what happens next.