How to Write a Sales Role Play Script: Template and Example

Most sales roleplay scripts are written for the wrong person. They give the rep lines to recite and leave the buyer to improvise, so the manager playing the prospect makes it up as they go and every attempt tests something different. A useful roleplay script works the other way around. It gives the rep a short brief and gives the buyer a full script: who they are, what they know, what they will only say if asked well, how they push back, and what counts as a pass.

This guide covers the seven parts of that script, a copyable template, one worked cold-call example, what we have learned about why practice scripts feel real or fall apart, and how to run the same script with an AI buyer. For ready-made situations, start with our 12 sales roleplay scenarios and use this page to write the script behind the one you pick.

TLDR

• Script the buyer in detail and give the rep only a brief. The rep should practice judgment, not recall.
• Every script has seven parts: seller brief, buyer brief, hidden facts, branching buyer responses, pressure rules, pass evidence, and a debrief with one retry.
• Each hidden fact needs an unlock condition, the rep behavior that earns it.
• For AI roleplay, add reveal rules, limits, and an end condition. For multiparty calls, write one brief per buyer.

The seven parts of a sales roleplay script

A roleplay script lets two people (or a rep and an AI buyer) run the same practice conversation the same way every time.

Share the seller brief and pass evidence with the rep before the call, so the standard is visible. Keep everything else with the buyer.

Why you script the buyer instead of the rep's lines

A rep who practices from their own lines is rehearsing a monologue, and the first unexpected question knocks them off it. One enablement program manager told us their team moved away from recorded pitch practice for this reason: nobody reads a script through a real sales conversation, so a live roleplay with objections shows readiness better. An SDR enablement leader said their coaches give frameworks and no scripts, and let reps fill in the words in their own style.

Scripting the buyer solves a different problem. When the buyer side is loose, the person playing the prospect is too easy or too hard, reveals everything in the first minute, or forgets the objection the drill was built around. Two reps who run the "same" roleplay end up practicing different calls, and their scores cannot be compared.

One exception: some teams want reps to memorize a short cold-call opener. A rep we coached on cold calls got the advice to script the opener but practice it out loud until it stopped sounding scripted. If your team uses a talk track, add it to the seller brief as a reference and keep the scripting effort on the buyer.

How to write each part

• Seller brief. Write only what a rep would know from the CRM and a few minutes of research. Name the call type and one goal, such as "book a specific next meeting." One goal per script keeps the score meaningful.
• Buyer brief. Describe the buyer by what they care about (cost, risk, speed, team time), not biographical trivia. Set an interest level. Buyers on a first call are rarely fully invested, so write something like "mildly curious, has five minutes."
• Hidden facts. For each fact, write the kind of question that earns it. "Reveals that managers cannot keep up if the rep asks what makes coverage hard" is usable. "Is secretly frustrated" is not.
• Branches. List the expected rep moves and the buyer response to each, including common mistakes like pitching early or accepting a brush-off.
• Pressure rules. Write the exact objection wording and its trigger. Match difficulty to purpose: guarded but fair for a new hire, stricter for certification.
• Pass evidence. Three to five behaviors a scorer can quote from the transcript. "Asked about the current process before pitching" is observable. "Built rapport" is not. For scoring anchors, see our sales call scorecard guide.
• Debrief and retry. Name the buyer line to restart from. Retrying one moment is faster than rerunning the whole call.

Copyable sales roleplay script template

Copy these blocks into a doc and fill in every bracket. Keep the buyer sections in a separate file or tab so the rep never sees them.

Seller brief (share with the rep)

• Call type and stage: [cold call / discovery / demo / pricing / renewal]
• Account context the rep would know: [industry, size, trigger, CRM notes]
• Who you are calling: [role and how you got the contact]
• One goal for this attempt: [single observable outcome]
• Optional talk track: [opener, if your team uses one]
• Time limit: [minutes]

Buyer brief (buyer only)

• Role and team: [title, reports to, team size]
• Current process: [how they handle this today]
• What they care about: [cost / risk / speed / team time]
• Attitude and interest level: [for example, polite, busy, mildly curious]
• When they end the call: [condition]
• Facts shared freely: [two or three surface facts]

Hidden facts (buyer only)

Branching buyer responses (buyer only)

Pressure rules (buyer only)

• Objection: [exact wording], raised when [trigger], repeated [number] times
• Difficulty: [onboarding / standard / certification]
• Never: [volunteer hidden facts, invent pricing, agree without a clear ask]

Pass evidence (share with the rep)

• [Behavior 1 a scorer can quote from the transcript]
• [Behavior 2]
• [Behavior 3]
• Pass threshold: [for example, all three present]

Debrief and retry

• What did the buyer tell you that you did not know before?
• Which hidden fact did you miss, and what question would have earned it?
• Restart point: [exact buyer line]

Worked example: a cold-call roleplay script

This example is adapted from a cold-call script we wrote for a product demo. Company and person details are fictional.

Seller brief. You are an SDR at a company that sells sales practice software. You are cold calling a senior sales training manager at a large software company with several regional offices. No prior contact. Goal: book a specific 15-minute meeting. Time limit: three minutes.

Buyer brief. You run sales training for a large, distributed team. Managers run roleplay in one-on-ones when they can fit it in. You care about manager time and consistent training across regions. You are polite but busy and will give the caller two minutes if they get to the point. Shared freely: managers handle roleplay in one-on-ones, and there is no dedicated practice program.

