cold_calling_playbook v1.0.0

---

name: "cold_calling_playbook" description: "Cold calling that respects the prospect: permission openers, gatekeeper handling, a short call structure, voicemail that earns callbacks, and a recorded-call review habit. Triggers on cold call, cold calling, sales calls, gatekeeper, voicemail script, call opener, or outbound prospecting calls."

---

Cold Calling Playbook

Purpose

Book a meeting on a call the prospect did not ask for, without tricking them, wasting their time, or breaking the law. The job of the call is narrow: earn permission, state a clear reason, sell the meeting, and leave cleanly if the answer is no. Selling the product happens later.

This skill covers live human calls, mostly B2B. It does not cover robocalls, AI voice calls, or autodialed calls to cell phones. Those need prior express written consent under US rules and sit outside a normal cold call.

Workflow

1. Clear the list before any dial

Run this check for every number. Skip a number that fails any line.

• Scrub against the National Do Not Call Registry and your internal do not call list. In the US, the FTC requires sellers and telemarketers to refresh lists against the Registry at least every 31 days. See references/compliance-us.md.
• Respect established business relationship limits only when they truly apply: up to 18 months after a purchase, delivery, or payment, and up to 3 months after an inquiry or application, and only until the person asks you to stop.
• Call only between 8 a.m. and 9 p.m. local time at the called party location. Some states are stricter. Check state rules for the prospect state.
• Transmit a real caller ID number that can receive a do not call request during business hours. Never block or spoof it.
• Identify yourself, your company, and that this is a sales call, right at the start.
• If someone says stop, do not call again, or asks to be removed, log it immediately, add the number to the internal list, and do not argue.

If you are unsure whether a call is allowed, do not make it. Get consent or use email or mail instead.

2. Prepare one reason per prospect

Before dialing, write one sentence: why this person, why now.

Good reasons name a trigger the prospect would recognize: a new role, a hiring post, a funding or expansion note, a tool they already use, a peer company with the same problem, or a deadline in their world. Weak reasons name your product, your quarter, or a generic pain.

Prep card, 60 seconds max per prospect:

• Name, role, company, timezone, best number
• Trigger in their words
• Problem you solve, stated as their problem
• One proof point you can say in one sentence, with a real source
• The meeting you will ask for: length, who attends, what they leave with

No trigger and no problem means no call. Research more or drop the prospect.

3. Open with permission, in under 30 seconds

Own the interruption. Do not pretend you know them, do not hide that this is a cold call, and do not open by asking if it is a bad time.

Pick one opener variant and adapt the bracketed parts:

Variant A, tailored permission opener: "[Name], this is [your name] from [company]. We have never spoken. I called because [trigger in one short clause]. Can I take 27 seconds to say why I called, then you decide if we keep going?"

Variant B, untailored permission opener, when you have no trigger: "[Name], this is [your name] from [company]. This is a cold call. Do you want to hang up, or can I take 27 seconds to say why I called and then you decide?"

Variant C, reason first opener: "[Name], [your name] at [company]. The reason for my call is [one sentence reason tied to their role]. If it is not relevant, tell me and I will close your file. Fair?"

Why this shape works: Gong Labs analyzed 90,380 connected cold calls and found that stating the reason for the call early was linked to a 2.1 times higher success rate than baseline in that dataset. That is vendor research on one dataset, not a guarantee. Treat it as a reason to lead with your reason, not as a promised result.

If they say no to permission: thank them, ask one short exit question if they will allow it ("Is it the topic, or just the timing?"), then honor the answer and end the call. Do not pitch after a clear no.

If they say "how have you been" style familiarity would be fake, skip it. Do not use a familiar greeting with a stranger to manufacture a past relationship.

Lines to cut:

• Asking if you caught them at a bad time. It invites a yes and ends the call.
• Asking how their day is going as a stalling tactic.
• Confirming their name as a question when you already have it. State it.
• A long company intro before the reason.

4. Run the short call structure

Target shape once permission is granted. Total aim: a focused call, often 3 to 6 minutes when it is working. Gong found successful calls in its dataset ran longer than failed ones, around 5 minutes 50 seconds on average, because the prospect stayed engaged. Length alone does not cause success. Engagement does.

1. Reason (20 to 30 seconds). Problem, peer context, one sentence solution. Example structure: "Teams like [peer type] call us when [problem] starts costing [cost]. We help by [one sentence]."
2. Check (one question). "Is that showing up on your side at all, or is it handled?" Listen to the full answer.
3. Teach briefly (30 to 40 seconds max per burst). One insight, one proof point, no feature list. In Gong data, successful reps talked more than on discovery calls, about 55 percent talk share, with longer clean bursts. That fits a cold call: you carry the meeting pitch, you do not run a full discovery interview here.
4. Sell the meeting, not the product. Name the value of the meeting itself: what you will show, compare, or map for them, even if they never buy.
5. Close with a specific ask. Offer two real times, state the length, state who joins. "Would Tuesday at 10 or Wednesday at 2 work for 20 minutes? I will bring [specific thing]. No prep on your side."
6. Confirm and protect it. Repeat the time and timezone, send the invite while still on the call if you can, and say what happens if they need to move it.

One decision at a time. Do not stack the problem, the belief, the meeting, and a calendar negotiation into one breath.

5. Handle objections as information

