Cold call script for SDRs: what to say after the opener

What do you say in the opener?

Our own wording, not a tested line. The opener has one job: get ten more seconds. Three parts, in this order:

1. Your name and company, in one breath. "Hi Priya, it's Jo from Brightlane."
2. The reason for the call, in one sentence. "I'm calling because your site says the Dayton warehouse opened last month."
3. A way out. "I know this is out of the blue. Is now a bad time, or do you have a minute?"

Keep it under ten seconds, and don't ask "how are you today?". If they say "go ahead," you're at block one below. If they say it's a bad time, offer a callback time instead of pushing on. For more first lines, see cold call openers.

What's the structure of a cold call script after the opener?

Five blocks. The time budgets are our guideline, not a study.

Swipe to see more →

That's about two to three minutes of your talking, spread across a conversation that can run longer. Everything between the opener and the ask has one purpose: earn the right to ask.

How long should the whole call run? Gong's analysis of cold calls reports that reps talk about 55% of the time on successful calls, which average 5:50. Gong's pages give two figures for unsuccessful calls: about 2:55 on its 2021 cold call stats post (published August 16, 2021, updated March 4, 2026) and 3:14 on its cold calling page, which carries no date. Either way, successful calls run roughly 1.8 to 2 times as long as unsuccessful ones (our math). That's a result of the call going well, not a target to pad to.

How do you write the problem statement?

One sentence with four parts: the trigger, who it hits, the problem, and what it costs.

Formula: "When [trigger] happens, [role or company type] usually ends up with [problem]. You see it as [symptom], and the bill is [consequence]."

Three fictional examples, so you can see the shape:

• "When distributors open a second warehouse, finance usually ends up with invoice disputes. You see it as payments stuck in review, and the bill is collections running weeks late."
• "When a clinic adds a third provider, the front desk usually ends up with scheduling gaps. You see it as empty slots on the calendar next to a waitlist."
• "When software teams switch to usage pricing, billing is usually the first thing to break. You see it as finance reconciling by hand at month end."

No feature list. No adjectives about your company. If the problem doesn't make them nod, no pitch will.

Which questions should you ask?

Two or three, and stop there. Use the three-question frame (situation, pain, stakes) and the question bank in how to run a discovery call without an interrogation. On a cold call, three rules matter most (ours):

• Ask, then go quiet. Let them finish before you ask the next one.
• Their numbers, not your features. The last question should get a rough figure you can use in the ask.
• "That's covered" ends the questions. Skip to a smaller ask, such as a 15-minute side-by-side, instead of digging harder.

How do you ask for the meeting?

Propose one specific time, say how long it takes, and say what they get. Then give them an easy way to change it. One time is easier to answer than a menu: they say yes, or they tell you what works. That's our guidance.

• "Let's put 15 minutes on the calendar. Does Thursday at 2 work? If not, what's better for you?"
• "I'll show you how two teams your size cut [symptom], with their numbers. Fifteen minutes. Would Wednesday morning work, or is another day better?"
• If they hesitate: "Fair. Would ten minutes, camera off, be easier?"

Then confirm out loud: "The invite is going to [email] now. Can you check it arrived while we're on the line?" If it didn't, you find out while you can still fix the address. If they say "send me something instead," that's an objection with its own talk track: see cold call objection handling.

What does a full script sound like, start to finish?

Illustrative example. Names and company are fictional.

Jo at Brightlane (invoice automation) has called Priya, finance operations lead at a regional distributor that just opened a second warehouse. The opener worked, and Priya said, "Go ahead."

Jo: Thanks, Priya. I picked you because your site says the Dayton warehouse opened last month. [Bridge]

Jo: When distributors add a second location, finance usually ends up with invoice disputes inside a quarter. You see it as payments stuck in review, and the bill is collections running weeks late. [Problem statement]

Priya: Honestly, that's been happening.

Jo: Who's working the disputes at the moment? [Question 1]

Priya: Me, a spreadsheet and a lot of email.