Hidden facts

Branching buyer responses

Pressure rules. Raise "Can you send me something?" once, after the rep first describes the product. If the rep talks for more than about 30 seconds without a question, say you have a meeting starting. Do not agree to a meeting unless the rep asks for a specific time.

Pass evidence

• States who they are and why they are calling in the first two lines
• Asks a coverage or scale question that surfaces at least one hidden fact
• Connects the offer to the buyer's own words about manager time
• Answers "send me something" with a specific meeting proposal
• Confirms the time and how the invite will be sent

Debrief and retry. If the rep accepted the brush-off, restart from "Can you send me something?" If the rep never surfaced hidden fact 2, restart from "Managers do roleplay in one-on-ones when they can fit it in."

In the original script, a strong attempt runs about 80 seconds: two questions, the gap, one sentence linking the offer to it, and a Friday meeting. For more cold-call situations to script this way, see our cold calling roleplay scenarios.

What makes a practice script feel real, and what breaks it

These patterns come from conversations with people who ran practice calls, including calls against AI buyers. Observations come first, then what we take from them.

Buyers that say too much. A sales advisor said an early practice buyer sounded like a manager quizzing the rep: it spoke perfectly, knew the product, and volunteered information. Real buyers at the VP or director level are guarded, reveal information gradually, and often have a hidden agenda about what winning this year looks like. A second advisor found a practice call too agreeable and too linear. A sales-tech founder described an over-informed buyer that jumped to deep objections before the rep had diagnosed any pain.

Buyers that are too harsh. One customer rep said a practice buyer was far harsher than real prospects, who in their experience are mostly pleasant and only sometimes dismissive. The same buyer repeated one phrase several times in a way no real person would. A fractional enablement consultant saw a buyer push back hard and fast and cut the consultant off mid-sentence.

Buyers that miss the topic that matters. An SDR enablement leader described an AI roleplay their team stopped using. The buyer was set up for a vertical with one key capability, and it never raised that topic, even after the rep did.

Scripts that drift. An enablement leader ran an objection-handling certification with five objections and ideal responses. Even when the rep answered well, the conversation went off the rails. Their preferred fix was a conversation on rails: a buyer told to reveal set pains and raise exactly the targeted objections, without improvising.

Teams disagree about that fix. The SDR enablement leader felt predefined conversation trees make a roleplay feel like a survey, because real calls jump from topic to topic. Both views are useful. Use tight branches for certification, where every rep needs the same standard. Use looser branches for everyday practice, where variety helps.

What we take from this when we write scripts: give every buyer brief an interest level, give every hidden fact an unlock condition, name the one topic the buyer must raise, and set difficulty by the call's purpose.

How we know this: this section draws on ten conversations with enablement leaders and program managers, sales advisors, a fractional enablement consultant, a sales-tech founder, and customer reps practicing cold calls. Names and company details are removed.

How to turn the script into an AI roleplay

An AI buyer can run the same script, but it needs more explicit instructions than a manager. A manager fills gaps with judgment. An AI buyer fills gaps with guesses, which is where the over-informed, overly harsh, and off-topic buyers above come from. Give the AI buyer:

• The buyer brief written as behavior. "Answers in one or two sentences until the rep asks about their process" works better than "reserved."
• Hidden facts with reveal conditions. State each fact, the question that earns it, and a rule never to share it unprompted. Reveal one fact per earned question.
• Exact objection wording and timing, including how many times to repeat each one.
• Topics the buyer must raise, if the deal depends on one capability or concern.
• Limits. No invented prices, no agreeing without a clear ask.
• An end condition. When the buyer ends the call, and what they say.

For multiparty practice, write one buyer brief per person with a different priority for each, such as a finance leader focused on cost and an operations leader focused on rollout effort. Decide who speaks first and what makes them disagree. Add moderation to the pass evidence: asking each person about their concern and summarizing where they agree. One advisor pointed out that reps are expected to moderate a buying group, and answering each buyer in turn falls short. They also suggested getting single-buyer scripts right before adding more voices.

In Quotain, you can build a simulation from a brief like this, add your playbook and call context, and run multiparty sessions with several buyer personas in one call. To use real calls as source material, see how to turn sales call recordings into roleplay scenarios.

FAQ

What is a sales roleplay script? A written plan for a practice call: a short brief for the rep, a detailed brief for the buyer, hidden facts, branching buyer responses, pressure rules, pass evidence, and a debrief with a retry point.

Should a roleplay script include the rep's lines? Mostly no. Give the rep a brief and a goal, and script the buyer. Include a short talk track only if your team expects one, such as a cold-call opener.

How long should a roleplay script be? One to two pages. A drill on a single moment can fit on half a page. A longer script is usually trying to practice more than one skill.

Can the same script work for peer, manager, and AI roleplay? Yes. Peers and managers can run it as written. For an AI buyer, add reveal conditions, limits, and an end condition so the buyer behaves the same way across attempts.

Start with one upcoming call

Pick a call on a rep's calendar this week. Write the buyer side with two hidden facts and one objection, and share only the seller brief and pass evidence. Run it, debrief, and retry from the moment that broke. To try it against an AI buyer, run a personalized practice call with no credit card.