Cold Calling Scripts: Examples and a Simple Framework
TL;DR: A good cold calling script gives human reps a clear introduction, a relevant reason to call, a useful question, and a possible next step. Treat the words as a flexible framework. Verify account facts, label assumptions, listen to the response, and stop when the person clearly declines further contact.
What does a good cold calling script include?
Use a short conversation structure that leaves room for the prospect’s answer. The script should help you begin a relevant discussion, not force every response back into the same pitch.
Use the framework and three fictional scripts below as starting points. Adapt the language to your product and market, replace placeholders with verified context, and leave room to respond naturally when the prospect answers.
- Introduction: “Hi [Name], this is [Your name] from [Company]”
- Reason: “I’m calling about [specific business process]”
- Relevant context: “[Verified fact], or [clearly labeled role-level hypothesis]”
- Question: “How are you handling [focused issue] today?”
- Next step: “Would [appropriate action] be useful?”
Here is a complete first-contact template for a fictional seller offering help with sales follow-up: “Hi [Name], this is [Your name] from [Company]. I’m calling about how sales teams keep ownership clear after a prospect responds. I don’t know whether that is a priority for your team. Is it something you handle, or does it sit elsewhere?”
If the person engages, listen before selecting the next question. If they correct your premise, use the correction. If they decline, close respectfully. The useful outcome may be a clearer understanding of fit, not a meeting.
How do you personalize the opening without inventing facts?
Use verified account information as context, and frame an unverified business implication as a question. A real company fact does not prove a particular employee has a problem.
- Verified-fact opening template: “Your [specific source] mentions [verified fact]. Does that change how your team handles [relevant process]?” Use it only after opening the source and confirming the wording
- Role-hypothesis opening template: “I work on [process] with teams in [function]. I don’t know how you handle it today. Is [focused question] relevant to your role?” Use it when you have role relevance but no account-specific trigger
Do not insert a vague reference to growth, funding, or hiring solely to make the call sound researched. The fact should connect to the question. If you cannot explain that connection without assuming urgency or pain, leave the fact out.
When website activity informs account selection, keep company signals separate from person-level interest. A company visit does not show that the employee on the phone visited your site. Open with a relevant business question instead of attributing browsing activity to them.
Record the source beside any fact in your preparation notes. Follow a consistent prospect research process so a rep can find the evidence again if the person challenges the premise, correct a stale detail, or remove an unsupported assumption before dialing.
What can you say in common calling situations?
Change the opening to reflect the relationship you actually have. A previous email is previous outreach; a real referral is direction from another person. Neither should be inflated into a relationship the prospect has not acknowledged.
Adapt these additional templates to the relationship you have.
- After a prior email: “Hi [Name], [Your name] from [Company]. I sent an email about [topic], but I don’t know whether you saw it. The reason I reached out is [relevant reason]. Is that an area you work on?” Do not say you are continuing a discussion unless a discussion actually occurred
- After a referral: “Hi [Name], [Your name] from [Company]. [Referrer] pointed me toward you for [specific responsibility]. I wanted to check whether that is right before explaining what we do. Is [process] part of your remit?” Use the referrer’s name only when the actual direction supports it
Treat each script as an opening, not a monologue. Pause after the question. If the person explains that the topic belongs elsewhere, clarify the responsibility when appropriate and update your record. Avoid delivering a product tour before understanding whether the topic is relevant.
How should you respond to common objections?
Respond to the meaning of the objection and preserve the person’s choice. A clear refusal or opt-out is a boundary, not a prompt for a more persistent script.
| Situation | Possible response | Boundary |
|---|---|---|
| The person is busy | “Understood. Would you prefer that I leave it here, or is there a better time?” | Only record a callback if one is actually agreed |
| They already use a tool | “That makes sense. Is the process working well, or is there a particular gap you are looking at?” | Do not assume dissatisfaction or argue for replacement |
| They ask for information by email | “Happy to. Which part would be useful so I send something relevant?” | Send what was requested without inventing meeting consent |
| They are not the right person | “Thanks for clarifying. Does this sit with another function?” | Make direction optional and verify any referral |
| They are not interested | “Understood. Thanks for letting me know” | End the pitch and record the response |
| They ask not to be contacted | “Understood. I’ll record that request” | Stop and apply the appropriate suppression process |
Do not turn the objection table into a branching argument where every answer leads back to a meeting request. Your next question should resolve a genuine ambiguity or serve the prospect’s stated preference.
If a request for information is vague, ask a focused clarifying question. If the person does not want to continue, accept that answer. A resource follow-up should not create a new obligation for the recipient.
How much research is enough before you dial?
Stop preparation when you can explain the person’s current role, a relevant problem hypothesis, and a defensible reason for calling. Continue only when another check would resolve a specific missing fact or uncertainty.
Spend additional preparation time on a specific uncertainty. An unfamiliar account or unclear identity may need another source check, while a straightforward role-level conversation may need no event-based personalization at all.
- Confirm the person and company you intend to contact
- Check the current responsibility relevant to your question
- Verify any fact you plan to say aloud
- Review prior conversations and contact preferences
- Remove unsupported claims about budget, urgency, or internal priorities
Hold calls when identity is unresolved. Phrase an unverified business premise as a hypothesis.
How can AI help prepare a natural talk track?
Use AI to organize approved evidence and draft language, then verify and edit the result yourself. The rep should decide what to say and how to respond during the conversation.
Try this original preparation prompt: “Using the sources and account notes I provide, separate supported facts from hypotheses and unknowns. For each fact, retain the source and relevant date. Draft a concise introduction, a relevant question, and a possible next step. Do not invent a relationship, company initiative, buying intent, or quotation.”
Read the draft aloud and remove wording you would not naturally use. Check every factual premise against its source. If the model cannot support a sentence, remove it rather than asking for a more confident version.
Before dialing, ask Chat for prospect research, insights, or a call script. Review the material and adapt the language to your conversation. With our Dialer, the rep clicks a phone number to start the call and speaks with the prospect; Chat prepares the material rather than placing the call.
When using research to prepare outreach, keep the supporting facts beside the draft. Check that the script preserves the source’s meaning, fits the person’s current role, and asks a relevant question without assuming a buying project.
How should you practice and improve the script?
Practice listening and adapting, not just memorizing the opening. Review whether the script helped the rep explain the reason for calling and respond accurately to what the person said.
- For a new rep: Rehearse the opening, a correction, and a respectful exit
- For an experienced rep: Review where assumptions or unnecessary detail enter the conversation
- For a manager: Use authorized call evidence to coach relevance, listening, and accurate next-step recording
Rehearse a correction, a request for information, and a refusal. When reviewing real calls, follow your recording policies and coach the rep’s actual words and responses.
| Red flag | Action |
|---|---|
| The opening depends on an unverified fact | Remove the claim or verify it before calling |
| The person corrects the premise | Acknowledge the correction and change course |
| The script implies a relationship that does not exist | Rewrite the introduction accurately |
| The person clearly refuses further contact | Stop and record the boundary |
What mistakes should you avoid?
Keep the script useful without letting it override evidence or the conversation.
- Pretending an unanswered email created a relationship
- Claiming a company signal identifies the person who visited
- Reciting a pitch after the prospect corrects the premise
- Treating every objection as something to defeat
- Describing an original template as a proven winning script
Sign up for Unify to put this workflow into practice with your own account context.
Frequently asked questions
Should I read a cold calling script word for word?
Use it as a guide. Keep the essential introduction and question, then adapt to the person’s actual response.
Do I need a buying signal to make a relevant call?
No. A verified role and a clearly labeled business hypothesis can support a question without inventing an account-specific trigger.
What if I sent an email but received no reply?
Say that you sent it and do not know whether they saw it. Avoid implying a prior conversation.
What should I do when asked to email information?
Clarify what would be useful and send the requested material. Do not describe that request as agreement to a meeting.
Can Unify prepare a call script?
Yes. Tell Chat who you are calling to get research, insights, or a script. Review the material, then click the phone number to place the call.
What is the right next step after an interested response?
Ask what action would be useful and record the actual agreement. Interest alone is not a booked meeting or a specific callback commitment.
Glossary
- Talk track: A flexible guide to the points a rep may discuss
- Role hypothesis: A proposed link between someone’s responsibilities and a business issue
- Opening: The introduction and reason for starting the conversation
- Objection: A concern, constraint, or response that changes the conversation
- Next step: An action actually agreed by the people involved
