-
1
Open with a permission-based intro, not a pitch
The first ten seconds decide whether the call lives or dies. Lead with the prospect's name, your name and company, then ask for permission to continue. A permission opener respects the interruption, signals you are not a robo-dialer, and gives the buyer a graceful out, which paradoxically keeps more of them on the line. Avoid fake rapport ("how is your day going"), fake familiarity ("we met briefly at..."), and the elevator pitch that treats a cold dial like a demo slot. Keep the opener under fifteen seconds and move to the reason for the call before the prospect has to ask.
- State the prospect's name and confirm you have the right person: "Is this <FirstName>?"
- Introduce yourself in one line: "<FirstName>, this is <RepFirstName> with <Company>. I know I am catching you cold."
- Ask for twenty to thirty seconds: "Can I take thirty seconds to tell you why I called, and you can tell me whether to keep going or lose your number?"
Tip: The permission ask is not a trick, it is a contract. If they say no, thank them and end the call. Buyers who hang up on scripted openers come back for reps who honor the no.
-
2
State the reason for the call tied to a specific insight
Right after permission, give the prospect the reason the call is landing on their phone this week, not next quarter. The reason has to be about them, not about your product. Tie it to a trigger event (new hire, funding, product launch, segment move), a public artifact (filing, podcast, LinkedIn post), or a pattern you see across their segment. One sentence. The reader of a cold email can forgive a generic opener; the receiver of a cold call cannot. If the reason could be true of any company on the list, the prospect will treat you as any rep on the list.
- Name the trigger in plain language: "I saw <Company> opened a <Role> req last week"
- Reference a public artifact: "your Q<N> call mentioned <initiative>, and that is usually where this comes up"
- Share a segment pattern: "across <segment> teams your size, we see <specific gap> show up around month <N>"
Tip: If the rep cannot say the reason-for-the-call sentence without a template, the account is not researched enough to dial. Pull it from the list, not from the script.
-
3
Qualify with one or two open questions, not a survey
After the reason for the call, hand the mic to the prospect. Ask one, at most two, open questions that reveal whether the pain you came to talk about is actually on their desk. Questions beat statements here because they shift the call from monologue to dialogue, and because a prospect who answers a qualifying question has invested enough to hear a value prop. Keep questions short, specific, and tied to the trigger you just named. Avoid the discovery-call ladder (budget, authority, need, timeline) on a cold call: this is a thirty-second conversation, not a BANT interview.
- Tie the question to the trigger: "when teams open a <Role> req, hiring ramp usually lands with you, or does <peer function> own it?"
- Make it answerable in a sentence: avoid questions that need a slide to answer
- Listen for three signals: ownership (is this their problem), timing (is it live), and openness (did they lean in or push back)
Tip: Silence after the question is the rep's job, not the prospect's problem. Count to five before filling the gap.
-
4
Deliver the value prop in ten seconds
If the qualifier lands, the prospect has implicitly asked for the value prop. Deliver it in a single compressed sentence: who it is for, the outcome you drive, and one proof shape. No feature list, no three-pillar framework, no "we are the leading platform." The ten-second value prop is a door opener, not a demo. Its job is to earn the right to the meeting ask, not to close the deal on the phone. If the rep cannot say it in one breath, it is still a pitch, not a prop.
- Who: "<segment> <Role>s who <situation>"
- Outcome: "typically see <specific metric> move by <range> inside <timeframe>"
- Proof shape: "a <peer segment> team of <size> cut <metric> by <%> last <timeframe>" (named peer if public, anonymized shape if not)
Tip: Never stack claims. One outcome, one proof point, one next step. Buyers tune out the second claim in a row and remember the first one.
-
5
Handle the four objections you will hear every day
Four objections cover roughly ninety percent of what cold-called prospects say in the first minute: not interested, send me info, no budget, and wrong person. Scripted responses are not about overcoming the prospect, they are about buying one more sentence to see whether the objection is a brush-off or a real signal. Keep every response under two sentences, acknowledge the objection out loud, and offer the smallest possible next step. If the prospect holds the objection twice, respect it and exit. Pushing a third time is how reps teach prospects to block the number.
- "Not interested" -> "Totally fair, and most <Role>s I call say the same thing in the first ten seconds. The reason I called specifically is <one-sentence trigger>. Worth thirty more seconds, or should I lose your number?"
- "Send me info" -> "Happy to, and I want to send the right thing. Is the question more about <outcome A> or <outcome B>? I will send one page on that and skip the rest."
- "No budget" -> "Understood, budget is not what I called about. I called because <trigger>. If budget is the long pole, is this a this-year problem or a next-year problem?"
- "Wrong person" -> "Got it, thanks for the honesty. Who at <Company> owns <function> now, and is it fair to mention your name when I reach out?"
Tip: Write the objection responses in the rep's own voice, not corporate speak. A script that sounds scripted gets hung up on; a script that sounds human gets a second sentence.
-
6
Ask for the meeting with a specific time
A specific time is the single biggest meeting-rate lever most teams never pull. Instead of "do you have time next week," offer two concrete options: a day, a time, and a duration. Specificity does three things at once: it shows the rep values the prospect's time, it reduces the decision from an open question to a yes or no, and it forces the prospect to look at their calendar instead of brushing off. Keep the meeting short, name the agenda in one line, and promise a clean exit if it is not a fit. The meeting ask is the only commitment that matters on this call.
- Offer two specific slots: "Thursday at 10:15 or Friday at 2:30, your time, fifteen minutes"
- Name the agenda: "I will walk through <specific thing>, you tell me whether it is worth a second conversation"
- Promise the exit: "if it is not a fit by minute ten, we both get our time back"
Tip: Fifteen or twenty minutes books more meetings than thirty. The buyer is agreeing to a conversation, not blocking a lunch.
-
7
Confirm the meeting and send the calendar invite before you hang up
A meeting booked verbally and not confirmed on the calendar is a meeting that will no-show. Before ending the call, read back the exact day, time, time zone, and attendees, confirm the best email, and tell the prospect the invite is landing in their inbox in the next sixty seconds. Then actually send it before you move to the next dial. Include a one-line agenda, the conferencing link, a short pre-read if one exists, and a clear reschedule path. Same-day confirmation separates a cold-call booking from a cold-call hope.
- Read back the slot: "so that is Thursday the <Nth>, 10:15 to 10:30 your time, Pacific"
- Confirm the email on file: "is <email> still the best address, or should I use a different one?"
- Send the invite within sixty seconds with a one-line agenda, the join link, and your direct line in case the prospect needs to reschedule
Tip: Attach a short pre-read only if it is genuinely short. A twelve-page PDF before a fifteen-minute meeting signals the rep did not hear "fifteen minutes."
-
8
Log the call in the CRM with disposition, notes, and next step
The call is not finished when the prospect hangs up, it is finished when the record is clean. Log the disposition (connected, no-answer, voicemail, do-not-call, meeting booked), paste one or two sentences of what the prospect actually said in their words, update the trigger field, set the next step with a date, and link the recording if the platform captured one. Clean logging compounds across the team: the next rep who touches the account inherits context instead of guessing, and sales leadership can coach from real signal instead of hearsay. A good script with bad logging produces one meeting; a good script with good logging produces a pipeline.
- Pick the disposition from a fixed list, not a free-text field
- Paste the prospect's own words into the notes, not the rep's interpretation
- Set the next-step task with a date and a channel (email, call, LinkedIn), never "follow up"
- Confirm the recording consent flag and the recording link, if the platform captured one, honor every opt-out immediately
Tip: Logging in the dialer is not logging in the CRM. Verify the activity, note, and task actually synced to the account record before closing the tab.