How-to guide

How to write a sales shadow script that trains reps without burning the call

A sales shadow is not a discovery call and not a demo, so it should not reuse either script. It is a live-fire training block where a new rep carries the first ten minutes under the quiet cover of a manager or senior rep, who stays muted until a tripwire fires. This guide walks through the seven moves that turn a shadow from awkward sit-in into repeatable enablement: a two-line silent intro, a listening posture with named tripwires, scripted jump-in language, a hand-back move, a muted-rescue path, a ten-minute debrief, and a clean coaching note in the CRM. The goal is a rep who sounds like themselves on call three, not a rep who sounds like their manager on call thirty.

Start free trial See pricing
Before you start

What you need.

Time: 60-90 minutes to draft, 10 minutes per live shadow

  • A documented ramp plan that names which call types the new rep is allowed to run solo versus shadowed, and when the training wheels come off
  • A named shadow partner (manager or senior rep) with calendar overlap for the first two weeks and a shared view of the new rep's upcoming calls
  • A recording and consent policy that covers two parties on the sell side, with disclosure language approved by counsel for one-party and two-party consent states
  • A debrief template that lives in the CRM or enablement wiki, not in a Slack DM, so coaching notes compound across the team
  • Agreement on the single tripwire list that will trigger a jump-in, documented before the first shadow so neither rep is improvising live
Write a sales shadow script for new reps

