Build a full cold call script: opener, problem, value, CTA
Builds a complete, branching cold call script with labeled sections, stage notes for delivery, and pre-written pivots for the most likely prospect responses. Total talk time stays under 60 seconds. You get a call structure a new SDR can run on day one, instead of a monologue that collapses at the first interruption.
You are a cold call script architect who has built scripts for outbound teams running Orum and Nooks dialers at high volume. You know a script is not a monologue; it is a structured conversation with planned branches. Your scripts follow a strict arc: opener (under 15 seconds), problem statement (the pain, in the prospect's words, not yours), value (one outcome with proof, no feature lists), and a CTA that asks for a specific meeting.
Build me a complete cold call script. Requirements:
- Total talk time for my side: under 60 seconds across the whole call, excluding prospect responses.
- Structure it in labeled sections: OPENER, PROBLEM, VALUE, CTA, with my exact words plus a stage note for each (pace, tone, when to pause).
- After the opener and after the problem statement, write the two most likely prospect responses and a one-line pivot for each, so the script branches instead of assuming cooperation.
- The problem statement must be phrased as a hypothesis I am checking ('usually when I talk to ops leaders, X is breaking'), not an accusation.
- The CTA proposes a specific meeting length and gives a reason the meeting itself is worth their time.
- Banned: 'solutions', 'streamline', 'reach out', 'touch base', feature dumps, more than one statistic, and any sentence over 20 words.
Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. What do you sell, and what single outcome do customers get?
2. Who are you calling: role, industry, company size?
3. What are the top 2 pains this persona says out loud, in their own words if you know them?
4. What proof do you have: a metric, a named customer, a before-and-after?
5. What meeting are you asking for: length, format, and what they get out of it?
Once you have my answers, write the script. If my proof point is weak, flag it and suggest what evidence to gather.How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Answer all five interview questions; question 3 works best with verbatim phrases pulled from call recordings or reply emails.
- 3
Read the script aloud with a timer and cut anything pushing your total past 60 seconds.
- 4
Run 20 to 30 dials, note where calls die, and paste those moments back into the same chat for a revision.
- 5
Hand the final version to your team with the stage notes intact.
Best practices
The problem-as-hypothesis framing is the load-bearing part; if you edit anything, keep that.
Keep the one-statistic rule; a second number turns a conversation into a webinar.
Revisit the script monthly with fresh objection data rather than rewriting from scratch.
Example: what this looks like in practice
A new SDR at a 60-person staffing software company answers the interview: they sell automated candidate sourcing, outcome is 'recruiters fill roles 9 days faster', personas are agency owners at 10 to 50 seat firms, the loud pain is 'my recruiters spend half their day sourcing instead of closing', and proof is a named client who cut time-to-fill from 32 to 23 days. The model returns a four-section script with pivots for 'we already use LinkedIn Recruiter' and 'now's not a good time', plus stage notes like 'pause two beats after the hypothesis'. After 60 dials and one revision pass, she is booking one meeting per 22 connects.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Opener, problem, value, CTA, in that order, with your total talk time under 60 seconds. The opener earns 30 seconds, the problem statement tests a pain hypothesis in the prospect's language, the value section gives one outcome with one proof point, and the CTA asks for a specific meeting. The structure works because each section earns permission for the next.
More cold calling scripts & openers prompts
Cold call role-play: the AI plays a skeptical VP and scores your performance
Turns the model into a realistic, interruption-prone VP buyer who objects, tests, and warms or cools based on how you actually perform, then scores you across five dimensions with the exact moment you lost them and a drill to fix it. It is unlimited call practice with instant, specific feedback and no burned leads.
Adapt your cold call script to a new industry without losing what works
Rewrites your proven script for a new vertical while preserving its structure, marking every change with the reason, and delivering an industry brief, shifted objections, and the outsider red flags in your original. You enter a new market sounding like someone who has sold there before, without rebuilding your script from zero.
Annotate your script with tonality, pacing, and pause marks
Turns your script into a performance document: inline pause marks, stress caps, pacing shifts, and falling-inflection notes on your exact words, plus your three danger zones, mandatory silences with durations, and a 60-second vocal warm-up. It coaches the half of cold calling that word-focused script work never touches.