Cold Call Script: A Complete Template and Sales Conversation Examples

Use this cold call script as a conversation map. Replace every bracketed field, choose a reason you can explain, and leave space after the question. The opening should make it easy for the person to understand who is calling and correct your assumptions.

Copyable first-call template

You: Hi [name], this is [your name] from [company].
We haven't spoken before. Is now an okay time for a brief question?

Prospect: What's this about?

You: We provide [specific product or service] for [relevant task].
I noticed [accurate business detail], and I'm calling to ask whether
[related task] falls within your role.

Prospect: Yes, it does.

You: How are you handling [specific part of that task] today?

Prospect: [Describes current approach.]

You: So [short summary of their answer]. Have I understood correctly?

If relevant: We can show you [demonstrable capability].
Would a short conversation about [named issue] be useful?

If they agree: Who should join, and what would you want to check?
Let's agree [time] and [purpose] before I send an invitation.

If not relevant: Understood. Thanks for clarifying. I'll leave it there.

For the reason field, use a business detail that connects to your actual offer: a published service expansion, a location you serve, or a responsibility listed on the company's website. A detail does not establish a problem. Say what you noticed, then ask whether the associated task matters.

Before using the template, decide what you can offer at the end: a relevant document, a focused demonstration, or a conversation with a specialist. If the person declines the opening question, thank them and end the call. Do not deliver the rest of the pitch over their refusal. Keep their ability to stop the conversation visible in your wording.

A useful SDR cold call script connects the first question to the next request. In the conversation below, the seller offers equipment-service scheduling software. The prospect explains a specific coordination issue, so the seller proposes checking that issue rather than requesting a general product tour.

Example: Service operations call

Maya, SDR: Hi Alex, Maya from ServiceRoute. We haven't spoken before. Can I briefly explain why I called?

Alex, operations manager: Go ahead.

Maya: We provide software for assigning equipment-service visits. Your website lists service across several locations. Do you handle scheduling for those teams?

Alex: I do, but we already have a scheduling system.

Maya: Understood. When a visit changes after assignment, how does the office let the technician know?

Alex: Dispatch calls them. The schedule is fine; confirming changes is the awkward part.

Maya: So the issue is confirming a changed assignment, rather than making the original schedule. Is that right?

Alex: Yes, though I don't want a whole replacement project.

Maya: I understand. Our software includes assignment acknowledgments. I can ask our specialist to show that workflow and discuss what a change would involve. Would that be useful enough for a short conversation?

Alex: Possibly. I need to know whether technicians can use our existing phones.

Maya: Let's make device compatibility the first question. What phone requirements should the specialist prepare for?

Alex: I'll send our device list. Email me the details first.

Maya: Certainly. Which business email should I use? I'll send the proposed topic and ask you to reply if you want to arrange a time.

Alex: Use the address on my contact page.

Maya: Thanks, Alex. I'll send that summary. Goodbye.

Notice that Maya gets agreement to an email, not a booked meeting. Her notes should preserve that distinction. These cold call script examples depend on listening: HubSpot's calling guidance recommends repeating relevant points about the prospect's company or goals to clarify understanding. If Alex had said changed assignments were already handled well, Maya would have no reason to keep pitching that problem.

Build the wording around a task you can discuss and a capability you can demonstrate. The best cold call script for your team is one a representative can explain when the prospect asks, “What do you mean?”

Start with four replacements:

• Role: Name the person responsible for the task, such as a service manager, office administrator, or purchasing lead.
• Context: Use a relevant, accurate detail about the business. Remove personal observations that have no connection to the offer.
• Capability: State what the product or service does in plain language. Keep an example, specification, or demonstration available to support it.
• Question: Ask how the buyer handles the task. Avoid a question that assumes failure, waste, or dissatisfaction.

For example, replace “We transform your operations” with “We supply labelled storage units for maintenance parts.” Then ask, “Who decides how parts are organised at your service desk?” That wording offers a clear subject without promising a result you have not measured.

When you have no customer case study, offer something inspectable. A supplier can discuss a sample layout; a software seller can demonstrate a named workflow. Do not replace missing evidence with an invented customer name, an unsupported saving, or a claim that similar businesses all have the same problem.

Keep separate versions for different responsibilities. An operations lead may discuss assignment changes; a purchasing lead may need supplier requirements. The WIIFT framework can help you review the opening from the recipient's perspective. Before calling, read the reason aloud and ask whether the next question actually follows from it.

Use a short branch that resolves the immediate uncertainty. Your cold call script does not need a speech for every objection; it needs a respectful way to decide whether this first conversation should continue.

“I'm busy.”

Say: “Understood. Would you prefer I leave it here, or is there a better time for a brief call?” If they suggest a time, confirm it. If they decline, end the conversation. A busy response is not permission to ask a longer question.

“Just send me something.”

Say: “Certainly. Would an overview of [named capability] be relevant, or did you have a different question in mind?” If they answer, send material on that subject. Ask which business address to use and whether they want any further contact. If they decline more questions, avoid turning the email request into another qualification exercise.

“You have the wrong person.”

Say: “Thanks for letting me know. Which role handles [task], if you're able to point me in the right direction?” Accept a role name or a general contact channel. Do not pressure someone for a colleague's direct number.

