How do you coach a rep to handle 'let me talk to my boss'?

Direct Answer

When a rep gets hit with "let me talk to my boss," the core move you coach is arming the champion plus getting a seat in the room — not chasing a callback. Teach the rep to treat that line as a signal they're talking to a coach, not the buyer, and to do two things at once: build the champion a business case they can sell upward, and request a short working session with the actual decision-maker.

As the manager, you coach this by separating the skill gap (multithreading, qualification) from the will gap (call reluctance, fear of the no), then drilling the exact language until "let me talk to my boss" turns into "let's get my boss on a 20-minute call." In 2027, with buying committees averaging 6–10 people and longer cycles, single-threaded deals that hide behind a champion's boss are the number-one source of slipped forecasts — so this is a high-leverage coaching target.

Why This Happens — Diagnose Before You Coach

"Let me talk to my boss" almost never means what the rep thinks it means. Before you coach the script, diagnose the root cause: is this a skill gap, a will gap, a knowledge gap, or a system/territory problem? Coaching the wrong layer wastes everyone's time.

• Skill gap: The rep never multithreaded. They built one relationship, never asked who else signs off, and now the deal is stalled at a gatekeeper. This is the most common cause and the most coachable.
• Will gap: The rep *knew* there was a boss but avoided the conversation because asking to meet the decision-maker feels confrontational. This is call reluctance wearing a polite mask.
• Knowledge gap: The rep can't articulate ROI in the boss's language (budget, risk, payback), so the champion has nothing to carry upward. The deflection is really "I have no ammo for my boss."
• System/territory problem: Sometimes the contact genuinely has no authority and your ICP targeting put the rep in front of the wrong persona. That's a routing and qualification fix, not a pep talk.

Use the GROW model to keep the diagnosis honest, and use the tree below in your 1:1 to route from the symptom to the real cause.

The Coaching Conversation

Run this in a 1:1 using the GROW model — Goal, Reality, Options, Will. Resist the urge to take over the deal. Your job is to make the rep capable, not to close it for them. These are verbatim scripts you can paste into a coaching doc.

Goal — set the target. Open with: *"For the Acme deal, what's the outcome you want from the next touch — and is 'I'll wait for them to talk to their boss' actually a plan?"* Make the rep say out loud that waiting is not a plan.

Reality — surface what really happened. Ask: *"Walk me through the exact words. When they said 'let me talk to my boss,' what did you say back?"* Most reps admit they said "sure, sounds good" and ended the call. Name it: passively accepting the deflection is how single-threaded deals die.

Options — generate the two moves. Coach both arms of the play.

First, arm the champion. Teach the rep to say, in the next call: *"Totally makes sense to loop in your boss. To make that easy, I'll put together a one-page summary — the problem, the expected payback, and the one risk of waiting.

What does your boss care most about: cost, time-to-value, or risk?"* This turns the champion into a guided messenger instead of an unreliable narrator. This is textbook champion enablement — you don't hope the champion sells for you; you hand them the deck, the numbers, and the words.

Second, get in the room. Drill this line until it's reflexive: *"Boss conversations always go better with all three of us in the room — I can answer the hard questions live so nothing gets lost in translation. Could we grab 20 minutes with you and [boss] on Thursday?

I'll keep it tight."* Lower the ask (20 minutes, specific day) so it's an easy yes.

Will — lock the commitment. Close the 1:1 with: *"What will you do by end of day tomorrow, and what's your fallback if they say the boss is too busy?"* Make the rep name the fallback: send the one-pager and propose three times. The discipline of multithreading is built by forcing the second contact every single deal.

The Coaching Plan / Cadence

Don't fix this in one conversation — build it over a 30/60/90 arc so the behavior sticks across the whole pipeline, not just one deal.

• Days 1–30 (Awareness): Review three of the rep's calls per week on Gong or Chorus. Every time you hear a deflection accepted, flag it and replay the moment together. Goal: the rep *notices* the deflection in real time.
• Days 31–60 (Skill): Role-play the arm-the-champion and get-in-the-room scripts twice a week until delivery is smooth. Require a documented second contact on every new opportunity in Salesforce.
• Days 61–90 (Habit): Shift to self-review — the rep brings one clip per week where they handled the boss objection well or badly and self-diagnoses. You verify multithreading is now happening at discovery, not at the stall.

The loop below is the engine. Run it continuously, not as a one-off.

