Explore

Cold Call Script - Cira Apps

Cira Apps - Cold Call Script

This isn't a rigid script to be read word-for-word, but a framework and guide for the conversation. Tone should be calm, curious, and detached from the outcome.

Permission-Based Opening & Pattern interrupt:

You: "Hi (Name), it's is just (Your Name) calling with Cira apps. I was wondering if you could help me out for a moment?”

Why this works: It's low-pressure, uses "just" to minimize perceived importance, and asks for help, which psychologically makes people more receptive than being told something. It puts them in control. (Ref: NEPQ Advanced Win the Gatekeeper Scripts.pdf)

State the Purpose (If permission granted):

Prospect: "Okay, maybe. What’s this about?"

You: "Well, we often speak with (mention their likely role, e.g., IT Directors, Operations Managers) just like yourself about how they manage the flow of contact and calendar information across their organization and I was calling to see if your company might be open to exploring if there are any potential hidden gaps or inefficiencies in how that information stays synchronized and up-to-date for everyone... so your not losing track of time and that way you can focus on more important things that need your attention...?"

Why this works: It's neutral ("potential hidden gaps," "inefficiencies"), references their likely peers, states the problem area (syncing info) without pitching your solution, and crucially, gives them an easy "out" ("perfectly buttoned up"). This reduces pressure and defensiveness.

Initial Situation Question (If they show any openness or curiosity):

Prospect: (Might say something like) "What do you mean by gaps?" or "We manage it okay, I think." or "Maybe..."

You: "Well, for example, you know how some organizations find challenges when a contact details of someone changes, it's not always updated instantly and accurately across everyone's mobile devices, Outlook, or shared company directories. So they end up having a lot of errors and spending too much time having to fix that...?

Well, what we do is exactly that. Our software company provides tools to sync all that important information across the organization and ensures it stays up to date.

Qualify Questions:

Just so I know, Would you mind sharing briefly how your team currently handles keeping shared contacts and calendar data across the board?

Why this works: It provides a neutral context ("some organizations find") and then asks an open-ended question about their current state (a Situation Question). It encourages them to talk about their process, not about buying something.

Problem Awareness (Based on their answer):

You: "Okay, so you use (mention EXACT system/process they described). And how is that working for the team in terms of ensuring everyone always has the most current information?"

You: "And what happens if, say, a salesperson updates a key client's contact on their phone – how does that information reliably get updated in the central company directory or for others who need it?"

Identify a Potential Gap (If the conversation reveals one):

If their answers suggest manual work, delays, inaccuracies, or frustrations related to syncing contacts/calendars, you've found a potential area where CiraSync might help.

Transition to Next Step (If a potential gap is surfaced):

You: "Okay, based on what you've mentioned about (briefly reference the potential issue, e.g., 'the manual steps involved in updating shared contacts' or 'ensuring calendar accuracy across devices'), it might be useful for us to schedule a brief, separate call – maybe 15-20 minutes? and we could explore your specific situation in a bit more detail and see if what we do at CiraSync could potentially help streamline things or solve that (mention the specific pain point again) for you. Would you be open to something like that?"

Why this works: It uses cautious language ("might be useful," "potentially help"), clearly defines the purpose and time commitment of the next step (a discovery call, not a demo yet), links it back to their potential problem, and asks for permission to schedule.

Key Takeaways to keep in mind before every call:

Tone: Calm, curious, slightly detached, professional. You're an investigator, not a seller, on this first call.

Pacing: Speak clearly and don't rush. Allow for pauses.

Listen: Pay close attention to their answers; they guide your next question.

Goal: The primary goal is to determine if a discovery call is warranted, not to sell CiraSync on this initial interaction.

References:

NEPQ Black Book of Calling Leads.pdf

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.