Verified against Claude · 2026-07-23
Pair a cold-call opener with a voicemail drop that earns a callback
Writes a 20-second phone opener built to survive the first ten seconds before a hang-up, plus a matching voicemail for when the call goes unanswered, with the pattern-interrupt line and the objection it is meant to preempt made explicit.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are writing a cold-call opening script and a matching voicemail drop for a B2B sales rep calling Daniel Osei, Head of IT Infrastructure at Merrow Health Systems. Most cold calls are decided in the first ten seconds — before the prospect has consciously decided anything, they've already decided whether this is a pitch to escape or a person worth another ten seconds. Write for that reality. CONTEXT FOR THE CALL Their company posted a job listing last week for a "Cloud Migration Lead," suggesting an infrastructure overhaul is starting WHAT WE SELL a managed cloud-cost monitoring platform for healthcare IT teams OBJECTION TO PREEMPT "We already have a vendor for cost monitoring" DESIRED NEXT STEP A 10-minute call next Tuesday or Wednesday afternoon LIVE-CALL OPENER Write the opener as a sequence of short, speakable lines, not a paragraph — nothing longer than about 12 words per line, because a sentence too long to say in one breath is a sentence that will get interrupted. Structure: (1) a permission-based, non-scripted-sounding greeting that names the reason for the call inside the first breath, not after a warm-up; (2) a one-line acknowledgment that this is an unscheduled call, since pretending otherwise reads as evasive the instant the prospect notices; (3) a pattern-interrupt line built from Their company posted a job listing last week for a "Cloud Migration Lead," suggesting an infrastructure overhaul is starting specific enough that a generic telemarketer script could not have produced it; (4) a direct, low-stakes ask for permission to continue for 30 seconds, framed as a genuine question the prospect can say no to, not a rhetorical one. If "We already have a vendor for cost monitoring" names something the prospect is likely to say in the first ten seconds — "we already have a vendor for this," "not the right person," "no budget this year" — write one line that addresses it before it's raised, without sounding defensive about an objection nobody has voiced yet. VOICEMAIL DROP Write a separate voicemail, under 20 seconds when read aloud at a normal conversational pace — that's roughly 45 to 55 words including the callback request. State your name and company once, not twice. Reference Their company posted a job listing last week for a "Cloud Migration Lead," suggesting an infrastructure overhaul is starting in one sentence, the same anchor as the live opener, since a voicemail that sounds like a different call than the one they might have half-heard about creates confusion, not curiosity. State A 10-minute call next Tuesday or Wednesday afternoon as a specific, low-friction ask, and give a callback number spoken at a deliberately slower pace than the rest of the message, since a number said at normal speaking speed is the single most common reason a prospect who wants to call back can't. WHAT NOT TO DO No "how are you today" as an opener — it signals script before a single real word has been said. No apologizing for the interruption; an apology invites the prospect to agree that this is, in fact, an unwelcome interruption. No stacking more than one question in the live opener before pausing to actually let them answer. OUTPUT FORMAT 1. The live-call opener, line by line, with a word count per line. 2. The voicemail script, with its total word count and estimated read-aloud duration. 3. One sentence naming which specific moment in the opener is most likely to get a hang-up, and why the pattern-interrupt line is built to survive it.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Structuring the opener as short, speakable lines rather than a written paragraph respects a real constraint of live speech that a paragraph-style script actively works against: a sentence long enough to require a mid-sentence breath is a sentence with a natural interruption point, and a prospect looking for a reason to hang up will use exactly that pause, so keeping every line short enough to say in one breath removes the easiest excuse to cut the call short before the actual ask is even reached. Naming a specific pattern-interrupt line tied to a real trigger, rather than a generic warm-up, targets the documented psychology of cold-call reception: prospects pattern-match an unfamiliar caller's first few words against every telemarketing call they've ever received, and a script that sounds like every other script gets sorted into that bucket and dismissed before the actual value proposition is heard, regardless of how good that value proposition is. Acknowledging the call is unscheduled, rather than pretending otherwise, is a deliberate transparency move that removes a specific objection before it can be raised — a prospect who notices they're being handled without an admission of the obvious becomes more guarded, not less, and naming it plainly signals a rep confident enough not to need the pretense. The voicemail's slow-callback-number instruction targets a genuinely common and easily overlooked failure: a phone number spoken at the same pace as the rest of a fluent, rehearsed message is frequently impossible to write down accurately on a first listen, meaning a voicemail that otherwise did everything right can still fail purely on delivery mechanics, and a rep who never notices this keeps blaming voicemail response rates on message content when the actual bottleneck was never legible. Requiring the same trigger anchor in both the live opener and the voicemail, rather than two disconnected messages, closes a subtler gap: a prospect who receives a call, misses it, and then hears an unrelated voicemail has no way to connect the two into one coherent outreach attempt, which quietly doubles the cognitive load of deciding whether to call back at all.
Verified against
Claude Sonnet 4.5 · 2026-07-23
ChatGPT GPT-5.1 · 2026-07-24
Changelog
- 2026-07-24 — Initial publish, verified against Claude (Sonnet 4.5) and ChatGPT (GPT-5.1).
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
