The five-part template
Copy this, then rewrite every line in your own words. Brackets are for you to fill in.
Hi [first name], [your name] here from [company]. How've you been?
Full name and company. The warm question buys a beat while they place you.
I saw [specific trigger at their company], so I figured [what that probably means for them].
Why you picked them, specifically. This is what makes the call about them.
A lot of [their title]s tell me [one problem]. Is that happening on your team, or is it a different headache?
Name one problem, then ask. The question starts a conversation instead of a pitch.
[One customer result you can back up, in a sentence.] I'd rather not guess at your situation, though.
Only say what you can prove. No proof yet? Say what you've seen across your conversations.
Could we take 15 minutes Thursday or Friday? Does morning or afternoon work better?
Specific and small, with two ways to say yes.
A worked example
Say you sell an AI customer support agent to support leaders at online retailers. You're calling Dana, VP of Customer Support. Her title tells you what she's judged on, and that decides the reason and the problem you lead with.
Hi Dana, [your name] here from [company]. How've you been?
I saw you're hiring seasonal support agents, so I figured ticket volume is climbing for your team.
Dana: "Okay, we are hiring a lot right now." A real detail earns a real answer.
Most support leaders I talk to say the same few questions, like where's my order and how do I return this, take up most of their team's day. Is that happening on your team, or is it a different headache?
Either answer is a conversation, which is what the question is for.
[A customer result you can back up, in one sentence.] I'd rather not guess at your situation, though.
Dana: "Okay. Go on." That's permission to ask.
Could we take 15 minutes on Thursday or Friday so I can show you how they did it? Does morning or afternoon work better?
Dana: "Thursday morning could work. What is it you do, exactly?" Answer in one sentence and confirm the time.
The first four seconds
| Weak | Stronger | Why |
|---|---|---|
| "Did I catch you at a bad time?" | "Hi Dana, [name] here. How've you been?" | The first hands them an exit before you've said anything. The second asks for nothing yet. |
| "I'm just reaching out to..." | "I saw you're hiring support agents, so..." | An empty reason does nothing on a big ask. A specific one earns attention. |
| "Would you be open to a chat sometime?" | "Could we take 15 minutes Thursday or Friday?" | Vague and undated is easy to defer. Small and specific is easy to accept. |
Before they decide whether to keep listening, they need to hear three things in your voice: sharp (clear and prepared), enthusiastic (real energy, not forced cheer) and expert (someone who knows their world). Record the first ten seconds of your calls for a week and listen back. Most people are surprised how much they rush.
The take-control version
The template above opens warmly and pauses. The take-control opener states who you are and why you're calling, then keeps going before asking for a response. Use it when you're confident, when the buyer is senior, or when permission-style openers keep getting you hung up on.
Mike, it's [your name] at [company]. How's the morning treating you? ... I'll keep this short. Let me tell you why I called and you can decide if it's worth your time.
I work with support teams at online retailers, and [company] stood out because [specific detail]. I wanted to find out whether handling more customer questions without adding headcount is something you're working on.
Then stop and let them talk. A brush-off is information, not a failure.
Most support leaders tell me the real problem isn't the hard tickets. It's that their best agents spend the day on questions a customer could answer in ten seconds. Does that land, or is yours different?
Expect an objection here, however good the line was.
For a team like yours that usually means three things: [benefit one], [benefit two] and [benefit three].
Three, not ten. A longer list weakens every item on it.
Worth 20 minutes next week to walk through how other teams set that up?
Don't debate which opener is better. Run each for two weeks, or split them across a team, and compare the meeting rate from conversations.
Leading with an insight
Senior buyers have heard "is that a problem for you?" four times this week. A third option is to open by telling them something true about their own world that they don't already know, and only then asking.
We talk to a lot of support leaders at online retailers, and the pattern we keep seeing is that headcount gets added to the volume rather than the repeat questions. Teams hire for the holiday peak, and by January the same handful of questions are still most of the queue. I don't know whether that's your situation. If it is, the fix usually isn't another hire. Worth 20 minutes to compare notes?
The insight has to be true, specific and checkable, and about them rather than your product. If you don't have a real pattern from your own customers or market, don't invent one. A manufactured insight is worse than a plain question, because an informed buyer spots it immediately.
Rules for every call
- Slow down. Nerves speed you up. Speak at about 80% of your normal pace.
- Ask, then stop talking. The silence after your question is where they decide to engage.
- Say it once. Don't repeat the pitch when you hear a pause.
- Never pitch features. Talk about the problem and the result.
- Sell the meeting, not the company. "I might not be the right fit. If I'm not, you'll still leave with a couple of ideas, and there's no commitment beyond the conversation."
- Take "no" cleanly. "Understood, thanks for your time." A calm exit is often what earns a second look in 90 days.
- Never manufacture urgency. An invented deadline or fake scarcity costs you the deal when it surfaces.
How to practise it
- Rewrite the five parts in your own words and read them aloud until they sound like you.
- Record yourself once, listen back, and fix the line you rushed.
- Role-play your five most common objections for ten minutes each. Alone, record both halves and play them back.
- Use the script unchanged for a full week of call blocks before changing a word, so you have something to compare against.
When they push back, use the Objection Lookup. For the system around the script, read how to cold call.