“We're not interested.”

Say: “Understood. Thanks for your time.” If they ask you not to contact them again, record and respect that request through your organisation's process.

Keep the outcomes distinct. “Send an overview” means send the agreed overview; it does not mean “book a demo.” These branches are for first-call routing. Save detailed fit questions for a later conversation the person has chosen to have.

Identify yourself and the purpose before asking for help. A gatekeeper is helping route a business enquiry; give them enough context to do that without implying an existing relationship.

Gatekeeper template

Hi, this is [name] from [company]. We provide [specific offer].
I'm trying to find the role responsible for [business task].
Could you tell me the appropriate way to contact that team?

If asked whether you know the contact:
No, we haven't spoken. This is a new business enquiry about [task].

If offered a general mailbox:
Thank you. Is there a subject or department name I should include?

Avoid “They're expecting my call” unless that is true. If the receptionist says enquiries must go through a supplier form, use that route. A transfer is an opportunity to introduce yourself again, rather than permission to sound like a returning customer.

A cold call voicemail script should leave a clear identity, a concrete subject, and a usable way to reply. Keep the wording short enough to say comfortably without rushing.

Voicemail template

Hi [name], this is [your name] at [company].
I'm calling about [specific business task].
We provide [brief, accurate offer].
If that is relevant to your role, you can reach me at [number].
Again, [your name], [company], [number]. Thank you.

Callback template

Say: “Hi [name], thanks for returning my call. This is [your name] from [company]. My message was about [task]. Is it okay to explain the reason briefly?” Then return to the relevance question.

Keep the voicemail consistent with your cold call script. Do not create urgency about an unspecified “account matter” or “important issue.” If the callback reaches someone else, explain the business subject again instead of assuming they heard the original message.

Change the relevance question and the proposed next step to fit the buying situation. A business software enquiry concerns a work process; a dealership call may concern an individual's current vehicle search. The same opening should not imply that those contexts are interchangeable.

Example: B2B software

A tech sales cold call script can start: “Hi Priya, Sam from QueueDesk. We provide software for routing customer-support requests. Your company lists separate support teams for its product lines. Do you oversee how requests move between those teams?”

If Priya confirms the responsibility, ask: “What happens when a request reaches the wrong team?” If she describes a relevant difficulty, offer a demonstration focused on routing rules. Leave compatibility, security, and implementation questions for someone equipped to answer them. If those questions determine whether a meeting is useful, include them in its proposed agenda.

Example: Dealership outreach

A car sales cold call script might say: “Hi Jordan, this is Lee from [dealership]. We haven't spoken before. I'm calling to ask whether you're currently considering a vehicle change. Is it okay to ask a brief question?” Use this wording only when your organisation has established that the contact is appropriate for outreach.

If Jordan is considering a change, ask what the vehicle needs to accommodate: passengers, equipment, or a particular journey. Offer to check a relevant vehicle's current availability before discussing a visit. Do not invent a prior enquiry, promise a trade-in value, or quote unconfirmed finance terms. If Jordan is not looking, end the call.

In either setting, use the answer to narrow the offer. Once a buyer wants a deeper business discussion, move to a discovery-call framework rather than extending the opening into a full needs interview.

SayNow AI provides conversation practice in professional scenarios and feedback on delivery, structure, clarity, and persuasiveness. Its coaching approach supports spoken rehearsal; the Sales Pitch scenario gives you a place to work on how you express a relevant offer.

Use this suggested practice sequence: speak the identity, reason, and question from your chosen opening, then pause as you would for an answer. Review the feedback and choose one delivery change, such as separating a long sentence or making the question easier to follow. Rehearse your cold call script again with that single change.

Next, practise saying a brief summary of the prospect's answer before making your request. Keep your own branch notes nearby and check the wording against the offer you can actually deliver. Finally, say the next-step request aloud without adding extra promises. Focus each round on a specific speaking decision. Practise your opening in the Sales Pitch scenario.

Use one sheet for the wording you are testing, what happened, and the next agreed action. Keep practice observations separate from customer statements so a rehearsal idea does not become a claim about a prospect.

Copyable preparation and outcome sheet

Contact role and relevant task: [details]
Reason for calling and source: [business detail and URL]
Offer I can explain or demonstrate: [capability]
Opening question: [wording]
Branches prepared: [busy / send information / wrong person]

Outcome: [no answer / declined / referral / email / conversation]
What the person actually said: [brief factual note]
Agreed next action, owner, and timing: [details or none]
Contact preference or request to stop: [details]
One wording change to rehearse: [change]

For a practice session, try the opening, a busy response, and an email request. After each attempt, check whether your identity was clear, whether the reason led naturally to the question, and whether you stopped to listen. Rehearse the weakest transition again instead of adding another paragraph to memorise.

After an actual call, record the outcome before interpreting it. A correct contact and a relevant issue are different findings. An email request and meeting agreement are different commitments. For broader delivery work, use sales communication skills training; for consulting-specific targeting, use the separate consulting cold-calling guide.

Choose one cold call script, replace its fields with accurate details, and practise the transitions aloud. On the call, let the answer determine whether you ask another question, agree a specific next step, or thank the person and stop.