Jo: When a big customer's payment sits in review, what slips first: month-end close, cash forecast, or your evenings? [Question 2]

Priya: Month-end close. We lose days.

Jo: Roughly how many days, on a bad month? [Question 3]

Priya: Three, maybe four.

Jo: Four days of close is worth fifteen minutes. I'll show you how two distributors your size handle disputes. Does Thursday at 2 work? If not, what's better for you? [Ask]

Priya: Thursday at 2 works.

Jo: Thursday at 2. Invite's going to your work email now. Can you see it? [Confirm]

Count what happened: three questions, one ask, one confirm. Jo talked most at the start, and the ask used Priya's own number.

How do you stop sounding scripted?

• Say it out loud five times before you dial. A script that reads fine on a page can sound stiff in the air.
• Bullet points, not paragraphs. Keep the five block names on a sticky note and write only the problem statement in full.
• No blank brackets. If you can't fill [trigger] for this prospect, they aren't ready for this call. Our rule of thumb: skip the dial if you can't fill the bridge.
• Record yourself. Listen for the spots where you filled silence.

Your dialer probably records. Aircall, for example, lists call recording on its Essentials plan, and call whispering and live monitoring on Professional, so a manager can coach live. Its pricing page shows the per-license price (3-license minimum), so it doesn't suit fewer than three callers. Compare more options in the best parallel dialers.

How do you practice the script every day with an AI role-play?

Rehearse the five blocks against an AI chatbot that plays the prospect, so your first bad attempt isn't on a live dial. Practice doesn't guarantee results, but it's cheap and it's yours to schedule. Our prompt (paste it into any chatbot, then fill the brackets):

Play [PROSPECT NAME], [ROLE] at [COMPANY TYPE]. Context: I will cite [TRIGGER]. I'm an SDR rehearsing a cold call. Start by saying only "Hello?" Then I'll give my opener and run five blocks: bridge, problem statement, two or three questions, the ask, the confirm. Stay in character, answer in one or two spoken sentences, never coach me mid-call. Be busy and mildly skeptical: share numbers only when my question is specific, raise one objection ([OBJECTION]) before agreeing, and accept a meeting only if I propose a specific time. When I type "end call", step out of character and tell me which block was weakest, whether I asked for the meeting, and one sentence to cut.

The 10-minute routine (our suggestion):

1. Minutes 0 to 2: fill the brackets for a real prospect on today's list.
2. Minutes 2 to 7: run one call, speaking out loud, with a phone timer running for the bridge.
3. Minutes 7 to 9: score it with the checks below.
4. Minutes 9 to 10: rerun only the block that failed.

Score yourself, yes or no:

• Did the bridge land in about 10 seconds?
• Was the problem statement one sentence?
• Did you ask two or three questions, then stop?
• Did you propose one specific time, with a fallback?
• Did you confirm the invite before "end call"?

Rotate the objection each day. The ones to drill are in cold call objection handling. Build the call like Jo's call with Priya above, with your own trigger. A chatbot is a gentler prospect than a real one, so treat a clean run as a warm-up, not proof.

How do you know your script is working?

Track the funnel, not the feeling. In Cognism's 2024 State of Cold Calling, from one vendor's own SDR team, 16.6% of dials connected (9,247 of 55,701) and 4.82% of conversations became meetings (254 of 5,265). About 57% of connects became conversations (our math on Cognism's counts). Put differently, a script that books 5 meetings per 100 conversations is running at about where that one team landed.

That tells you which number the script can move. Connect rate depends on your data and your timing. Conversation-to-meeting rate is where the script shows. Cognism also found 3 call attempts is optimal and that the most meetings were booked at 11am and 2pm.

Our test method: change one block at a time, run the new version for about 20 conversations, and compare meetings per 100 conversations. Go deeper by tracking how many cold calls it takes you to book a meeting. For a quick check of your numbers, use the Pipe Playbook calculator.

Calling, consent and recording rules differ by country and state. Check your local rules before you dial or record.