Telecommunications · Cold Call
Telecommunications Cold Call Script: Opening a CTO or Head of Network Ops Who Didn't Ask for Your Call
The person you're about to ring runs a NOC, a field workforce, or a consumer book — and they are almost certainly mid-something. A Head of Network Operations is looking at an event storm out of one OLT. A Director of Field Operations is staring at tomorrow's dispatch board and a first-time-fix number that hasn't moved in two quarters. A GM Consumer is in a spreadsheet showing which suburbs churned 45 days after the POI incident in March. None of them woke up hoping a vendor would call.
That's actually good news, because it means the bar is clear. You are not going to win this call with your funding round or your "AI-powered assurance platform" — this buyer has been sold AIOps before, watched the false positives train their operators to close the tickets unread, and is now openly hostile to anything that adds another alarm source. You win by naming something true about their week: that the truck roll line is the biggest controllable opex they own and a chunk of it comes back no-fault-found, or that the cancellations from the last mass service disruption landed in the following two billing cycles and retention burned ARPU with bill credits to hold a base that left anyway.
This telecommunications cold call script is built for that thirty seconds. It uses the buyer's own numbers — truck rolls per 1,000 services, cost per truck roll, NFF rate, average speed of answer during a peak fault, cost to serve per service per month — and it assumes you will be interrupted before you finish sentence two. The goal is not a good conversation. It's a 20-minute hold on a calendar, sent while they're still on the phone.
The cold call script
Say it in your own words. The structure is the part that matters.
- 1
Before you dial — 60 seconds, out loud
Say each of these to yourself before the number rings. If you can't, don't dial. 1. WHO: Exact title and what they own. "Head of Network Operations — owns the NOC, MTTD, unplanned outage minutes. Does not own the field crews." A CTO call is about detection and capex framing. A Director of Field Operations call is about dispatch volume and first-time-fix. A GM Consumer call is about churn cohorts and ARPU erosion. Never run the same open on all three. 2. TRIGGER: An outage on the status page, a regional fault in the news, an ombudsman/complaints report, a new NBN or wholesale pricing construct, a migration announcement, three field technician job ads in one region. If there's no trigger, the segment is the trigger: "every RSP with a consumer book between 50 and 500 thousand services is having the same argument about dispatch cost." 3. ONE PROBLEM. Written down. One. Truck rolls OR post-MSD churn OR queue collapse during a fault. Not a tour. 4. THE ASK: "Twenty minutes, Thursday 8:15 or Friday 4." 5. Have the follow-up email drafted in a window before you dial.
- 2
Opener — the first eight seconds
"Hi Marcus, it's Priya from [Company]. We haven't spoken — this is a cold call. Can I have thirty seconds to tell you why I rang, and you can tell me to get lost?" Then STOP. Two full seconds of silence. Do not fill it. Delivery notes that matter more than the words: - Downward inflection on "...tell me to get lost." Not up. Up sounds like begging. - Slow down. Cold-call nerves speed you up about a third; a NOC lead reads fast talking as a script. - Match their energy within one notch. If they answer flat and clipped — most network people do — do not come in bright. Variants: - Pattern interrupt: "Marcus — Priya, [Company]. You don't know me. Bad time?" - Trigger-led: "Marcus, Priya from [Company]. I saw the notice about the Tuesday fault in the northern POI region — that's actually why I rang. Got a minute?" Never: "How are you today?", "Did I catch you at a bad time?", "I'll be brief", "the reason for my call is to introduce myself and our platform."
- 3
The reason — Field Ops / COO version (truck rolls)
"We work with a handful of RSPs and regional carriers on the dispatch line. The thing that keeps coming up with Field Operations directors is the no-fault-found rate — the tech drives out, spends the two-hour window, and it was either nothing or it sat on the access-network side and was never yours to fix. So you're carrying the van, the fuel and the hour, and the customer still thinks you failed them. Meanwhile you're being asked to lift first-time-fix and cut truck rolls per thousand services in the same board pack. Is that anywhere near your world, or have you got that solved?" The out at the end — "or have you got that solved" — is what makes an honest answer safe. Say it every time.
- 4
The reason — GM Consumer / Head of CX version (post-outage churn)
"We work with consumer teams at a few RSPs. What we hear from GMs of Consumer is that the outage itself is survivable — it's the cancellations that land 30 to 60 days later, two billing cycles out. And by then retention is throwing bill credits and free speed tier upgrades at a base that's already decided, so you erode ARPU to hold a service you lose in six months anyway. You can name the suburbs and the incident; nobody in Network Ops can promise it won't repeat. Is that a real thing at your place, or am I describing someone else's problem?"
- 5
The reason — CTO / Head of Network Ops / GM Service Assurance version (MTTD)
"We work with network operations teams at a few carriers and RSPs. The consistent one is mean time to detect — the EMS throws thousands of events a night, correlation catches some, and a lot of the time the actual first signal is a customer calling the contact centre. So MTTD is really being set by your inbound queue, not your NOC. I'll say up front: I'm not calling to sell you another alarm source. Is detection-before-the-call something you're actively working on, or is it living with?" The pre-emptive "not another alarm source" line matters with this buyer. They have been burned. Saying it before they do buys you twenty seconds you would otherwise spend defending.
- 6
Two questions, maximum — then close
You are not running discovery. You need just enough to make the meeting relevant. Pick two, narrow and factual: - "Roughly what's your NFF rate sitting at — is it tracked separately or bundled into closure codes?" - "When there's a regional fault, what does average speed of answer do — does the outbound retention campaign get paused to cover inbound?" - "Is the churn cohort analysis after an MSD something Consumer does, or does it go to the NOC?" - "How are you triaging L1 today — is that a person reading alarms or a rules engine?" - "Is that on this year's plan or is it just being absorbed?" Listen for the ADMISSION: "yeah, it's a mess," "we've been meaning to look at that," "don't ask me about closure codes." The moment you hear it, stop asking and ask for the meeting.
- 7
The ask
"Here's what I'd suggest. Twenty minutes — not a demo, no deck. I'll walk you through what we found in one region's fault and dispatch history at a carrier about your size: how many of those dispatches were predictable before the van moved, and what they'd cost at your cost per truck roll. You tell me on the call if it's worth a second one. I've got Thursday at 8:15 before your day starts, or Friday late afternoon. Which is less bad?" Elements doing the work: twenty not thirty; "not a demo"; the meeting content is their data shape, not your product; two slots, not an open calendar; explicit exit. The moment they pick: "Sending the invite now while we're talking — can you tell me it's landed?" A meeting confirmed on the line no-shows far less often.
- 8
Gatekeeper / EA screen
"It's about their dispatch and no-fault-found numbers — Priya at [Company], he won't know me, it's a cold call. Is he the right person for field operations cost or is that sitting with someone else now?" Short, calm, specific. Never claim a prior relationship, never say "it's personal," never be cute. Asking the EA to correct your targeting often gets you the right name and a warm transfer.
- 9
Voicemail — under 20 seconds, no ask
"Marcus, Priya at [Company] — you don't know me. Calling about no-fault-found dispatches and how many of them were visible in the telemetry before the van left. It's a thing we see a lot at RSPs your size. I'll try you again Thursday morning. 02 [number]." The voicemail's job is name recognition for attempt two and the email. No meeting request, no website, no value prop.
- 10
The soft no and the recycle
"No problem, I'll let you go. Last thing — is this a timing thing or a 'not a priority' thing?" [Listen. Then one of:] "Got it. When does the capex cycle lock for next year — is it the September committee?" "Understood. Who does own dispatch cost — is that Field Services or does it roll up to the COO?" "Perfect. I'll come back to you the week after that committee. One email so you've got my name, nothing else." A cold call that produces a dated callback and one piece of intel — the committee date, the real budget owner, the name of their assurance platform — is a working call. A cold call that produces "send me something" and nothing else is a polite hang-up you accepted.
- 11
Follow-up email — send within five minutes
Subject: Our call just now — NFF dispatches "Marcus — as promised, short. You said the closure codes are mostly 'other' and you can't separate access-side faults from your own before dispatch. That's the exact thing I want to show you a number on: one region, one quarter of fault and dispatch history, and how many of those rolls were predictable from the performance telemetry you already publish. Thursday 8:15 is in your calendar. Twenty minutes, no deck. If it's not relevant three minutes in, say so and I'll drop off." Use their words. "Mostly other." "Not ours to fix." "The suburbs that churned." Those phrases go into the email and then into the discovery call.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Marcus, it's Priya from [Company]. We haven't spoken — this is a cold call. Can I have thirty seconds to tell you why I rang, and you can tell me to get lost?
Buyer
I'm in the middle of something. What's it about?
Rep
Fair. Thirty seconds. We work with network operations teams at a few RSPs and regional carriers. The consistent one is mean time to detect — the EMS throws thousands of events overnight, correlation catches some, and the actual first signal on a degradation is often a customer calling the contact centre. So MTTD ends up being set by your inbound queue rather than your NOC. I'll say up front, I'm not calling to sell you another alarm source. Is detection-before-the-call something you're actively working, or is it just living with?
Buyer
We've got an assurance platform. We've got event correlation. Every vendor who rings me says the same three sentences and then tries to bolt another feed onto my NOC. My operators already ignore two dashboards.
Rep
Then they'd ignore a third by week three, and I'd deserve that. Correlation tells you what already broke — that's its job and yours sounds like it's doing it. The narrow bit we get pulled into is the lead indicator on a service degrading before anyone calls, delivered into the ticket your team already works, no new queue. And I'd want the precision threshold agreed with whoever runs your NOC floor up front — if it fires on noise, kill it. Can I ask one thing and then I'll get to the point?
Buyer
Go on.
Rep
When a degradation does turn into a dispatch — what's your no-fault-found rate sitting at? Tracked separately, or buried in closure codes?
Buyer
Honestly? Our closure codes are a joke. Half of them are 'other'. And that's before you get to the fact that a big share of what we dispatch on isn't even ours — it sits on the access network. We send a tech, he tells the customer it's not us, the customer complains anyway, and we wear it. I can't fix a fault I don't own.
Rep
Right — and that's exactly the truck roll you shouldn't be sending. Not because you can fix it, because you'd know before the van moves. If the degradation pattern says upstream, you raise the wholesale fault, you tell the customer the truth on the first call instead of the third, and your tech stays on a job that's actually yours. On the closure codes — that's true at nearly every carrier I've worked with, and it's why we don't use them. The signal comes off performance and alarm telemetry, not off what someone typed at 4:45 on a Friday.
Buyer
Look, even if I liked it, we're mid-migration on the BSS side. My engineering team has zero spare cycles this year, and anything with capex attached waits for the committee, which meets quarterly and is already spent on the fibre replacement program.
Rep
So let's take both of those off the table. The ask on your engineers is two hours from someone who can point at the northbound feed you already publish, and a NOC lead to look at output weekly. Read-only, out of band, nothing written back, no change window, nothing that touches the migration. And it shouldn't be a capex item — it sits against dispatch cost, so it argues on truck rolls per thousand services and cost per truck roll, not the network build. If your committee is nine weeks out, that's nine weeks you could spend proving your own number so you walk in with data instead of my slide.
Buyer
Send me something. I'll look at it.
Rep
Happy to, but the generic deck dies in that room — your CFO will ask what it does to cost to serve per service and nobody in the meeting will have the number. Better version: twenty minutes with me, no demo, no deck. I'll take one region's fault and dispatch history from last quarter and come back with how many of those dispatches were visible in the telemetry beforehand. Then it's your data, not mine. Thursday 8:15 before your day starts, or Friday late?
Buyer
Thursday. But if you turn up with a product tour I'm gone in five minutes.
Rep
Understood — if I do, tell me and I'll drop off the call myself. Sending the invite now while we're on the phone. Can you tell me it's landed? And one thing before Thursday: who should be on it besides you — does dispatch cost sit with Field Services or does it roll up to the COO?
Buyer
It's landed. Bring it to me first. If it's real I'll pull in field services.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"Integration with our OSS/BSS stack kills most vendors. Everyone says they've got connectors and then we spend nine months on a data model."” | "Fair — so let's not talk connectors. Which systems hold your fault tickets, your inventory and your dispatch? If it's a standard assurance platform plus a homegrown inventory layer, we read from the northbound feed you already publish and write nothing back until you tell us to. First phase is read-only, out of band, no change to your ticket flow. If we can't produce something useful off your existing alarm and performance feeds within six weeks, there's nothing to integrate and you've spent no engineering time." |
| “"We already have an assurance platform and event correlation. Why do I need another alarm source?"” | "You don't, and that's the point — if this generated a new alarm queue your NOC would ignore it by week three. Correlation tells you what already broke. What we're adding is a lead indicator on degradation before the customer calls, delivered into the ticket you already work. And I'd want to agree the precision threshold with your NOC lead up front — if it fires on noise, kill it." |
| “"Half our faults sit on the access network. We don't own the fault, so we can't fix it — we just wear the customer call."” | "Right, and that's exactly the truck roll you shouldn't be sending. If you can tell before dispatch that the degradation pattern is upstream, you raise the wholesale fault, you tell the customer the truth, and you keep your technician in the van. Fewer no-fault-founds and fewer 'we sent someone and they said it wasn't us' calls — which is where a lot of your ombudsman complaints come from." |
| “"Our field and fault data is a mess. Half our closure codes are 'other' and the inventory doesn't match what's actually in the ground."” | "That's true at nearly every carrier I've worked with, and it's the reason the prediction is worth something — the signal comes from performance and alarm telemetry, not from closure codes. Bad inventory affects where we route the dispatch, not whether we spot the degradation. And honestly, one of the first outputs is a list of where the inventory is wrong, because the telemetry doesn't match the record." |
| “"The capex committee meets quarterly and nothing moves faster than that."” | "Then we shouldn't be a capex item. This sits in opex against dispatch cost — if we take a slice of avoidable truck rolls out, it pays from the field services line, not the network build. And realistically, if the next committee is nine weeks out, that's nine weeks we could spend proving the number so you walk in with your own data instead of my slide." |
| “"We're mid-migration and my engineering team has zero spare cycles this year."” | "Understood — so what's the actual ask? Two hours from someone who can point us at the data feed, and a NOC lead to look at the output weekly. No integration sprint, no change window, nothing that touches the migration. If it needs more than that from your engineers before you see value, we've designed it wrong." |
| “"Send me something and I'll take it to the exec. We look at this stuff once a year."” | "Happy to, but a deck won't survive that room — the CFO will ask what it does to cost to serve per service and nobody will have the number. Give me one region's fault and dispatch history for the last quarter and I'll come back with how many of those dispatches were predictable and what they cost you. Then you're presenting your own data, not a vendor's." |
| “"Not interested." (fired in the first three seconds)” | "Totally fair — you don't know what I do yet. If I'm wrong I'll hang up: is no-fault-found dispatch volume something your team is actively working on this year, or genuinely not a thing at your place?" One reframe only. If they repeat it, take the recycle: "Understood. Is that a timing thing or a never thing? Either's fine, I just want to get it right." |
Questions reps ask about this call
- How is a telecommunications cold call script different from a generic B2B one?
Two ways. First, the buyer set is fragmented and each one owns a different number — a Head of Network Operations owns MTTD and unplanned outage minutes, a Director of Field Operations owns truck rolls per 1,000 services and first-time-fix, a GM Consumer owns churn by cohort and ARPU. The same opener across all three sounds like a mailing list. Second, this market has scar tissue: nearly every network leader has bought an 'AIOps' tool whose false positives trained the team to ignore it. If your script doesn't pre-empt 'another alarm source' in the first thirty seconds, they'll raise it and you'll spend the rest of the call defending instead of qualifying.
- Which problem should I lead with on a cold call to a CTO versus a Field Operations director?
One problem each, written down before you dial. CTO or GM Service Assurance: mean time to detect being set by the inbound queue rather than the NOC, and what unplanned outage minutes do to the board pack. Director of Field Operations or COO: no-fault-found rate and the dispatches that were never theirs to fix, framed against cost per truck roll. GM Consumer or Head of Customer Experience: the cancellations landing 30–60 days after an MSD, and the ARPU erosion from bill credits and free speed tier upgrades used to hold them. Head of Customer Experience also responds to average speed of answer collapsing during a regional fault while CSG and complaint clocks tick.
- What do I say when they tell me their fault and inventory data is a mess?
Agree immediately — it's true almost everywhere and arguing costs you credibility. Then move the ground: the signal you're using comes from performance and alarm telemetry, not from closure codes that are half 'other'. Bad inventory affects where a dispatch gets routed, not whether the degradation is visible. It also helps to offer the by-product: one of the first outputs of looking at telemetry against records is a list of where the inventory is wrong. That turns their objection into a reason to take the meeting.
- They said capex is locked to the quarterly committee. Is the call dead?
No — it's dead only if you let it stay a capex conversation. Reframe it as opex against an existing line: dispatch cost, or contact centre cost during peak faults. Then use the committee date as your close: 'if the next one is nine weeks out, that's nine weeks to prove the number so you walk in with your own data.' Even on a soft no, always leave with the committee date. A cold call that produces a dated callback and the name of the real budget owner is a working call.
- How do I stop 'send me some information' from ending the call?
Treat it as a polite hang-up, because it is. Trade it: 'Happy to, but the generic deck dies in the exec room — your CFO will ask what it does to cost to serve per service and nobody will have the number. Give me one region's fault and dispatch history for last quarter and I'll come back with how many of those dispatches were predictable.' If they still won't book, extract two facts — their assurance platform and whether dispatch cost sits with Field Services or the COO — plus a callback date. Never hang up with an email address and nothing else.
- What should the meeting ask actually be at the end of a telco cold call?
Twenty minutes, explicitly not a demo, with the content being their data shape rather than your product: one region's fault and dispatch history, how many rolls were predictable, what that is at their cost per truck roll. Offer two specific slots — early morning before the NOC handover works well with network people. Then send the invite while they are still on the phone and ask them to confirm it landed. Verbally agreed meetings that get calendared later no-show at a much higher rate.
- How do I handle it when they say the fault is on the access network and not theirs?
Don't try to solve the fault — solve the dispatch. 'That's exactly the truck roll you shouldn't be sending. If you know before the van moves that the pattern is upstream, you raise the wholesale fault, tell the customer the truth on the first call, and keep the tech on a job that's yours.' Then link it to the number they're measured on: fewer no-fault-founds, and fewer 'we sent someone and they said it wasn't us' conversations, which is where a lot of ombudsman complaints per 10,000 services originate.