Telecommunications · Manager Coaching Call
Sales Coaching Roleplay for Telecommunications Teams: Running the Two-Quarter Miss Conversation
Your rep sells network assurance and field-efficiency software into RSPs and carriers. They've missed two quarters — not spectacularly, just consistently — and they walk into this 1:1 with the excuses already loaded: the capex committee only meets quarterly, every account is mid-migration and engineering has zero cycles, they've all been burned by AIOps and won't look at another alarm source, the tier-1 logos got carved out of my patch. Every one of those is a real thing that really happens in telecommunications. That's exactly what makes this call hard. You can't dismiss the list, because a Head of Network Operations genuinely does say those words, and you can't accept the list, because two other reps on the same segment are landing pilots anyway.
What's underneath it — and they will not volunteer this — is that their discovery calls stop at "we want better visibility into the network," they've never once walked a Director of Field Operations through cost per truck roll multiplied by no-fault-found rate, and somewhere around week three of last quarter they stopped prospecting because cold-calling a NOC lead felt futile and they had two doomed deals to babysit instead. You get to that in one way only: staying curious longer than they expect, arguing about numbers instead of feelings, and making it obviously safer to say the true thing than to defend the story.
This playbook gives you the pre-work, a block-by-block script, a 16-turn sales coaching roleplay for Telecommunications teams you can drill in DrillCall before the real 1:1, and the six telco-flavoured pushbacks your rep will bring. You have 30 to 45 minutes. The goal is one true root cause and one changed behaviour they actually own — not a verdict, not a PIP, not a speech.
The manager coaching call script
Say it in your own words. The structure is the part that matters.
- 1
Before You Open Your Mouth: Pull the Tape (Telco Edition)
You cannot coach a story about the capex calendar. You can coach a number and a recording. Walk in with five things printed: 1. **New opportunities created per week, last 90 days.** If they created 7 in month one and 2 in month three, that graph is the entire conversation and you don't need much else. 2. **Titles on the record.** For every stage-2+ opp, who's named? A solution architect and a NOC engineer is not a deal. A Head of Network Operations, a GM Service Assurance, a Director of Field Operations or a GM Consumer is. Count how many opps have zero economic buyer. 3. **Closed-lost reasons, and what sat behind them.** Count how many say "budget / capex cycle" or "no decision." Then count how many of those had a documented dollar figure — truck rolls per 1,000 services, cost per truck roll, no-fault-found rate, cost to serve per service per month. It's usually zero, and that's the finding. 4. **Stage conversion against team median.** Specifically first-call-to-second-call. If their meeting-set rate is normal and the floor drops after call one, the territory argument is dead on arrival. 5. **Two recordings.** One won, one lost. Timestamped to the exact moment discovery stopped and the demo started. One more telco-specific check: pull their pain-field text. If it reads "wants better network visibility" instead of "1,900 dispatches a month, 31% NFF, roughly $310 a roll," you already know what this call is about — but do not lead with it.
- 2
Open: Name the Stakes, Don't Swing the Hammer
Two sentences. No warm-up, no "how's the family." They know why they're here and false warmth costs you the next thirty minutes. > "Two quarters is a pattern, not bad luck, and I'm not going to pretend otherwise. But I didn't book this to read you your numbers — you know your numbers. I want to work out what's actually going wrong, because I think it's one thing and not five, and I genuinely don't know yet which one. Fair?" Then stop talking. Do not fill the pause. Do not say the words "formal plan," "performance," or "HR" anywhere in the first ten minutes — the moment they hear it they stop diagnosing and start building a defence, and you lose the only honest version of this conversation you were ever going to get.
- 3
Drain the Tank: Get All of It Out Before You Touch Any of It
This is the step that decides the call. Your rep has four or five grievances stacked up. Rebut the first one — "the capex committee" — and you'll spend forty minutes litigating capex cycles and never hear the fifth, which is always the closest to the truth. > "Before I say anything, give me the whole picture. What's making this hard right now? All of it — I don't want the diplomatic version." Then after each item, one word: **"What else?"** Ask it three times minimum. Write the list where they can see the pen moving. In this segment the list usually comes out as: capex is locked to committee cycles, every account is mid-migration with no engineering bandwidth, they've all got an assurance platform and won't add another alarm source, OSS/BSS integration scares them off, the two tier-1 accounts got carved out, and marketing pulled air cover from the wholesale segment. Read it back flat, no editorial: > "So: capex calendar, no engineering cycles, they've already got correlation, OSS integration fear, territory carve, marketing. That's the list? Nothing else?" Getting them to confirm the list is complete is what closes the escape hatches later, when a seventh reason appears at minute twenty-five.
- 4
Sort the List: Real, Partly Real, Story
Work the list *with* them. Take each one completely seriously, then put a number next to it. **Concede the true one out loud, first.** This is what buys you the right to press on the rest. > "Territory's real. You lost the two tier-1 carriers in the carve and that was about a third of your historical pipeline. I'm not going to pretend that's nothing. What I need to understand is why the mid-market RSP list didn't backfill it — there are 60-odd of them in your patch and you created two new opps in September." **Then test the ones you can measure.** > "Take the capex objection, because if that's really killing deals I need to change how we price. You've had six losses tagged budget or no-decision. Of those six, how many were positioned as opex against the field services line instead of a network capex item?" > "Priya works the same segment, same objection — she got 41 conversations last quarter, you got 38, basically identical. Where it splits is after that. She moved 12 of 41 to a second call with a Director of Field Ops or a GM Service Assurance in the room. You moved 4 of 38. Help me understand that gap." Then shut up. Five seconds. Ten. The silence after that question is doing more work than anything you could say into it. When they can't explain it, resist "exactly, that's my point." Instead: > **"Okay. What do you make of that?"**
- 5
Make It Safe to Say the Real Thing
They know their discovery is thin. They know they stopped dialling. What stops them saying it is the belief that the admission becomes a document. Break that belief explicitly and out loud. > "Let me say the thing that's sitting between us. I am not building a file right now. If the honest answer is 'I stopped picking up the phone in week three because cold-calling NOC leads felt pointless' — that's fixable, I've fixed it with reps before. What I can't fix is a version where none of it's in your control, because then neither of us has anything to do on Monday." Then the two questions that usually crack it: > "If I handed you fifteen warm intros to Heads of Network Operations tomorrow — real ones, all mid-market RSPs — do you hit the number?" The hesitation *is* the answer. Let it sit, then: > "What's the part of this you'd fix if nobody was watching and there were no consequences?" Or the direct route into activity: > "Walk me through the last three weeks of the quarter. What did a Tuesday morning look like? Not the deals — the morning." A rep who's still prospecting can describe a Tuesday in ninety seconds. A rep who stopped will describe two deals instead. That's your tell. **Do not accept a fast, flat "yeah, you're right, I need to prospect more" at minute six.** That arrives before any number has been discussed, which means it's a rep managing you out of the room, not an admission. Answer it with: *"Maybe. But we haven't looked at a single call yet — let's not land before we've looked."*
- 6
Go to the Tape: A Moment, Not a Theme
"Your discovery needs more depth" is a horoscope. Play ninety seconds. > "This is minute eleven of the Halcyon Broadband first call. Their GM Service Assurance says — and I'm quoting — 'we're seeing churn spike about six weeks after any material outage and we can't get ahead of it.' Listen to what you do next." [Play it. They demo the correlation dashboard.] > "You went to the product. Give me the three questions you didn't ask." Let **them** name the misses. In this segment the misses are almost always the same three: - Which suburbs, which POI incident, and how many services churned — by cohort? - What does the retention team spend to save one of those accounts, and what does that do to ARPU? - Who owns that number internally — is the GM Consumer in this conversation or not? If they can name them unprompted, this is an execution problem: they know the move and aren't making it, usually because they're rushing to prove value before someone hangs up. If they genuinely cannot name them, it's a skill gap and your plan is training, not accountability. **That distinction sets everything that follows. Don't skip it.**
- 7
Land on One Root Cause and Say It Plainly
You'll want to fix six things. Fix one. Reps change one behaviour at a time. > "Here's where I've landed. Territory's real, it cost you pipeline, I own part of that. But the thing actually killing you is that you're demoing at minute eleven instead of finding out what the problem costs them — so every deal turns into 'we already have an assurance platform,' and you've got no number to argue back with. And because you're only creating two opps a week, you can't afford to disqualify anything, so you carry dead deals for a full quarter, which makes the discovery problem worse. One cause, two symptoms. Does that match what you see?" Ask for agreement, genuinely. If they push back with an argument, listen — you might be wrong. If they push back with a seventh excuse, name it: > "That's a new one. We agreed the list was six. I think you're looking for a reason this isn't about the calls."
- 8
Let Them Write the Plan, Then Make It Countable
Manager-authored plans get complied with for eleven days. Rep-authored plans get done. > "Given all that — what do you want to change first?" Whatever they say, convert it into something you can both check on Friday: - "Prospect more" → **"Tuesday and Thursday, 8 to 10, calendar-blocked, five new opps a week, mid-market RSPs only."** - "Better discovery" → **"No product on a first call for three weeks. If they ask, you say: 'I'd rather show you the two screens that matter than all forty — give me ten more minutes of questions.'"** - "Quantify it" → **"No opp advances past stage 2 without three numbers in the pain field: dispatches per month, no-fault-found rate, and cost per truck roll. If you don't have them, you haven't finished discovery."** - "Get higher" → **"Every stage-2 has a named GM Consumer, Head of Customer Experience or Director of Field Operations, not just a solution architect."** Then commit to your side, out loud: > "I'll be on your first two discovery calls this week and we debrief straight after — same day, not Friday. And I'll get you the mid-market RSP list with the ones who've had a reportable mass service disruption in the last two quarters flagged, because those are the ones where the GM Consumer already has the churn-by-cohort number on a slide." Coaching that only assigns homework to the rep reads as a warning, not a partnership.
- 9
Close on the Standard, Not the Pep Talk
No "you've got this." It tells them the last half hour was theatre. > "So: two hours Tuesday and Thursday, no product on a first call, three numbers in the pain field before anything advances. I'm on your Halcyon follow-up Wednesday. We meet Friday at four and we look at opps created — opps, not deals. And to be straight with you: a third quarter like the last two changes this conversation. I don't think that's where we're headed, but I'd be doing you a disservice not saying it once, plainly." Then the last question, and let them answer it: > **"What did you hear me commit to?"** Their summary tells you whether anything landed. If they play back three things, you're fine. If they play back "prospect more," you've got another ten minutes of work to do right now.
- 10
If They Never Admit Anything: Convert the Stalemate Into an Experiment
Some versions of this end with the rep still holding the line on capex cycles and migration freezes. Don't extract a confession — you'll get a fake one and it'll cost you the relationship. > "Alright. We disagree on cause, and that's fine. Let's test it instead. Three weeks: no product on a first call, five new opps a week, all mid-market RSPs. If the problem really is that carriers can't move outside the capex calendar, that'll change nothing and I'll take the pricing and packaging fight upstairs myself — I'll go argue for an opex-only SKU. If it does change something, we've learned what we're dealing with. Either way we know more in three weeks than we know sitting here." That keeps them intact, gives you a clean decision point, and means the next conversation is about data rather than character.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Two quarters is a pattern, not bad luck, and I'm not going to pretend otherwise. But I didn't book this to read your numbers back to you — you know them. I want to figure out what's actually going wrong, because I think it's one thing and not five. Fair?
Buyer
Fair. Though I'll say up front, I don't think it's one thing. I think it's the segment. These are carriers. Halcyon is mid-migration, Brightline's engineering team is fully consumed replacing DSLAMs, and every single CTO tells me the same thing — capex is committed to core upgrades and tower builds through to next July.
Rep
Okay. Keep going — what else is making this hard? I want the whole list before I say anything.
Buyer
The assurance thing. Every Head of Network Operations I get in front of already has a correlation platform, and they've all been burned by an AIOps pitch before. The second they hear 'predictive' they hear 'another alarm source my NOC will ignore by week three.' And then there's OSS/BSS — the minute integration comes up, someone tells me about the nine months they lost to a data model with the last vendor.
Rep
What else?
Buyer
Territory. I lost both tier-1s in the carve. That was most of my pipeline last year. And marketing's basically stopped doing anything in the wholesale RSP segment, so I'm sourcing everything myself.
Rep
What else? Last one.
Buyer
Honestly? Price. We're above the challenger and I don't have a story for a CFO who knows cost to serve per service per month down to the cent.
Rep
So: capex calendar, mid-migration, they've already got correlation, OSS integration fear, territory carve, no marketing air cover, price. Seven. That's the list — nothing else? Good. Territory's real, by the way. You lost both tier-1s, that's roughly a third of your historical pipeline, and I own part of that. What I want to understand is the mid-market RSPs. There are 58 in your patch. You created two new opportunities in September.
Buyer
Because I was running the Brightline deal and the Halcyon renewal, and those were both live. I couldn't be dialling NOC leads at seven in the morning while a GM Service Assurance is waiting on a pilot scope.
Rep
Understood. Let's take the capex objection then, because if that's genuinely killing us I need to go change how we package. You had six losses tagged budget or no-decision. Of those six, how many were positioned as opex against the field services line rather than a network capex item?
Buyer
… I mean, I raised it on Brightline. Sort of. It came up late.
Rep
Okay. And Priya's working the same segment with the same objection — she had 41 first conversations last quarter, you had 38. Almost identical. Where it splits is after that. She moved 12 of 41 to a second call with a Director of Field Operations or a GM Consumer in the room. You moved 4 of 38. Help me understand that gap.
Buyer
Her accounts have had outages. Halcyon hasn't had a reportable MSD in eighteen months, so the churn story doesn't land the same way. That's luck, not skill.
Rep
Maybe. Let's look at one. This is minute eleven of your Halcyon first call. Their GM Service Assurance says — quoting — 'we're seeing churn spike about six weeks after any material outage and we can't get ahead of it.' Listen to what you do next. [plays 40 seconds] You opened the correlation dashboard. Give me the three questions you didn't ask.
Buyer
… Which suburbs. Which POI. How many services, and what the retention team spent per save.
Rep
You named them in four seconds. So you know the move. What stopped you making it on the call?
Buyer
I think I was worried he'd give me twenty minutes and I'd have shown him nothing. And honestly — that's most of my first calls. I get one number, maybe none, and then I go to product because at least product is something I can control.
Rep
That's the most useful thing either of us has said today, and it's not a file-building thing — it's a fixable thing. Here's where I've landed: territory's real and cost you pipeline. But the reason your deals die at price is you never get a dollar figure on the table, so 'we already have an assurance platform' has nothing to push against. And because you're creating two opps a week instead of five, you can't afford to disqualify Brightline, so you carried it for a quarter. One cause, two symptoms. Does that match what you see?
Buyer
Mostly. Though I still think the capex calendar is genuinely a wall on the bigger accounts.
Rep
It is — which is why it belongs in the opex conversation with a Director of Field Operations, not in a capex conversation with a CTO. That's a positioning fix and I'll help you build it. But it's not why 34 of 38 first calls didn't go to a second. So — what do you want to change first?
Buyer
No product on a first call. Three weeks. And I'll block Tuesday and Thursday mornings for the mid-market RSP list — if you can get me the list with the recent MSDs flagged, that actually helps.
Rep
Done, you'll have it Monday. Add one thing: nothing advances past stage 2 without three numbers in the pain field — dispatches per month, no-fault-found rate, cost per truck roll. I'm on your first two discovery calls this week, we debrief same day. Friday at four we look at opps created — opps, not deals. And straight with you: a third quarter like the last two changes this conversation. I don't think that's where we're going. What did you hear me commit to?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"Every account in my patch is mid-migration. Their engineering teams have zero spare cycles this year — there's nowhere to put us."” | That's a real objection and it's also the one you're supposed to be handling, not repeating to me. The answer to a Head of Network Operations mid-migration is: what's the actual ask? Two hours from someone who can point at the northbound feed, and a NOC lead who looks at output weekly. No integration sprint, no change window, nothing that touches the migration. Say that out loud on the call and see if it still ends the conversation. And separately — migration freezes are a reason to reforecast a deal, not a reason to create two opportunities in a month. Those are different problems and I don't want them bundled. |
| “"The capex committee meets quarterly and everything's already committed to core upgrades and FTTN replacement. Nothing I do moves that."” | Agreed, so stop selling it as capex. It sits in opex against dispatch cost — if it takes fifteen percent of avoidable truck rolls out, it pays from the field services line, not the network build, and the Director of Field Operations owns that budget without a committee. Say to them: '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.' Now — of your six budget-tagged losses, how many did you reposition that way before they closed? |
| “"They've all got an assurance platform and event correlation already. I keep getting 'why would I want another alarm source?'"” | Good — that objection means you're talking to a real operator. The answer is to agree with them: 'you don't want another alarm source, and if we generated one your NOC would ignore it by week three.' Correlation tells them what already broke. You're offering a lead indicator on degradation before the customer calls, delivered into the ticket they already work. Then hand them the kill switch: 'let's agree the precision threshold with your NOC lead up front — if it fires on noise, switch it off.' You lose that objection by defending. You win it by conceding it faster than they expect. |
| “"The second OSS/BSS comes up they tell me about the nine months they lost to a data model with the last vendor. It's an instant no."” | So don't lead with connectors. Ask them which systems hold fault tickets, inventory and dispatch, then tell them phase one is read-only and out-of-band — you read from the northbound feed they already publish and write nothing back until they say so. '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.' That's a scoped, falsifiable promise. What you've been doing is answering an integration fear with a capability list, which makes it worse. |
| “"Their data's a mess anyway — half the closure codes are 'other' and inventory doesn't match what's in the ground. They tell me that themselves."” | That's true at nearly every carrier and it's an opening, not a wall. The signal comes from performance and alarm telemetry, not from closure codes — bad inventory affects where you route the dispatch, not whether you spot the degradation. And one of the first outputs is a list of where the inventory record disagrees with the telemetry, which is something a GM Service Assurance will actually pay attention to. Try that line on the next one and tell me Friday whether it changed the temperature in the room. |
| “"I lost both tier-1s in the carve. That's not a coaching problem, that's a territory problem."” | It's real and I'm not arguing it — that's roughly a third of your historical pipeline and I own part of how that got done. Here's the part I need from you: there are 58 mid-market RSPs in what's left, most of them reselling access on thin margin where cost to serve per service decides whether the consumer book makes money at all. You created two opportunities in September. The carve explains why the number's harder. It doesn't explain the two. |
Questions reps ask about this call
- What should a sales coaching roleplay for Telecommunications teams actually simulate — the customer, or the rep?
Both, in separate drills. Most managers only ever practise the buyer side. But the 1:1 after two missed quarters is the higher-stakes conversation, and it's the one nobody rehearses. In DrillCall you run the rep-side version: the AI plays your underperformer, loaded with the excuses your segment actually generates — capex committee cycles, mid-migration freezes, 'we already have correlation' — and you practise draining the list, conceding the true grievance, and landing on one root cause without triggering a defensive shutdown. Then run the buyer-side drills separately against a Head of Network Operations or a GM Consumer so your rep has somewhere to take the new behaviour.
- How do I coach a rep whose excuses are genuinely true? Telco capex really is locked to a committee calendar.
Concede it out loud, early, and by name — 'territory's real, you lost both tier-1s, that's a third of your pipeline.' Conceding the one that's true is what earns you the right to press on the ones that aren't. Then separate the two claims hiding inside the excuse: 'the capex calendar slows deals' is almost certainly true, and 'the capex calendar explains why you created two opportunities in September' is almost certainly not. Reps bundle them deliberately. Your job is to unbundle them with a number, not an argument.
- Which telecom buyer titles should reps be drilling against after this coaching call?
Whichever one is missing from their opportunity records. If every stage-2 has a solution architect and no economic buyer, drill the GM Service Assurance and the Director of Field Operations — those are the people who own no-fault-found rate, first-time-fix and cost per truck roll. If the deal is retention-led, drill the GM Consumer and the Head of Customer Experience on churn by cohort after a mass service disruption. Save the CTO and COO drills for reps who can already quantify a problem; a CTO conversation without a number attached is where these deals go to die.
- How do I tell whether it's a skill gap or an effort gap?
Play ninety seconds of a real first call and ask them to name the three questions they skipped. If they name them in four seconds, it's execution — they know the move and something is stopping them making it, usually anxiety about running out of time before showing product. That's coachable with a constraint, like no product on a first call for three weeks. If they genuinely cannot name the missed questions, it's a skill gap and your plan is training and roleplay reps, not accountability check-ins. Getting this wrong is expensive: you'll hold a skill-gap rep accountable for something they don't yet know how to do.
- Should I mention a performance plan in this conversation?
Not in the first ten minutes, and not as a threat. The moment a rep hears formal-plan language they stop diagnosing and start defending, and you lose the only honest half hour you were going to get. Say the standard once, plainly, at the close — 'a third quarter like the last two changes this conversation' — and then stop. That's clarity, not a hammer. If you genuinely are heading toward a formal plan, this call still comes first, because you'll need to know whether it's skill, effort or fit before you write anything down.
- How many roleplay reps before I run the real 1:1?
Three, and vary the difficulty. Run one where the rep collapses at minute six with a fast 'yeah, I need to prospect more' — you need to practise not accepting it, because that's a rep managing you out of the room. Run one where they hold the line on capex and territory all the way through, so you can practise the experiment close. And run one where they get genuinely upset, because it happens and it's the version most managers handle worst. Fifteen minutes of drilling changes how the first ninety seconds land, and the first ninety seconds decide the rest.