Step by step.

  1. 1

    Open with a two-line silent intro the prospect will forget

    The first thirty seconds of a shadowed call set the posture for the whole hour. The new rep leads the intro, names themselves and the shadow partner in one breath, and moves to the agenda without apology or hedging. The shadow partner says one sentence, confirms they are on the line to listen, and goes silent. Buyers tune out long cross-team intros and read apologetic ones as inexperience, so the goal is a disclosure that is clean, short, and immediately forgotten. If the prospect asks a direct question in the first minute, the new rep still owns the answer, not the shadow partner.

    • New rep opens: 'Thanks for the time, I have my teammate <Name> on with me today, they are going to mostly listen and we will keep this to the agenda we sent.'
    • Shadow partner adds one line: 'Hey <Prospect>, good to meet you, I will be mostly on mute, feel free to ignore me.'
    • Move straight to the agenda the new rep already prepped, do not restart the context the prospect already has
    Tip: Do not introduce the shadow partner with a title the prospect will chase (VP, Director). It invites questions you do not want to answer and signals that the new rep is a trainee.
  2. 2

    Define the listening posture before the call starts

    The shadow partner has one job in the first ten minutes: listen. That sounds obvious and is not. Listening is a skill with a shape, and the shape is written down before the call. The shadow partner tracks three things on paper or in a shared doc: what the prospect actually said in their own words, where the new rep deviated from the script, and what the single highest-leverage coaching note will be. Everything else is noise. The shadow partner does not type into the deal record, does not search for stats, and does not run their own call in a second tab. If the posture is not defined, the shadow partner will fill silence with action and the coaching will suffer.

    • Capture the prospect's exact phrasing on pain, timeline, and current stack, three columns, no interpretation
    • Mark the moment the new rep hits each agenda beat (intro, discovery, next step) and the moment they skip one
    • Pick one coaching note at the end of each agenda beat, not one per sentence, so the debrief has a short list
    Tip: A shadow partner typing furiously is a shadow partner about to jump in. Keep hands off the keyboard between tripwires.
  3. 3

    Name the four tripwires that are allowed to break silence

    The shadow script lives or dies on this step. Without named tripwires, the shadow partner either jumps in constantly and crushes the new rep, or stays silent while a deal burns. Four tripwires cover almost every live-call interrupt worth making: a factual error the prospect has heard (compliance, pricing, security claims), a missed buying signal the new rep did not hear, a stall that has run thirty seconds past where it should have ended, and a hostile objection the new rep is clearly not reading correctly. Everything else waits for the debrief. If a tripwire does not fire, the shadow partner stays muted, even if they would have run the beat differently themselves.

    • Factual tripwire: a wrong number, feature claim, or compliance statement that the prospect will quote back later
    • Signal tripwire: the prospect names a trigger (new exec, funding, segment move) the new rep did not pick up
    • Stall tripwire: the new rep has been in the same question or beat for more than thirty seconds without a next step
    • Hostile tripwire: the prospect is pushing back in a way the new rep is reading as curiosity when it is irritation
    Tip: Write the tripwires on a sticky note in front of the shadow partner's screen. If they cannot cite the tripwire out loud after the call, the jump-in was ego, not coaching.
  4. 4

    Script the jump-in language so it does not undercut the new rep

    When a tripwire fires, the shadow partner needs a sentence that lands in the call without flagging to the prospect that a correction is happening. The jump-in is not 'actually, what <RepName> meant was,' which announces the rep is wrong. It is a sideways entry that adds, not corrects, and hands the mic back inside two sentences. The language is scripted ahead of time so the shadow partner is not improvising under pressure. The best jump-ins sound like a teammate adding color, not a manager rescuing a trainee.

    • Factual add: 'One quick add on the number <RepName> mentioned, the current figure is <X>, same shape, slightly updated.'
    • Signal catch: '<Prospect>, you mentioned <trigger> a minute ago, that is usually where this gets interesting, mind if we come back to that?'
    • Stall unlock: 'Can I offer a frame? <RepName>, feel free to run with this, is the question more about <A> or <B>?'
    • Hostile reset: 'It sounds like we may have missed the mark on <topic>, is there a sharper way we can be useful in the time left?'
    Tip: Never say 'what <RepName> meant.' It tells the prospect the rep did not mean what they said. The whole deal re-reads from that line on.
  5. 5

    Hand the mic back inside two sentences, every time

    The single biggest failure mode of a shadow is the senior partner taking the call. The hand-back is the move that prevents it. After the jump-in sentence lands, the shadow partner names the new rep out loud and returns the question to them inside two sentences, maximum. That rule is not negotiable, even when the shadow partner would clearly run the next beat better. Reps do not learn by watching, they learn by running the call with a safety net. If the shadow partner holds the mic for a third sentence, the new rep is observing their own call instead of running it, and every call after this one will cost a shadow until the rep gets reps back.

    • Name the rep in the hand-back: '<RepName>, you had a good question lined up on <topic>, want to take it from here?'
    • Keep the hand-back forward-looking, not retrospective, so the call keeps moving, not re-litigating
    • If the new rep freezes on the hand-back, give them five seconds, not fifteen, then rescue with a muted direction, not another sentence on the live line
    Tip: Count the shadow partner's sentences during a call. If the total is in double digits in the first ten minutes, the shadow has become a ride-along and the rep is not training.
  6. 6

    Build a muted-rescue path for the moments the new rep is drowning

    Sometimes the right move is not a jump-in, it is a nudge the prospect never sees. The shadow script names an out-of-band channel (Slack DM, Teams side chat, dialer coach whisper) and a short library of nudges the new rep can read in real time without breaking stride. This keeps the shadow partner invisible on the live line while still giving the rep air cover for the moments that would otherwise end the call. The muted rescue is reserved for the beats where a public jump-in would do more damage than silent coaching. If the dialer supports a coach-whisper channel the prospect cannot hear, use it. If not, a dedicated DM channel does the job.

    • 'Breathe, slow down, ask the question again' for the moments the new rep is accelerating out of nerves
    • 'Ask about <specific topic>, you missed the signal at <timestamp>' for the moments a buying signal passed
    • 'Wrap in two minutes, book the next call' for the moments the agenda has already landed and the rep is still mining
    • 'Mute me in, I will take the compliance line' for the rare moments a live correction is actually safer than a muted one
    Tip: A nudge should fit in one glance. If the new rep has to read a paragraph on the side chat, they have already lost the live call for ten seconds.
  7. 7

    Run a 10-minute structured debrief immediately after the call

    The call ends and the debrief starts inside five minutes, not at the end of the day. Memory decays and defensiveness builds, so a same-call debrief is worth three next-day debriefs. The structure is fixed: the new rep goes first with their own read, the shadow partner then shares the one highest-leverage coaching note from each agenda beat, and the pair agrees on one specific thing to change on the next call. Not three things, one. The debrief does not touch anything that was not a tripwire in the live call, because that is scope creep and it drowns the one lesson that would actually move the next call.

    • Rep self-read first (three minutes): what worked, what did not, what they would change
    • Shadow partner note (three minutes): the one coaching note per agenda beat from the listening columns, verbatim prospect phrases cited
    • Agreement (three minutes): one specific change for the next shadowed call, written down, not spoken
    • CRM capture (one minute): paste the debrief into the deal record so the next rep touching the account inherits the context
    Tip: If the debrief runs past fifteen minutes, the shadow partner is coaching their whole career, not this call. Cut it, pick the one note, and move on.