Classify first, then respond. Most early objections are a reflex to the interruption, not a verdict on your offer.

Use this sequence: agree in one short line, ask one clarifying question, answer that point only, re-ask for the meeting or close cleanly.

• "Send me information." Ask: "Happy to. What would you want it to answer so I send the right page, not a deck?" Send exactly that, with a dated follow up.
• "We already have something." Ask: "Makes sense. What part still takes manual work or still breaks?" If nothing, close cleanly.
• "No budget." Ask: "Is that no budget this quarter, or no value in fixing this at all?" Separate timing from value.
• "Bad timing, call later." Pin it: "Happy to. What changes, and what date should I use so I do not guess?" Log that date and honor it.
• "Not interested." Do not argue. "Understood. I will close this out. If [trigger] changes, what is the best way to reach you?" End warmly.
• "How did you get my number?" Answer plainly: name the source type (public listing, data provider, referral) without inventing a source. Offer removal on the spot.
• "Remove me, do not call again." Stop selling at once. Confirm removal, log it, end the call.

Full wording for ten common objections sits in references/objection-paths.md.

6. Work gatekeepers without lying

Gatekeepers screen for strangers. Your job is to sound like a legitimate caller with a real reason, while never misrepresenting who you are or why you called.

Rules:

• Never lie about identity, company, or purpose. Never claim a prior meeting that did not happen.
• Use minimum viable information first: your first and last name, and a request to be connected.
• If pressed on purpose, give context, not a pitch: the trigger, a peer reference you can back up, or the note you already sent.
• If pressed again, give one sentence of social proof plus company, then ask for voicemail if they will not connect you.
• Be brief and calm. Do not try to befriend, flatter, or pressure the gatekeeper, and never pitch them as if they were the buyer.
• After one or two firm blocks, stop pushing that path. Try a direct number, a different time, or another channel. Log the block.

Three step path and exact wording sits in references/gatekeeper-and-voicemail.md.

7. Leave voicemail that earns a callback or a reply

Voicemail rarely sells. It supports the email you send the same hour.

• Keep it 18 to 30 seconds. Time it in practice. Cut anything that is not name, reason, value, or next step.
• Structure: name and company, one specific reason, one outcome, one clear next step, callback number said slowly twice.
• Pair it: send an email within the hour with the same subject line you mention in the voicemail: "Left you a short note on [topic]."
• Leave at most two voicemails per prospect in a sequence. After that, email or stop.
• Never leave a prerecorded or AI voice voicemail to a cell phone without the consent that US rules require for that kind of call.

Scripts for first touch, follow up, referral, and breakup voicemail sit in references/gatekeeper-and-voicemail.md.

8. Log, then review recorded calls weekly

Log every call the same day: prospect, outcome code, objection heard verbatim, permission granted or denied, next step and date, and any do not call request.

Weekly review habit, 30 minutes, 3 calls:

1. Pick one booked call, one long failed call, and one gatekeeper or voicemail outcome.
2. Score each with scripts/call_review.py or by hand using the rubric in references/call-review-rubric.md: permission earned, reason stated in first 30 seconds, one clear meeting ask, objection classified before answering, clean close.
3. Write one change for next week only. Test that one change for a full week before judging it.
4. Track four numbers weekly: connect rate, permission rate, conversation to meeting rate, and meetings that actually show. Change the list or the opener when the numbers say so, not on a feeling.

Output Contract

When asked to plan, write, or review cold calls, return:

1. Compliance check result for the list or the single number, with any number that must not be called and why.
2. The prep card for each prospect, or a note that research is missing and what to find.
3. The exact opener to use, chosen from the variants and filled in, plus the fallback line if permission is denied.
4. The call structure for that prospect: reason, check question, one teaching point, meeting ask with two times.
5. Objection paths for the two most likely objections, word for word.
6. Voicemail script timed to 18 to 30 seconds, plus the paired email subject line.
7. Logging fields and the next scheduled touch, or a clear stop with the reason.

For a review request, return the score per rubric line, quoted moments that earned or lost permission, and one concrete change to test.

Operating Rules

1. Respect is the tactic. Permission, a real reason, and a clean exit book more meetings over time than pressure or tricks.
2. Never lie to a prospect or a gatekeeper about identity, purpose, a referral, a prior conversation, or a result.
3. Never invent numbers, customer names, or outcomes. Use only proof you can source. Label vendor research as vendor research.
4. Honor every no and every do not call request at once, in the log and in practice.
5. Sell the meeting on the cold call. Save full discovery and the product pitch for the meeting.
6. One ask at a time. One objection at a time. One change per week in review.
7. Keep voicemail short, paired with email, and capped at two per prospect in a sequence.
8. If compliance is unclear for a country, state, or number type, pause that call and check the rule first. US rules in this skill do not cover the UK, EU, Canada, or Australia, each of which has its own consent and calling rules.

References

• US compliance notes for TCPA and Telemarketing Sales Rule basics, calling hours, DNC scrubbing, and consent limits for autodialed, prerecorded, and AI voice calls.
• Objection paths for ten common objections with classify, ask, answer, and close wording.
• Gatekeeper and voicemail for the three step gatekeeper path and four timed voicemail scripts.
• Call review rubric for the weekly scoring sheet.
• Run python3 scripts/call_review.py --help for the scoring helper that totals a review and flags missed permission, missing reason, and missing meeting ask.