Find AI Prompts
Home›Sales›Cold Call Scripts and Talk Tracks
SalesProspecting & Outreach

AI Prompts for Cold Call Scripts and Talk Tracks

A cold call has about twenty seconds before the prospect decides whether to keep listening. The talk track earns those seconds with an honest opener that asks for permission, a reason for the call that is about them, and a question that is easy to answer. Reading a pitch does not work; neither does improvising. A talk track is a structure with prepared language, not a script read verbatim.

These prompts build the track, prepare the brush-off responses (the first thirty seconds is where most calls end), and write voicemails that do a job in the sequence. Objection handling once a conversation is under way lives on the objection response page.

Before you use these

Have these ready to replace the highlighted [variables]:

The prompts

1. Build the cold call talk track

Best forA structured track with prepared language for each stage, in your own voice.
Inputs needed
  • Persona
  • Angle
  • Proof
  • Call goal
How to use itGive the model phrases you naturally use. Ask for a structure with options per stage, not a monologue.
Expected outputTalk track: opener options, reason for call, qualifying question, value bridge, ask, and the transitions — with timing and the words to avoid.
Act as a sales call coach building a cold call talk track for calling [persona] at [segment] about [product].

Angle: [the reason for the call, about them]
Proof: [one number with context]
Goal: [meeting / qualifying answer / referral]
My voice: [phrases I use, phrases I hate]

Build the track with timing:
1. Opener (0–10s): two permission-based options ('…did I catch you at a bad time?' style and a direct 'the reason I'm calling' style) — honest, no fake familiarity, name and company clearly.
2. Reason for the call (10–25s): the angle in one or two sentences, about their situation, ending in a question they can answer easily.
3. Bridge (25–60s): if they engage, the one-sentence value statement and the proof point — then a second question, not a pitch.
4. Qualifying question: the single question that tells us whether to ask for the meeting.
5. The ask: specific (day, duration, purpose) with a fallback ask (send something relevant, referral to the right person).
6. Transitions and recovery lines: what to say when they interrupt, when they ask 'what is this about?', when they are not the right person.
7. Words and habits to avoid for this persona.

Write in natural speech. Mark the parts to say verbatim versus the parts to adapt. Keep the whole track under 90 seconds of talking.

2. Prepare responses to the first thirty seconds of brush-offs

Best forStaying in the conversation past 'not interested', 'send me an email' and 'we already have something'.
Inputs needed
  • Common brush-offs you hear
  • Angle and proof
  • Persona
How to use itList the brush-offs you actually get. The model prepares a response for each with the acknowledge → reframe → question structure, and the point at which to let go.
Expected outputBrush-off response table with the acknowledgement, the one-line reframe, the question, a second response if it repeats, and the graceful exit.
You are preparing early-call brush-off responses for cold calls to [persona] about [product].

Brush-offs we hear: [e.g. 'not interested', 'send me an email', 'we already use X', 'no budget', 'call me next quarter', 'how did you get my number?', 'I'm in a meeting']
Angle and proof: [summary]

For each brush-off:
1. Acknowledge (one short line that shows we heard it, no 'I understand, but…').
2. Reframe (one line that makes the call about their situation, not our product — using the angle).
3. Question (easy to answer, moves toward whether there is a reason to talk).
4. If they repeat the brush-off: one more response, then the graceful exit with a small ask (permission to send one relevant thing, or the right person's name).
5. The tell that this brush-off is a real 'no' versus a reflex, and how to tell the difference within one exchange.

Rules: never argue, never plead, never ask 'what would it take'. Keep every line under 20 words. Write in the voice of someone who respects the prospect's time.

3. Write voicemails that connect to the sequence

Best forVoicemails that do one job — make the next email get opened — instead of pitching to a machine.
Inputs needed
  • Sequence position
  • Angle
  • Email subject line that follows
How to use itTell the model which touch the voicemail is and what email follows. It writes short voicemails that reference the email and give one reason to open it.
Expected outputTwo or three voicemail variants under 20 seconds each, with the email subject they point to, and the rules for tone and repetition.
Act as an SDR coach writing voicemails for a cold sequence to [persona] at [segment].

Sequence: [touches and where each voicemail sits; the email that follows each]
Angle: [summary] Proof: [one number]

Write:
1. First voicemail (after the first email): name, company, one sentence on why (the angle), reference the email by subject line, one reason to open it, name and number again. Under 20 seconds spoken.
2. Second voicemail (mid-sequence): a different angle or the proof point, again pointing to the email. Under 15 seconds.
3. Final voicemail (with the breakup email): gracious, no pressure, one line on what we would have helped with, door left open.
4. For each: the exact email subject line it references, so they are consistent.
5. Tone notes: pace, no upspeak on the ask, how to say the number.
6. Rules: no 'just checking in', no 'wanted to touch base', no questions on voicemail (they cannot answer), no more than three voicemails in a sequence.

Write them as spoken language, with pauses marked.

Related prompts

Logical next step

After this, most sales teams move on to Objection Handling and Response Libraries.

Get the free B2B Sales AI Starter Kit → Nine of these prompts as a target → engage → qualify workflow with an intake worksheet, delivered by email. See what's inside

All Sales prompts · Search the full library