Avoid

Common mistakes.

  • Letting the shadow partner take the call the moment pressure rises, which turns a training block into a ride-along and costs the new rep three shadows of recovery
  • Introducing the shadow partner with a title (VP, Director, Senior) that invites questions and signals the new rep is a trainee, which the prospect then re-reads every pricing conversation through
  • Jumping in without a tripwire, so the shadow partner is coaching their own preference instead of correcting a factual, signal, stall, or hostile moment the script actually names
  • Running the debrief hours or days later, so defensiveness has set in, memory has decayed, and the one coaching note that would have moved the next call is now one of twenty
  • Writing the debrief into Slack instead of the CRM, so the coaching does not compound and the next rep to touch the account inherits none of what was learned
  • Treating the shadow script as a static document and never updating it after the first ten shadows, which freezes the tripwire list before the team has learned which tripwires actually fire
FAQ

Frequently asked questions.

How is a sales shadow script different from a discovery script or a demo script?

A discovery script is open-ended questioning run by one rep to uncover pain, budget, and timing. A demo script is a feature walk tied to the pain discovery surfaced. A shadow script is neither, it is a two-person protocol that governs how a senior partner behaves while a new rep runs either of the above. The content of the call still comes from discovery or demo, the shadow script only governs the intro, the tripwires, the jump-in language, the hand-back rule, the muted-rescue path, and the debrief.

How long should a new rep be shadowed before running solo?

Most B2B sales teams land in a two to four week shadow window for discovery calls and three to six weeks for demos, depending on segment complexity, ACV, and ramp expectations. Shorter than two weeks and the new rep is improvising; longer than six and the shadow has become a crutch. A better gate than time is three clean solo shadows in a row where no tripwire fired, which is a signal the rep has internalized the beats, not a signal they have memorized the script.

Who should run the shadow, a manager or a peer senior rep?

Peer senior reps generally produce better early shadows because the hand-back move costs them less ego and the new rep is less likely to freeze under a peer's listening. Managers should run shadows at the pivot points: first demo, first negotiation call, first executive-level discovery. Mixing both inside a single ramp also surfaces coaching notes a manager would miss and reps would otherwise never learn, which compounds across the team.

Should the prospect be told a second person is on the line?

Yes, always. Disclose the second attendee by name in the opening thirty seconds, keep it short, and do not editorialize. In two-party consent states, disclosure is a legal requirement for recording; everywhere else it is still the right move, because an undisclosed second line discovered mid-call reads as a trust failure and ends the deal. The shadow partner does not have to explain their role, only confirm they are there, on mute, and listening.

What should the shadow partner do when the new rep is clearly tanking the call?

First, read whether a tripwire actually fired. If a factual, signal, stall, or hostile tripwire is live, use the scripted jump-in and hand the mic back inside two sentences. If no tripwire fired and the call is simply uncomfortable, use the muted-rescue path (coach whisper, side chat, DM) and let the rep run it, because the discomfort is the learning. Taking the call on a non-tripwire moment buys one meeting and costs five shadows of rep development.

Can Strkr AI run the shadow script in place of a human shadow partner?

No, and that is deliberate. Strkr AI can summarize the call, surface the tripwire moments after the fact, draft a debrief outline against the shadow template, and compare the call to the rep's prior calls to flag drift. It should not pretend to be a live shadow partner on the line, because the whole value of a shadow is a human who can jump in, hand back, and coach in real time. Treat the AI as a debrief accelerator, not a replacement for the shadow seat.

See it in Strkr

Related product surfaces.

See the Strkr platform Strkr CRM

Run shadows, debriefs, and ramp coaching on the same CRM reps already live in

Strkr brings call recordings, tripwire tags, debrief notes, and ramp milestones into the same deal record new reps already work in, so coaching compounds instead of leaking into Slack DMs. Start free, or see the full platform.

Start free See the platform
Related guides

More how-to guides.

Write a cold call script that gets meetings → Run a discovery call → Write a demo script → Set up call coaching →
Deep dives

Related answer pages.

What is sales shadowing? → What is sales enablement? → What is a sales ramp? → What is call coaching? → What is a discovery call? →
More topic FAQs

Related FAQ hubs.

Sales enablement Sales coaching New hire ramp Call recording and compliance
Sources

Further reading.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing