Industry playbooks
Telecommunications sales call playbooks
Your buyers are watching churn spike for two billing cycles after every outage, paying for truck rolls where half come back no-fault-found, and defending capex to a committee that meets four times a year. Practising against a network ops or customer experience leader who will push back on OSS/BSS integration, false-positive rates and the budget cycle means you've already had the hard part of the conversation before you dial the real one.
Every call type for Telecommunications
Scripts, sample dialogue, objection handling and a live AI buyer for each one.
Cold Call
You dialled someone who was mid-something-else — reviewing a P&L, walking between meetings, about to eat lunch — and they picked up without knowing your name, your company, or why their phone rang. There is no prior email, no referral, no webinar download to reference. The first three to five seconds decide whether you get thirty more, and the first thirty decide whether you get a meeting. Your job on this call is not to sell the product, qualify thoroughly, or run discovery — it's to earn a next conversation by naming a problem so specifically that the prospect thinks 'how do they know that about us?' You will be interrupted, you will hear a reflex brush-off before they've processed a word you said, and you have to stay conversational through it without sounding like you're reading. Success is a calendar hold, not a good chat.
Read the playbook →Demo Call
A scheduled demo with someone who has already had the pitch conversation and said yes to seeing it — which means they are not here to learn what it does, they're here to find out where it breaks. They arrive with a mental list: how it hooks into the systems they already run, who on their team owns it once you're gone, what happens at 2am when it falls over, and how long before it's actually doing something useful. They will interrupt. Every interruption is either a buying question or a disqualification test, and your job is to answer it in their environment, not in your sandbox. If you run the standard tour — click here, then here, notice this dashboard — they go quiet, you hear typing, and you've lost the room without them ever saying no. The demo you rehearsed is a resource, not a script; the call is won by how well you handle the detours.
Read the playbook →Discovery Call
A 25-minute scheduled discovery call with a prospect who took your first touch seriously, cleared time, and showed up expecting to be diagnosed — not sold to. They already know your one-liner, so repeating it burns credibility. They have a real, layered problem: a surface symptom they'll hand over in the first two minutes, a mechanism underneath it they'll explain if you ask a decent follow-up, and a cost or political consequence they'll only name once you've proven you can hold the conversation without reaching for a demo. Your job is to earn each layer with open questions, quantify what you find, understand how a decision like this actually gets made in their shop, and leave with a specific, dated next step that both sides agreed to out loud. Pitch early, monologue, or run a BANT checklist and they will answer politely, in short sentences, and never take the next meeting.
Read the playbook →Manager Coaching Call
This is the 1:1 nobody sleeps well before. You manage a rep who has missed two quarters in a row — not catastrophically, but consistently — and you've got 30 to 45 minutes to find out whether this is a fixable skill problem, a fixable effort problem, or the start of an exit. They walk in with the excuses pre-loaded: the leads are garbage, the territory got carved up, we're 20% over on price against the challenger. Some of that is even partly true, which is what makes it hard. Underneath it, they know their discovery calls are shallow and they stopped prospecting sometime around week three of last quarter when they got busy 'working' two deals that were never going to close. They will not volunteer that. They'll only get there if you stay curious longer than they expect, look at actual numbers instead of arguing about feelings, and make it clear that admitting the real problem is safer than defending the fake one. Your job is not to win the argument, deliver a motivational speech, or put them on a PIP by minute ten. It's to get to one true root cause and leave with one changed behaviour they actually agreed to.
Read the playbook →Pricing Negotiation Call
This is the call after the technical win. They've run the eval, they've told their VP your product is the pick, and the only thing left is the number. They are not trying to talk themselves out of buying — they're trying to buy the same thing for less, and they will use every lever they have to do it: a low anchor ("honestly, we budgeted about half that"), a competitor's quote they may or may not still be considering, a case study or logo trade dangled as if it's currency, a threat to push the PO into next quarter, and long, deliberate silence after they name a figure. The trap is that they're pleasant about all of it, so it doesn't feel like a fight — it feels like a friendly conversation in which you keep making small, reasonable-sounding concessions until you've given away 30 points and gotten nothing. Your job is not to win the negotiation; it's to hold price by trading, keep the relationship warm enough that they still want to sign with you, and leave the call with a dated path to signature.
Read the playbook →Upsell Call
You're calling a customer who is already paying you, already reasonably happy, and has no idea you're about to ask for more money. They picked up expecting a check-in. Your job is to convert an account review into an expansion conversation without burning the goodwill that made the account healthy in the first place. The buyer's default posture is defensive on three fronts: the budget for your category is already spent for the year, their team is underwater and can't absorb another rollout, and they suspect they aren't even getting full value from what they bought last time — a suspicion you must address before they'll hear anything new. This call is won or lost in the prep: if you can open with their actual usage numbers and the specific result they've already gotten, you get a real conversation. If you open with "I wanted to tell you about our new module," you get a polite ten minutes and a "send me something."
Read the playbook →Warm Call
A warm call is one where somebody else's credibility got you the answer. A peer downloaded your guide and said "you should call Dani", or a mutual contact fired off a three-line intro that the prospect skimmed on their phone and archived. They pick up expecting you, but expecting is not the same as knowing — they can usually name the referrer and almost never name what you sell. You start with maybe ninety seconds of borrowed goodwill and a very specific obligation: prove the referrer wasn't wasting their time. Warmth is a loan, not a grant. Two generic sentences — "So, just to give you a bit of background on us" — and you've converted a warm call into a cold call the prospect now feels mildly embarrassed to be on, which is worse than cold. The job is to cash the referral fast, convert it into one specific, testable reason you're relevant to *them* rather than to the referrer, and get out with a real second meeting.
Read the playbook →
Who you're calling
In Telecommunications, the people who pick up are network and customer operations leaders at carriers, RSPs and MSPs. The titles you will actually reach:
- Chief Technology Officer
- Head of Network Operations
- GM Service Assurance
- Director of Field Operations / Field Services
- Head of Customer Experience
- GM Consumer / Retention
- Chief Operating Officer
What keeps them up at night
Name one of these in your first thirty seconds and you have earned the rest of the call.
Churn spikes 30–60 days after every material outage
The mass-service-disruption itself is survivable; the cancellations that land the following two billing cycles are not. Retention teams are throwing bill credits, plan downgrades and free speed tier upgrades at a base that has already decided to leave, which trashes ARPU to save a service they lose anyway six months later. The GM Consumer can tell you exactly which suburbs churned after which POI incident, and nobody in Network Ops can promise it won't repeat.
Truck rolls are the single biggest controllable opex line — and half are avoidable
Every dispatch is a technician, a van, fuel, and a two-hour appointment window. A brutal share come back as no-fault-found, or as a fault that sat on the access-network side and was never the RSP's to fix in the first place. Field Ops leaders are being asked to lift first-time-fix rate and cut dispatch volume in the same breath, while the network keeps generating tickets that the L1 queue can't triage without sending someone.
Support queues collapse exactly when the network does
Average speed of answer is fine at 11am on a Tuesday and catastrophic during a regional fault, because 4,000 customers dial in about the same event. Handle times blow out, the outbound retention campaign gets paused to cover inbound, and CSG and complaint-handling obligations start ticking. Every peak fault is also a compliance event and an ombudsman-complaint generator.
Alarm noise means the NOC is reacting, not predicting
The EMS throws thousands of events; the assurance platform correlates some of them; a handful of experienced operators know which ones actually matter at 2am. Mean time to detect is dominated by the customer calling in before the NOC knows. Leaders have been sold 'AIOps' before, watched false positives train the team to ignore the tool, and are now openly suspicious of anything that adds another alarm source.
Wholesale margins leave nothing to absorb inefficiency
Reselling access at wholesale-plus-a-thin-margin means CVC/aggregation costs, backhaul commitments and support cost per service decide whether the consumer book makes money at all. A 10% lift in cost-to-serve isn't an efficiency story, it's the difference between a profitable and unprofitable segment — and the CFO knows the per-service numbers better than the CTO does.
Capex is locked to a committee calendar, not to the problem
Network capex is planned annually, reviewed quarterly, and already committed to core upgrades, tower builds and fibre-to-the-node replacements. Anything unbudgeted either waits for the next cycle or has to be argued as opex against an existing line — usually the field services or contact centre budget, which means taking money off a peer.
What they'll push back with
The objections that come up on nearly every call, and a response that keeps the conversation alive.
- “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 useful predictions off your existing alarm and performance feeds within six weeks, there's nothing to integrate and you've spent no engineering time.
- “The capex committee meets quarterly and nothing moves faster than that.”
- Then we shouldn't be a capex item. What we're proposing sits in opex against dispatch cost — if we take 15% 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've already got 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.
- “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.
- “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 complaints come from.
- “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 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.
Their language
Use these the way they do. Getting one wrong costs more credibility than getting none of them right.
Jargon
- ARPU
- churn (voluntary vs involuntary, and by cohort)
- truck roll / dispatch
- no-fault-found (NFF)
- OSS/BSS
- MTTR and MTTD
- backhaul
- POI / NNI
- CVC and AVC (access and aggregation charges)
- RSP (retail service provider)
- mass service disruption (MSD)
- first-time-fix rate
- SLA credits
- average speed of answer / average handle time
- CSG and ombudsman complaints
- GPON / OLT / DSLAM
Metrics they are measured on
monthly and annualised churn rate, by cohort and by region, ARPU (and ARPU erosion from retention offers), truck rolls per 1,000 services and cost per truck roll, no-fault-found rate, first-time-fix rate, MTTR and mean time to detect, network availability / unplanned outage minutes, average speed of answer and SLA compliance during peak faults, cost to serve per service per month, NPS and ombudsman complaints per 10,000 services
Related industries
Buyers with adjacent pressures, and the same call types against them.
Practise against a Telecommunications buyer
A live AI prospect with Telecommunications context — their pressures, their jargon, their objections. They talk back, they interrupt, and they can hang up on you. You get a scored breakdown when the call ends.
Start a roleplay