Drills & Role-Play

• The deflection replay. Pull a real Gong clip where the rep ate the "talk to my boss" line. Pause at the exact moment and have the rep redeliver the get-in-the-room ask three different ways until one feels natural.
• Champion one-pager drill. Give the rep 10 minutes to write the actual one-page business case for a live deal — problem, payback, risk of inaction — in the boss's language. Grade it like the boss would.
• The hostile-boss role-play. You play a skeptical CFO who joins late and asks "why should I care?" The rep has 60 seconds to land ROI. Run it three times; raise the difficulty each round.
• Multithreading scorecard. Before any pipeline review, the rep scores each open deal: number of contacts engaged, decision-maker met yes/no, business case sent yes/no. Red on any column is a coaching trigger.

What to Measure

Watch leading indicators, not just closed-won, so you know the coaching is working weeks before quota tells you.

• Average contacts per opportunity (target ≥3; single-threaded deals are the warning sign).
• Decision-maker meeting rate — percent of deals where the rep has met the actual signer.
• Champion-enablement assets sent — one-pagers or business cases delivered per deal.
• Deflection-to-meeting conversion — how often "let me talk to my boss" becomes a booked multi-party call.
• Slip rate on single-threaded deals vs. Multithreaded deals — this number alone usually sells the whole program to the rep.

Common Mistakes Managers Make

• Rescuing the rep. You jump on the call and close it yourself. The deal is saved; the skill is not. Coach the rep to make the ask, even if it's clumsy the first time.
• Coaching the deal, not the skill. You solve the Acme stall and ignore that the rep will do the exact same thing on the next 10 deals. Always zoom out to the pattern.
• No follow-through. You give the script in the 1:1 and never check whether they used it. Inspect the next call on Chorus or it didn't happen.
• Coaching everyone the same. A will gap needs courage work; a knowledge gap needs ROI framing. Diagnosing wrong is worse than not coaching.
• Treating a system problem as a rep problem. If the rep keeps landing on no-authority contacts, fix targeting and routing — more pep talks won't make a non-buyer a buyer.

FAQ

What if the rep insists the boss really is just rubber-stamping it? Test it cheaply. Coach the line: *"Great — then a quick 15-minute intro should be painless and it protects you if your boss has a last question."* If the champion still blocks access, the deal is not as safe as the rep thinks, and you've surfaced risk early instead of at end-of-quarter.

Is "let me talk to my boss" a skill problem or a will problem? Usually both, layered. The skill gap is the missing multithreading earlier in the cycle; the will gap is the avoidance of asking for the decision-maker's time. Diagnose with the tree above before you pick the drill.

How do I coach this without taking over the deal myself? Use GROW and ask questions instead of giving answers. Let the rep run the live call after role-play. Your leverage is the next 50 deals, not this one — protect the learning even at the cost of a little short-term risk.

What if multithreading earlier feels pushy to the rep? Reframe it as service: *"Looping in everyone who'll live with this decision is how I make sure it actually works for your whole team."* Buyers in 2027 expect a seller who understands the committee; asking "who else weighs in?" reads as competence, not aggression.

When is this a coaching problem versus a hiring or comp problem? If a rep can deliver the scripts in role-play but still won't ask in real calls after 60 days of follow-through, you may have a will issue that coaching won't fix — that's a performance conversation, not another drill.

And if the rep keeps reaching powerless contacts, look at territory and ICP routing first.

Bottom Line

The one move that matters: stop letting reps treat "let me talk to my boss" as the end of the conversation. Coach the dual play — arm the champion with a business case in the boss's language, and ask for a short working session with the decision-maker — then build it into a 30/60/90 habit measured by multithreading and decision-maker meetings, not just quota.

Diagnose skill vs. Will before you drill, and never close the deal for the rep when the real goal is to make them able to close it themselves.

Sources

• Gong Labs: Multithreading and win rates
• Harvard Business Review: The New Sales Imperative (buying committees)
• Challenger / Gartner: B2B buying committee research
• RAIN Group: Sales coaching research
• Sandler: Coaching reps to qualify decision-makers
• Winning by Design: Champion and multithreading frameworks
• MEDDIC Academy: Identifying the Economic Buyer and Champion

*Sales coaching for the "let me talk to my boss" objection — how to coach a rep to handle the boss deflection, sales manager coaching guide, champion enablement and multithreading framework, and a rep coaching playbook for 2027.*